How do I install the Pilot Health skill?

Run npx skillmds@latest add teoslayer/pilot-health in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pilot Health safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pilot Health?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pilot Health free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under AGPL-3.

Who published Pilot Health?

TeoSlayer (@teoslayer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pilot Health by teoslayer — Agent Skill

Name: Pilot Health
Author: TeoSlayer

Pilot Health

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)

TeoSlayer 7c14658 2 files · 2.9 KB Updated Sep 17, 2026

File contents

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).

---name: pilot-healthdescription: 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)license: AGPL-3.0---# pilot-healthNetwork health monitoring for Pilot Protocol agents. Check connectivity, measure latency, diagnose routing issues, and monitor daemon health.## Commands### Ping an agent```bashpilotctl --json ping <node-id>```Sends ICMP-like echo requests and returns round-trip time statistics.### Traceroute to agent```bashpilotctl --json traceroute <node-id>```Shows the path packets take through the network, including relay hops.### Benchmark connection```bashpilotctl --json bench <node-id>```Measures throughput, latency under load, and connection stability.### Check daemon status```bashpilotctl --json daemon status```Returns daemon health including uptime, memory usage, connection count.### List active connections```bashpilotctl --json connections```Shows all active connections with state, ports, encryption status, and byte counts.### List all peers```bashpilotctl --json peers```Returns known agents with last contact timestamp.## Workflow ExampleDiagnose why connections to a specific agent are slow:```bash# Check basic reachabilityping_result=$(pilotctl --json ping "ai-worker-01")echo "$ping_result" | jq '{avg_rtt: .avg_rtt_ms, loss: .packet_loss_pct}'# Identify relay hopstrace=$(pilotctl --json traceroute "ai-worker-01")echo "$trace" | jq '.hops[] | {hop: .hop_num, node: .node_id, rtt: .rtt_ms}'# Measure throughputbench=$(pilotctl --json bench "ai-worker-01")echo "$bench" | jq '{throughput_mbps: .throughput_mbps, latency_p99: .latency_p99_ms}'# Check daemon healthpilotctl --json daemon status | jq '{uptime: .uptime_seconds, conn_count: .connection_count}'```## DependenciesRequires the `pilot-protocol` core skill and a running daemon. Target agents must be reachable (may require trust for private agents).

Frequently asked questions