Pilot Service Agents Flights

Aircraft tracking and aviation weather — ADS-B feeds (ICAO + bbox), airport directory, METAR/TAF/SIGMET. Use this skill when: 1. Live aircraft positions by I...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (using pilotctl to query flight/aviation agents), but it implicitly depends on a local pilotctl daemon and its configuration (potentially containing keys) which the SKILL.md does not explicitly declare—so proceed with awareness of that local dependency.

Purpose & Capability

Name/description (ADS‑B, METAR/TAF, airport data) match the declared runtime requirements: pilotctl binary on PATH, pilot-protocol core skill, and a daemon joined to network 9. Requiring pilotctl is appropriate for a skill that drives Pilot Protocol agents.

Instruction Scope

SKILL.md instructs the agent to run pilotctl commands (send-message, inbox, list-agents, etc.) and to interact with overlay agents. It does not instruct reading arbitrary user files or env vars, but it implicitly assumes access to a running pilotctl daemon and its local state (socket/config files). The skill does not declare or document whether pilotctl will read local keys/configs—this implicit local access is a scope concern to verify before use.

Install Mechanism

No install spec — instruction-only. That minimizes disk-write/install risk. The skill relies on an existing pilotctl binary rather than fetching code or running downloads.

Credentials

The skill requests no environment variables or credentials, which is proportionate. However, pilotctl/pilot‑protocol daemons often use local configuration, sockets, or key material; these are not declared. Confirm pilotctl's config locations and any keys the daemon may expose before running the skill.

Persistence & Privilege

always:false and default autonomous invocation are appropriate. The skill does not request to modify other skills or system-wide agent settings and has no install-time persistence behaviors.

Assessment

This skill appears to do what it says: it runs pilotctl to discover and query flight and weather agents. Before installing, verify you trust the pilotctl binary and the Pilot Protocol network you will join. Specifically: (1) confirm where pilotctl stores its config/keys on your system and whether a running daemon exposes any credentials or sockets you don't want the agent to access; (2) ensure the daemon you join (network 9) is intended and trusted; (3) if you need stronger isolation, run pilotctl and the daemon in a sandbox or VM, or inspect the pilot-protocol core skill and pilotctl documentation for config/key locations. If you want higher assurance, ask the skill author for explicit documentation of any local config or key usage.

Aircraft tracking and aviation weather — ADS-B feeds (ICAO + bbox), airport directory, METAR/TAF/SIGMET.

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
adsb-lol-icao	Live ADS-B aircraft by ICAO24 hex
adsb-lol-latlon	Live ADS-B aircraft within N nm of a point
adsbdb-aircraft	ADSBdb aircraft registration lookup
adsbdb-callsign	ADSBdb flight route / aircraft / callsign lookup
airport-data	Airport-Data.com airport metadata by ICAO
aviation-weather-airsigmet	AIRMETs and SIGMETs worldwide
aviation-weather-metar	Aviation Weather Center METAR observations worldwide
aviation-weather-taf	Aviation Weather Center TAF terminal forecasts

What you can expect

• Open ADS-B feeds (adsb.lol + ADSBdb) with no auth
• Aviation Weather Center (METAR, TAF, AIRMETs, SIGMETs) keyed by station or region
• Airport metadata by ICAO

What NOT to expect

• Guaranteed 100% coverage — ADS-B depends on receiver density
• Proprietary radar or military-restricted feeds

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

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

# 3. Query it
pilotctl --json send-message aviation-weather-metar --data '/data {"ids":"KSFO,KSJC"}'
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.