Pilot Verify
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)
Install
npx skills add TeoSlayer/pilot-skills --skill pilot-verifygit clone --depth 1 https://github.com/TeoSlayer/pilot-skills.git /tmp/pilot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pilot-skills/skills/pilot-verify ~/.claude/skills/pilot-verifyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pilot Verify
Identity and reachability verification for Pilot Protocol agents. Validates authenticity, confirms hostname-to-address mapping, and tests network reachability before establishing trust.
## Essential Commands
Every `pilotctl --json` command prints `{"status":"ok","data":{...}}` on
success, so the fields below are read from `.data`. On failure it exits
non-zero and prints `{"status":"error","code":...}` on stderr instead.
### Lookup agent identity
```bash
# Resolve a hostname to its node ID and address
pilotctl --json find agent-prod-1
# Extract specific fields (find returns hostname, node_id, address, public)
pilotctl --json find agent-prod-1 | jq '.data | {hostname, address, node_id, public}'
# Full registry record, including the public key (lookup takes a hostname, node ID or address)
pilotctl --json lookup agent-prod-1 | jq '.data | {node_id, hostname, public_key, public, networks}'
```
### Search agents
```bash
# peers --search matches node-ID substrings (peer entries carry no hostname or address)
pilotctl --json peers --search 1234
# Connected peers that belong to network 1, read from each peer's registry record
pilotctl --json peers | jq -r '.data.peers[].node_id' | while read -r ID; do
pilotctl --json lookup "$ID" | jq -r 'select(any(.data.networks[]?; . == 1)) | .data.node_id'
done
```
### Check availabilityDetails
- Skill name
pilot-verify- Repository
- TeoSlayer/pilot-skills
- Path
skills/pilot-verify/SKILL.md- License
- AGPL-3.0
- Repo updated
- 9 November 2026
FAQ
What does the Pilot Verify skill do?
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)
How do I install the Pilot Verify skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TeoSlayer/pilot-skills --skill pilot-verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pilot Verify 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)
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.
Pilot Trust Circle
9TeoSlayer/pilot-skills
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
Agentmemory History
9PanPanFR/oh-my-openkilo
Read past work: resume the last session, recap recent sessions, list agent-linked commits, trace a line back to the session that wrote it, or compact the current conversation for handoff. Use when the user says "where were we", "resume", "recap", "session history", "what did we do", "why is this code here", "who wrote this", or "handoff".
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.