Pilot Service Agents Transit

Public-transit schedules and live data — Amtrak, BART, Deutsche Bahn, Swiss SBB, BC Ferries, BVG Berlin, and more. Use this skill when: 1. Live train / ferry...

Security Scan

The skill is internally consistent with its stated purpose: it is an instruction-only transit data client that expects the pilotctl CLI and a Pilot Protocol daemon/overlay; it does not request unrelated credentials or install arbitrary code.

Purpose & Capability

The name/description (transit schedules, multi-modal journeys, stop lookups) match the declared requirements: pilotctl on PATH, the pilot-protocol core skill, and a running daemon joined to network 9. These requirements are proportionate to a networked service-agent client.

Instruction Scope

SKILL.md only instructs use of pilotctl commands (send-message, inbox, /help, /data, /summary) against listed transit agents and to parse inbox JSON. It does not direct reading of unrelated files, environment variables, or system configuration. Note: it requires the agent to communicate over a peer overlay (network 9) and to query remote agents/upstream URLs, which is expected for this purpose but does involve network I/O and remote responses.

Install Mechanism

No install spec and no code files — lowest-risk instruction-only skill. It only requires an existing pilotctl binary; nothing is downloaded or written by the skill itself.

Credentials

No environment variables or credentials are requested. The skill's declared requirements (pilotctl and pilot-protocol daemon) explain the needed permissions; there are no unexplained SECRET/TOKEN/PASSWORD requests.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request permanent presence or modify other skills. The agent may invoke the skill autonomously per platform defaults, which is normal.

Assessment

This skill appears coherent for querying transit data via the Pilot Protocol. Before installing: (1) ensure you trust the pilotctl binary and pilotprotocol network — the skill requires joining an overlay (network 9) and will exchange messages with remote agents, which may expose metadata about queries and responses; (2) confirm you have the pilot-protocol daemon and understand its network/peer implications; (3) if you want to be extra cautious, run the daemon and pilotctl in a sandbox or inspect the pilotctl source/packaging; (4) there are no credentials requested by this skill, but check any upstream agents you query if you expect sensitive data not to be forwarded.

Public-transit schedules and live data — Amtrak, BART, Deutsche Bahn, Swiss SBB, BC Ferries, BVG Berlin, and more.

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
amtrak-stations	Amtrak train schedules by station (unofficial)
bart-etd	Bart Etd
bcferries-capacity	BC Ferries sailing capacity & schedule
bvg-berlin-departures	Berlin BVG live departures by stop
entur-geocoder	Norway national transit geocoder
gbfs-bluebikes-boston	Gbfs Bluebikes Boston
gbfs-capitalbikeshare-dc	Gbfs Capitalbikeshare Dc
gbfs-divvy-chicago	Gbfs Divvy Chicago
gbfs-lyft-bayarea	Gbfs Lyft Bayarea
gbfs-toronto-bikeshare	Gbfs Toronto Bikeshare
irail-liveboard	Belgian SNCB live rail departures
mbta-routes	Mbta Routes
mbta-stops	Mbta Stops
mta-nyc-subway-stations	NYC MTA subway station metadata
swiss-transport-connections	Swiss public transport connection search
tfl-stoppoint-meta	TfL stop point category metadata
transport-rest-journeys	Deutsche Bahn multi-modal journey planner
transport-rest-stations	Deutsche Bahn station search

What you can expect

• Multi-country rail and transit: US (Amtrak, BART), Germany (DB, BVG), Switzerland, Belgium (iRail), Norway (Entur)
• Real-time departure boards and delay data where the upstream exposes it

What NOT to expect

• Rideshare / taxi availability
• Fare-payment or ticketing flows — read-only

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

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

# 3. Query it
pilotctl --json send-message bart-etd --data '/data {"orig":"POWL"}'
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.