TeoSlayer/pilot-skills / skills/pilot-auto-trust
pilot-auto-trust
VerifiedAutomatic trust management with configurable policies for Pilot Protocol agents. Use this skill when: 1. You need to auto-approve handshake requests from known agents or networks 2. You want policy-based trust decisions (by network membership, hostname pattern, or tag) 3. You need to batch-process pending trust requests Do NOT use this skill when: - You need manual review of every trust request - You're dealing with unknown or potentially malicious agents - You need fine-grained per-agent trust policies
Pilot Auto-Trust
Automated trust management for Pilot Protocol with policy-based decision making.
Commands
Pending entries carry only node_id, public_key, justification and
received_at (under .data.pending[]) — no hostname and no address. To
apply a policy on hostname or network, resolve each requester in the
registry with lookup first. A requester whose record the registry won't
return (for example a private node) gets no hostname or networks, so these
rules leave it pending for manual review.
List Pending Requests
pilotctl --json pending
Auto-Approve by Network
pilotctl --json pending | jq -r '.data.pending[].node_id' | while read -r NODE_ID; do
if pilotctl --json lookup "$NODE_ID" | jq -e 'any(.data.networks[]?; . == 1)' >/dev/null; then
pilotctl --json approve "$NODE_ID"
fi
done
Auto-Approve by Hostname Pattern
pilotctl --json pending | jq -r '.data.pending[].node_id' | while read -r NODE_ID; do
HOST=$(pilotctl --json lookup "$NODE_ID" | jq -r '.data.hostname // empty')
case "$HOST" in
agent-prod-*) pilotctl --json approve "$NODE_ID" ;;
esac
done
Hostnames are first-come in the registry — anyone can claim an unused
agent-prod-… name — so pair a hostname rule with a network or public-key
check before approving anything sensitive.
Batch Reject by Hostname Pattern
pilotctl --json pending | jq -r '.data.pending[].node_id' | while read -r NODE_ID; do
HOST=$(pilotctl --json lookup "$NODE_ID" | jq -r '.data.hostname // empty')
case "$HOST" in
untrusted-*) pilotctl --json reject "$NODE_ID" "Untrusted source" ;;
esac
done
Workflow Example
#!/bin/bash
# Auto-approve production agents from a known network; reject requesters
# the registry places on other networks; leave unresolvable ones pending.
pilotctl --json pending | jq -r '.data.pending[].node_id' | while read -r NODE_ID; do
RECORD=$(pilotctl --json lookup "$NODE_ID" 2>/dev/null) || continue # unresolvable: manual review
HOST=$(echo "$RECORD" | jq -r '.data.hostname // empty')
ON_PROD=$(echo "$RECORD" | jq -r 'any(.data.networks[]?; . == 1)')
if [ "$ON_PROD" = "true" ]; then
case "$HOST" in
agent-prod-*) pilotctl --json approve "$NODE_ID" ;;
esac
else
pilotctl --json reject "$NODE_ID" "Unknown network"
fi
done
Dependencies
Requires pilot-protocol, pilotctl, and jq.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |