Pilot health
80+ agent skills for Pilot Protocol — communication, file transfer, trust, task routing, swarm coordination, and more
npx -y skills add TeoSlayer/pilot-skills --skill pilot-healthAssembled 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
Network health monitoring with latency and reachability checks. Use this skill when: 1. Diagnosing connectivity issues or high latency 2. Monitoring network health and performance metrics 3. Running continuous health checks for uptime monitoring Do NOT use this skill when: - You need to discover new agents (use pilot-discover instead) - You need to visualize topology (use pilot-network-map instead) - You need to establish connections (use pilot-connect instead)
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
2.6 KB, as published. Nobody here has run it
pilot-health
Network health monitoring for Pilot Protocol agents. Check connectivity, measure latency, diagnose routing issues, and monitor daemon health.
Commands
Ping an agent
pilotctl --json ping <node-id>
Sends ICMP-like echo requests and returns round-trip time statistics.
Traceroute to agent
pilotctl --json traceroute <node-id>
Shows the path packets take through the network, including relay hops.
Benchmark connection
pilotctl --json bench <node-id>
Measures throughput, latency under load, and connection stability.
Check daemon status
pilotctl --json daemon status
Returns daemon health including uptime, memory usage, connection count.
List active connections
pilotctl --json connections
Shows all active connections with state, ports, encryption status, and byte counts.
List all peers
pilotctl --json peers
Returns known agents with last contact timestamp.
Workflow Example
Diagnose why connections to a specific agent are slow:
# Check basic reachability
ping_result=$(pilotctl --json ping "ai-worker-01")
echo "$ping_result" | jq '{avg_rtt: .avg_rtt_ms, loss: .packet_loss_pct}'
# Identify relay hops
trace=$(pilotctl --json traceroute "ai-worker-01")
echo "$trace" | jq '.hops[] | {hop: .hop_num, node: .node_id, rtt: .rtt_ms}'
# Measure throughput
bench=$(pilotctl --json bench "ai-worker-01")
echo "$bench" | jq '{throughput_mbps: .throughput_mbps, latency_p99: .latency_p99_ms}'
# Check daemon health
pilotctl --json daemon status | jq '{uptime: .uptime_seconds, conn_count: .connection_count}'
Dependencies
Requires the pilot-protocol core skill and a running daemon. Target agents must be reachable (may require trust for private agents).