Pilot Metrics

Collect and aggregate agent metrics from connections, peers, and custom events. Use this skill when: 1. You need to monitor agent health and performance 2. Y...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (collecting agent metrics) and do not request unrelated credentials or perform unexpected actions.

Purpose & Capability

Name/description ask for agent metrics and the skill only requires pilotctl and jq, which are directly relevant. Declaring dependency on the pilot-protocol skill and a running daemon is consistent with the stated purpose.

Instruction Scope

SKILL.md only instructs running pilotctl commands and using jq to aggregate JSON into a local /tmp file. It does not read unrelated system files, request unrelated environment variables, or post data to external endpoints.

Install Mechanism

No install spec — instruction-only. Nothing is downloaded or written to disk by the skill itself beyond the example script writing to /tmp, so installation risk is low.

Credentials

No environment variables, credentials, or config paths are required. The requested binaries (pilotctl, jq) are appropriate for the functionality described.

Persistence & Privilege

The skill does not request always:true or elevated privileges, and it does not modify other skills or global agent configuration. Autonomous invocation is allowed by default but not excessive here.

Assessment

This skill appears coherent and limited to running pilotctl and jq to collect metrics. Before installing: ensure the pilotctl binary you have on PATH is from a trusted source (the skill runs it with your permissions), confirm the pilot daemon is intended to run on the host, and be aware the example script writes to /tmp (review and run in a safe environment). The skill is AGPL-3.0 licensed and depends on the separate pilot-protocol skill — verify that dependency. If you do not trust the pilotctl binary or the pilot network, do not enable the skill.

Collect and aggregate metrics from Pilot Protocol agents.

Commands

Get agent info

pilotctl --json info

Returns node ID, address, hostname, uptime, polo score.

Get peer list

pilotctl --json peers

Lists connected peers with connection time.

Get connections

pilotctl --json connections

Lists active connections with state, ports, bytes sent/received.

Subscribe to custom metrics

pilotctl --json subscribe <source-hostname> "metrics.*" [--timeout <seconds>]

Workflow Example

Fleet health dashboard:

#!/bin/bash
OUTPUT_FILE="/tmp/fleet-metrics-$(date +%Y%m%d-%H%M%S).json"

echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","agents":[]}' > "$OUTPUT_FILE"

agents=$(pilotctl --json trust 2>/dev/null | jq -r '.data.trusted[].hostname')

for agent in $agents; do
  ping_result=$(pilotctl --json ping "$agent" 2>/dev/null)
  rtt_ms=$(echo "$ping_result" | jq -r '.data.results[0].rtt_ms // null')

  agent_data=$(jq -n --arg hostname "$agent" --arg rtt "$rtt_ms" \
    '{hostname: $hostname, rtt_ms: ($rtt | tonumber), status: "online"}')

  jq --argjson agent "$agent_data" '.agents += [$agent]' "$OUTPUT_FILE" > "${OUTPUT_FILE}.tmp"
  mv "${OUTPUT_FILE}.tmp" "$OUTPUT_FILE"
done

Dependencies

Requires pilot-protocol skill, jq, and a running daemon.