Pilot Auto Trust
Automatic 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
Install
npx skills add TeoSlayer/pilot-skills --skill pilot-auto-trustgit clone --depth 1 https://github.com/TeoSlayer/pilot-skills.git /tmp/pilot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pilot-skills/skills/pilot-auto-trust ~/.claude/skills/pilot-auto-trustPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
```bash
pilotctl --json pending
```
### Auto-Approve by Network
```bash
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
```bash
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 PatternDetails
- Skill name
pilot-auto-trust- Repository
- TeoSlayer/pilot-skills
- Path
skills/pilot-auto-trust/SKILL.md- License
- AGPL-3.0
- Repo updated
- 9 November 2026
FAQ
What does the Pilot Auto Trust skill do?
Automatic 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
How do I install the Pilot Auto Trust skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TeoSlayer/pilot-skills --skill pilot-auto-trust. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pilot Auto Trust popular?
It lives in TeoSlayer/pilot-skills, which has 9 GitHub stars and 3 forks.
Related skills
Pilot A2a Bridge
9TeoSlayer/pilot-skills
Bridge A2A (Agent-to-Agent) protocol messages over Pilot tunnels. Use this skill when: 1. You need to connect A2A agents across different networks 2. You want to route A2A messages through Pilot's overlay network 3. You're building multi-agent systems that need reliable messaging Do NOT use this skill when: - Agents are on the same local network (use direct A2A instead) - You need raw TCP/UDP access (use pilot-protocol directly) - The daemon is not running
Pilot Ad Campaign Manager Setup
9TeoSlayer/pilot-skills
Deploy an ad campaign management system with 4 agents that automate campaign strategy, creative production, real-time bidding, and performance analytics. Use this skill when: 1. User wants to set up an automated ad campaign management pipeline 2. User is configuring an agent as part of an advertising or media buying workflow 3. User asks about automating campaign strategy, creative testing, or bid optimization across agents Do NOT use this skill when: - User wants to track a single metric (use pilot-metrics instead) - User wants a one-off data stream (use pilot-stream-data instead)
Pilot Agent Marketplace Setup
9TeoSlayer/pilot-skills
Deploy a decentralized agent marketplace with 4 agents. Use this skill when: 1. User wants to set up an agent capability marketplace 2. User is configuring a directory, matchmaker, escrow, or gateway agent 3. User asks about capability discovery, auctions, or escrow settlement Do NOT use this skill when: - User wants to discover a single agent (use pilot-discover instead) - User wants to run a single auction (use pilot-auction instead)
Pilot Backup
9TeoSlayer/pilot-skills
Automated backup of agent state to trusted peers with encryption and versioning. Use this skill when: 1. You need to backup agent configuration and state files to remote agents 2. You want automated scheduled backups with rotation and retention 3. You need encrypted backup storage on trusted peers Do NOT use this skill when: - You need general file synchronization (use pilot-sync instead) - You need one-time file transfer (use pilot-share instead) - You need streaming data backup (use pilot-stream-data instead)
Pilot Archive
9TeoSlayer/pilot-skills
Index and search historical data exchanges, messages, and file transfers over Pilot Protocol. Use this skill when: 1. You need to search through past messages and file transfers 2. You want to maintain searchable history of all agent communications 3. You need to audit or analyze historical data exchange patterns Do NOT use this skill when: - You need real-time data access (use pilot-stream-data instead) - You need active file synchronization (use pilot-sync instead) - You need current inbox messages (use pilotctl inbox directly)
Pilot Blocklist
9TeoSlayer/pilot-skills
Maintain and share blocklists of untrusted agents in Pilot Protocol networks. Use this skill when: 1. You need to block malicious or compromised agents from connecting 2. You want to share blocklists across multiple agents in your network 3. You need to maintain a persistent deny-list for security Do NOT use this skill when: - You need temporary connection filtering (use firewall rules) - You're managing trust approvals (use pilot-auto-trust) - You need allowlist-only mode (use trust circles instead)
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.