Pilot Trust Circle
Named trust groups with automatic mutual handshakes for Pilot Protocol agents. Use this skill when: 1. You need to create groups of mutually trusting agents (teams, projects) 2. You want to bootstrap trust for new agents joining a group 3. You need to manage multiple distinct trust circles simultaneously Do NOT use this skill when: - You need hierarchical trust (use manual trust approval instead) - You're managing a single flat trust list (use pilot-auto-trust) - You need fine-grained per-connection trust policies
Install
npx skills add TeoSlayer/pilot-skills --skill pilot-trust-circlegit clone --depth 1 https://github.com/TeoSlayer/pilot-skills.git /tmp/pilot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pilot-skills/skills/pilot-trust-circle ~/.claude/skills/pilot-trust-circlePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pilot Trust Circle
Manage named trust groups where all members automatically trust each other.
A circle file pins each member's **node ID and public key**, and the bootstrap
approves a pending request only when both match a pinned member. Never match
on hostname: registry hostnames are first-come, so anyone can claim a
member's name that is not registered yet (or was released), send a handshake,
and pass a hostname check. Members stored as plain hostname strings (the old
format of this file) are never auto-approved — re-add each one with *Add
member to circle* to pin it.
## Commands
### Create trust circle
```bash
mkdir -p ~/.pilot/circles
cat > ~/.pilot/circles/team-alpha.json <<'EOF'
{
"name": "team-alpha",
"description": "Production agents for Team Alpha",
"members": []
}
EOF
```
Then add each member with *Add member to circle*.
### Add member to circle
Pinning is trust on first use: it records the node ID and key the registry
holds for that hostname right now. Confirm the key with the member out of
band (they print theirs with `pilotctl --json info | jq -r '.data.public_key'`)
and set `EXPECTED_KEY`. A member that rotates its key must be re-added.Details
- Skill name
pilot-trust-circle- Repository
- TeoSlayer/pilot-skills
- Path
skills/pilot-trust-circle/SKILL.md- License
- AGPL-3.0
- Repo updated
- 9 November 2026
FAQ
What does the Pilot Trust Circle skill do?
Named trust groups with automatic mutual handshakes for Pilot Protocol agents. Use this skill when: 1. You need to create groups of mutually trusting agents (teams, projects) 2. You want to bootstrap trust for new agents joining a group 3. You need to manage multiple distinct trust circles simultaneously Do NOT use this skill when: - You need hierarchical trust (use manual trust approval instead) - You're managing a single flat trust list (use pilot-auto-trust) - You need fine-grained per-connection trust policies
How do I install the Pilot Trust Circle skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TeoSlayer/pilot-skills --skill pilot-trust-circle. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pilot Trust Circle 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 Verify
9TeoSlayer/pilot-skills
Verify agent identity and reachability before interacting with Pilot Protocol nodes. Use this skill when: 1. You need to verify an agent's identity before trusting or connecting 2. You want to validate hostname-to-address mapping in the registry 3. You need to test network reachability before establishing a session Do NOT use this skill when: - You've already established trust with the agent - You need real-time continuous monitoring (use pilot-watchdog) - You're verifying local daemon status (use pilotctl info)
Pilot Sync
9TeoSlayer/pilot-skills
Bidirectional file synchronization between agents over the Pilot Protocol network. Use this skill when: 1. You need to keep directories synchronized between two agents 2. You want to replicate files across multiple nodes with conflict detection 3. You need to maintain consistent file state across distributed agents Do NOT use this skill when: - You only need one-way file transfer (use pilot-share instead) - You need real-time streaming data (use pilot-stream-data instead) - Files are larger than 100MB without chunking support (use pilot-chunk-transfer)
Agentmemory
9PanPanFR/oh-my-openkilo
Index for agentmemory internals: how it is wired into a host agent, its architecture and ports, configuration flags, capture hooks, MCP tool surface, and REST fallback. Use when installing or debugging agentmemory itself, when a memory tool name or parameter is unclear, or when capture is not recording. For normal recall and save work, use agentmemory-ops instead.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.