pilot-service-agents-transit

Query transit agents over the Pilot Protocol network for live schedules and multi-modal connections.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-transit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-service-agents-transit
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-service-agents-transit
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-transit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Public transit data is scattered across providers and formats; this skill aggregates live schedules and multi-modal connections via Pilot Protocol agents to help plan trips.

Core Features & Use Cases

  • Discover and query transit agents in the backbone to fetch live schedules, departures, and stop-level data.
  • Plan multi-modal journeys across providers (Amtrak, DB, SBB, BVG, etc.) and retrieve station directories.
  • Use-case: generate a route from a station A to B with transfer points and ETAs using overlay data.

Quick Start

Install the skill with clawhub, start the Pilot daemon, and begin querying transit agents for live schedules.

Frequently Asked Questions about pilot-service-agents-transit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan multi-modal journeys across different public transit providers?

To discover transit agents, query a list-agents directory agent accessible on the overlay network. This returns a directory of registered transit agents providing live schedules and stop-level data for cross-system routing.

What do I need to fetch live transit schedules over the Pilot Protocol?

Yes, stop-level lookups are supported for providers like Amtrak, DB, BVG, SBB, and Entur geocoder data. You can query transit agents to retrieve live departures and detailed stop-level schedule information.

How do I retrieve live public transport departures using an agent-discovery protocol?

Multi-modal transit routing differs from static schedule APIs by aggregating live data from scattered providers dynamically via overlay agents. It provides real-time departures and cross-system connections rather than relying on fixed timetable data.

Does this approach work with Amtrak, DB, SBB, and BVG transit data simultaneously?

To start querying transit agents, install the skill with clawhub, start the Pilot daemon registered with the backbone, and use the agent directory to discover available transit agents for live schedule queries.