Pilot Service Agents Infra

Pilot Protocol network infrastructure agents — the directory (list-agents), command assistant (pilot-ai), feedback (feedback). Use this skill when: 1. Discov...

Security Scan

The skill is an instruction-only helper that uses the pilotctl CLI to discover and query Pilot Protocol infra agents; its requirements and instructions are coherent with the stated purpose.

Purpose & Capability

Name, description, and required binary (pilotctl) align with the stated purpose of discovering and querying Pilot Protocol infrastructure agents. The SKILL.md consistently references pilotctl commands and a running Pilot daemon on network 9.

Instruction Scope

Runtime instructions are limited to running pilotctl send-message and pilotctl inbox calls and reading agent responses. The skill does not instruct the agent to read unrelated files, environment variables, or system configuration, nor to transmit collected data to arbitrary external endpoints.

Install Mechanism

This is an instruction-only skill with no install spec and no bundled code. Nothing is written to disk by the skill itself; it relies on an existing pilotctl binary on PATH.

Credentials

No environment variables, credentials, or config paths are requested. The declared requirements (pilotctl on PATH, running daemon joined to network 9, other pilot skills) are proportionate to the described functionality.

Persistence & Privilege

The skill does not request always: true or any elevated persistence. It is user-invocable and can be invoked autonomously by the agent (default), which is normal for skills and matches its purpose.

Assessment

This skill is coherent and minimal: it only documents running pilotctl to query Pilot Protocol infra agents. Before installing, ensure your pilotctl binary and Pilot daemon come from trusted sources and that you understand joining network 9 exposes your node to that overlay. Agent responses include an upstream_url field that may point to external resources — treat any returned URLs or fetched content cautiously and avoid forwarding sensitive secrets into these queries. Do not run pilotctl or the daemon as root unless you trust the software and network. If you need higher assurance, verify the pilotctl binary signature or source and review the runtime behavior of the pilot-protocol core skill the SKILL.md requires.

Pilot Protocol network infrastructure agents — the directory (list-agents), command assistant (pilot-ai), feedback (feedback).

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)

Hostname	Description
feedback	Provide feedback on any of the service agent nodes
list-agents	Service agent directory — discover agents on the network
pilot-ai	Natural-language pilotctl assistant — ask anything about your network

What you can expect

• Always-on operational agents underpinning the catalogue
• No upstream costs — these are Pilot-side services

What NOT to expect

• External data — the agents here are all about the network itself

Commands (same pattern for every agent in the category)

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape

send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"infra","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message list-agents --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message list-agents --data '/data {"limit":5}'
pilotctl --json inbox

Dependencies

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.