skills.rest
TeoSlayer
TeoSlayerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pilot-metrics

Collect and aggregate Pilot Protocol agent metrics for fleet health monitoring.

7|3|Updated Apr 8, 2026
Search Tags:#monitoring#dashboards#metrics#observability#telemetry#fleet#pilot-protocol
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-metrics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pilot-metrics
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-metrics
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects and aggregates metrics from Pilot Protocol agents to provide visibility into health, performance, and fleet activity.

Core Features & Use Cases

  • Collects node, peer, and connection metrics from Pilot Protocol daemons.
  • Aggregates metrics for dashboards, alerting, and troubleshooting across fleets.
  • Exposes insights for health checks, RTT, throughput, and trust status in real time.

Quick Start

Install and enable the pilot-metrics skill to start gathering metrics from running Pilot Protocol agents.

Frequently Asked Questions about pilot-metrics

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

FAQPage Schema
How do I monitor agent health and collect metrics from a Pilot Protocol fleet?▼

To monitor agent health, you need to collect metrics from Pilot Protocol daemons, peers, and custom events. This skill aggregates node, peer, and connection metrics to provide real-time visibility into fleet performance and overall trust status.

What telemetry data can I track for my Pilot Protocol agents?▼

You can track connection counts, round-trip time (RTT), throughput, and overall trust status. The skill exposes these telemetry insights for health checks, troubleshooting, and fleet activity monitoring in real time.

Do I need a running pilotctl daemon to gather fleet observability data?▼

Yes, a running pilotctl daemon is required to gather fleet observability data. You also need jq installed for JSON processing and a properly configured pilot-metrics skill installation to start collecting metrics from your agents.

How do I set up dashboards and alerting for my Pilot Protocol network?▼

You can set up dashboards and alerting by installing and enabling the pilot-metrics skill. It aggregates node, peer, and connection metrics, allowing you to visualize fleet activity and configure alerts for connection counts and health status.

What is the best way to troubleshoot connection issues across a fleet of agents?▼

The best way to troubleshoot connection issues is by aggregating real-time metrics from your Pilot Protocol daemons. This skill collects node and peer data, exposing health checks and RTT insights needed to identify and resolve fleet communication problems.

Can I use this metrics collection approach without jq installed?▼

No, jq is explicitly required for JSON processing within the metrics collection workflow. Along with a running pilotctl daemon, jq must be installed to properly parse and aggregate telemetry data from your Pilot Protocol agents.

Related Skills

Explore More Data & Analytics Skills→
TeoSlayerTeoSlayer
7

pilot-audit-log

Generate structured audit trails for Pilot Protocol activity.

Community
Advanced
Steffen025Steffen025
186

VoiceServer

Invoke a local ElevenLabs TTS server for real-time voice notifications.

Community
Advanced
dtsongdtsong
1

Fleet Management

Design IoT fleet management infrastructure for device provisioning, OTA updates, and telemetry aggregation.

Community
Advanced
TeoSlayerTeoSlayer
7

pilot-mesh-status

Aggregate daemon health, peer status, and bandwidth data from pilotctl.

Community
Advanced