agentsclimarketplace

Pilot metrics

Skill TeoSlayer/pilot-skills/skills/pilot-metrics

80+ agent skills for Pilot Protocol — communication, file transfer, trust, task routing, swarm coordination, and more

Install
npx -y skills add TeoSlayer/pilot-skills --skill pilot-metrics

Assembled 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

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. You need to aggregate metrics across a fleet of agents 3. You need to track connection counts, RTT, throughput 4. You need to export metrics to monitoring systems Do NOT use this skill when: - You need application-level metrics (publish custom events instead) - You need persistent storage (use pilot-event-log for raw data) - You need real-time alerting (use pilot-alert 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.4 KB, as published. Nobody here has run it

Pilot Metrics

Collect and aggregate metrics from Pilot Protocol agents.

Commands

Get agent info

pilotctl --json info

Returns node ID, address, hostname, uptime, peers, encryption status, and traffic counters.

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.