pilot-health

Diagnoses network health issues for Pilot Protocol agents using pilotctl.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-health
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-health
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network health monitoring for Pilot Protocol agents, enabling rapid diagnosis of connectivity and routing issues to maintain uptime and performance.

Core Features & Use Cases

  • Ping and traceroute to diagnose reachability and routing.
  • Benchmark and monitor daemon health and active connections across peers.
  • Continuous health checks for uptime monitoring and alerting.

Quick Start

Install the Pilot Health skill and start the Pilot Protocol daemon, then run a health check.

Frequently Asked Questions about pilot-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose network latency and routing issues for Pilot Protocol agents?

To diagnose Pilot Protocol network latency, this Skill applies ping and traceroute commands to measure reachability and identify routing issues across peers. It outputs actionable latency and routing diagnostics.

Do I need the pilotctl daemon running to monitor Pilot Protocol network health?

Yes, monitoring Pilot Protocol network health requires the pilotctl binary on your PATH and a running pilotctl daemon. The daemon enables peer listing and active connection benchmarking for health checks.

What is the best way to monitor daemon health and active connections across Pilot Protocol peers?

Monitor Pilot Protocol daemon health by running benchmark and daemon status commands across peers. This assesses active connections and produces actionable outputs for network uptime monitoring.

Can I perform continuous health checks and alerting for Pilot Protocol network uptime?

Yes, you can perform continuous health checks for Pilot Protocol uptime monitoring and alerting. It applies repeated peer listing and daemon status checks to maintain network performance and connectivity.

Why does Pilot Protocol connectivity fail between specific peers despite a running daemon?

Pilot Protocol connectivity failures can be diagnosed by running traceroute to assess routing issues and ping to check reachability. This identifies specific network paths causing peer connection drops.