Pilot Service Agents Data

General open-data APIs that didn't fit a narrower category — PubChem compounds/substances, REST Countries full catalog. Use this skill when: 1. Compound or s...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (querying Pilot Protocol data agents via pilotctl); it does not request unrelated credentials or install code, but it does send user-supplied queries over an overlay network so avoid including secrets in queries.

Purpose & Capability

Name/description match the requested artifacts: the skill is an instruction-only wrapper for Pilot Protocol 'data' agents (PubChem, REST Countries) and legitimately requires the pilotctl binary, the pilot-protocol core skill, and a running daemon on the data-exchange network. No unrelated binaries or env vars are requested.

Instruction Scope

SKILL.md instructs the agent to run pilotctl send-message and pilotctl inbox to interact with overlay agents. That is within purpose, but these commands transmit whatever filters/queries the user provides onto the overlay network (and agents may return upstream URLs). Do not include secrets or private data in queries because the skill will forward them to peers.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. It relies on an existing pilotctl binary; installing/obtaining that binary (outside this skill) is the user's responsibility and should be verified from official sources.

Credentials

No environment variables, credentials, or config paths are requested. The declared requirements (pilotctl, daemon joined to network 9, list-agents reachable) align with the stated function.

Persistence & Privilege

always:false and default invocation settings — the skill does not request forced or persistent privileges, nor does it modify other skills or system-wide settings.

Assessment

This skill is internally consistent: it simply tells the agent to use pilotctl to query Pilot Protocol data agents. Before installing, ensure you already run a trusted pilotprotocol daemon and have an authentic pilotctl binary (verify source). Never include passwords, API keys, or other secrets in queries/filters — those strings will be transmitted to overlay peers. Be aware responses may include upstream URLs; inspect them before following. If you do not run Pilot Protocol or do not trust the network/peers on network 9, do not enable this skill.

General open-data APIs that didn't fit a narrower category — PubChem compounds/substances, REST Countries full catalog.

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
pubchem-compound-search	PubChem compound search — CID/SID/name lookup
pubchem-substance-search	PubChem substance search — name/CAS/SID lookup
restcountries-all	REST Countries — full country catalog

What you can expect

• Broad-catalog queries for exploratory use

What NOT to expect

• Narrow-domain queries — each agent covers a large dataset at coarse grain

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":"data","limit":20}'
pilotctl --json inbox

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

# 3. Query it
pilotctl --json send-message restcountries-all --data '/data {"fields":"name,capital,currencies"}'
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.