Pilot verify

Skill TeoSlayer/pilot-skills/skills/pilot-verify

80+ agent skills for Pilot Protocol — communication, file transfer, trust, task routing, swarm coordination, and more

Install

npx -y skills add TeoSlayer/pilot-skills --skill pilot-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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)

The file declares its own license as AGPL-3.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, 738 tokens by cl100k_base, as published. Nobody here has run it

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

Lookup agent identity

# Basic lookup by hostname
pilotctl --json find agent.pilot

# Extract specific fields
pilotctl --json find agent.pilot | jq '.[0] | {hostname, address, node_id, public, public_key}'

Search agents

# Find by pattern
pilotctl --json peers --search "agent-prod"

# Find in network
pilotctl --json peers | jq '.[] | select(.address | startswith("1:"))'

Check availability

# Ping agent
pilotctl --json ping agent.pilot

# Ping with timeout
timeout 5s pilotctl --json ping agent.pilot || echo "Agent unreachable"

Get local info

pilotctl --json info | jq '{hostname, address, peers, encrypted_peers, authenticated_peers}'

Verify identity matches expected fingerprint

AGENT="agent.pilot"
EXPECTED_PUBKEY="abc123..."

ACTUAL=$(pilotctl --json find "$AGENT" | jq -r '.[0].public_key')
if [ "$ACTUAL" = "$EXPECTED_PUBKEY" ]; then
  echo "Identity verified: public key matches"
else
  echo "Identity verification FAILED: pubkey mismatch (expected $EXPECTED_PUBKEY, got $ACTUAL)"
  exit 1
fi

Workflow Example

Comprehensive verification before trust:

#!/bin/bash
set -e

AGENT="$1"
EXPECTED_PUBKEY="${2:-}"

echo "=== Verifying Agent: $AGENT ==="

# Step 1: Lookup identity
echo "1. Looking up identity..."
IDENTITY=$(pilotctl --json find "$AGENT" | jq '.[0]')
if [ -z "$IDENTITY" ] || [ "$IDENTITY" = "null" ]; then
  echo "FAILED: Agent not found"
  exit 1
fi

NODE_ID=$(echo "$IDENTITY" | jq -r '.node_id')
ADDRESS=$(echo "$IDENTITY" | jq -r '.address')
PUBKEY=$(echo "$IDENTITY" | jq -r '.public_key')
echo "  Node ID:    $NODE_ID"
echo "  Address:    $ADDRESS"
echo "  Public key: ${PUBKEY:0:16}..."

# Step 2: Verify public-key fingerprint if expected value provided
if [ -n "$EXPECTED_PUBKEY" ]; then
  echo "2. Checking public-key fingerprint..."
  if [ "$PUBKEY" != "$EXPECTED_PUBKEY" ]; then
    echo "FAILED: Public-key mismatch"
    exit 1
  fi
  echo "  PASSED"
fi

# Step 3: Test reachability
echo "3. Testing reachability..."
if ! timeout 5s pilotctl --json ping "$AGENT" >/dev/null 2>&1; then
  echo "FAILED: Agent unreachable"
  exit 1
fi
echo "  PASSED"

echo ""
echo "Status: VERIFIED"
echo "Safe to proceed with trust/connection."

Dependencies

Requires pilot-protocol skill, pilotctl binary on PATH, running daemon, jq for JSON parsing, and timeout for reachability testing.

What ships with it: 1 file

688 B alongside SKILL.md

README.md688 B