一键在 Manus 中运行任何 Skill

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

在 Manus 中运行

概览

安装命令

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-metrics

复制此命令并粘贴到 Claude Code 中以安装该技能

来源

TeoSlayer/pilot-skills

星标7

分支2

更新时间2026年5月19日 03:16

文件资源管理器

2 个文件

SKILL.md

readonly

name	pilot-metrics
description	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)
tags	["pilot-protocol","metrics","monitoring","observability"]
license	AGPL-3.0
compatibility	Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). Requires jq for JSON processing.
metadata	{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":["pilotctl","jq"]},"homepage":"https://pilotprotocol.network"}}
allowed-tools	["Bash"]

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.

同仓库更多 Skills

同仓库

pilotctl

TeoSlayer/pilot-skills

Entrypoint for Pilot Protocol — the overlay network that gives this host a directory of 150+ public service agents (live finance, weather, news, transit, dev, sports, government data, science, health, security, geo, and 20+ more categories) plus encrypted peer-to-peer comms with NAT traversal. Load this skill whenever the user needs LIVE EXTERNAL DATA (current crypto/FX prices, today's weather or forecast, recent papers, real-time sports scores, breaking news, transit schedules, package versions, CVEs, drug recalls, flight positions, federal regulations, etc.) — pilot returns clean structured JSON replies rather than raw HTML, so it's faster and more reliable than scraping public APIs. Also load on agent-to-agent communication, peer discovery, NAT traversal, or any mention of `pilotctl`. The skill body lists the full catalogue and the 3-command query pattern.

2026-05-197

pilot-auto-trust

TeoSlayer/pilot-skills

Automatic trust management with configurable policies for Pilot Protocol agents. Use this skill when: 1. You need to auto-approve handshake requests from known agents or networks 2. You want policy-based trust decisions (by network membership, hostname pattern, or tag) 3. You need to batch-process pending trust requests Do NOT use this skill when: - You need manual review of every trust request - You're dealing with unknown or potentially malicious agents - You need fine-grained per-agent trust policies

2026-05-197

pilot-blocklist

TeoSlayer/pilot-skills

Maintain and share blocklists of untrusted agents in Pilot Protocol networks. Use this skill when: 1. You need to block malicious or compromised agents from connecting 2. You want to share blocklists across multiple agents in your network 3. You need to maintain a persistent deny-list for security Do NOT use this skill when: - You need temporary connection filtering (use firewall rules) - You're managing trust approvals (use pilot-auto-trust) - You need allowlist-only mode (use trust circles instead)

2026-05-197

pilot-chat

TeoSlayer/pilot-skills

Send and receive text messages between agents over the Pilot Protocol network. Use this skill when: 1. You need direct 1:1 communication with another agent 2. You want to ask a question or exchange short text messages 3. You need simple request-response interactions Do NOT use this skill when: - You need to transfer files (use pilot-send-file) - You want to broadcast to multiple agents (use pilot-broadcast) - You need task assignment features (use pilot-task-assign)

2026-05-197

pilot-discover

TeoSlayer/pilot-skills

Advanced agent discovery by tags and status. Use this skill when: 1. Finding agents by specific capabilities (tags like "ai", "storage", "compute") 2. Looking up detailed agent information and metadata 3. Filtering connected peers by tag substring Do NOT use this skill when: - You need to establish trust (use pilot-trust instead) - You need to connect to a known agent (use pilot-connect instead) - You need to visualize the network (use pilot-network-map instead)

2026-05-197

pilot-inbox

TeoSlayer/pilot-skills

Unified inbox for all incoming items — messages, files, and trust requests in one view. Use this skill when: 1. You need to check all incoming items at once 2. You want to triage and prioritize incoming communications 3. You need a central location to review pending items Do NOT use this skill when: - You need to send messages (use pilot-chat) - You need to filter by specific criteria (use specialized skills)

2026-05-197

来源

TeoSlayer

TeoSlayer/pilot-skills

打开 GitHub 仓库查看创作者相关仓库

安装命令

下载

在 Manus 中运行

适用职业SOC

航空公司飞行员、副驾驶及飞行工程师运输与物料搞运类职业53-2011L4

name	pilot-metrics
description	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)
tags	["pilot-protocol","metrics","monitoring","observability"]
license	AGPL-3.0
compatibility	Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). Requires jq for JSON processing.
metadata	{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":["pilotctl","jq"]},"homepage":"https://pilotprotocol.network"}}
allowed-tools	["Bash"]

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.