pilot-service-agents-traffic

Coordinate live transit and bike-share data across agents via pilotctl.

7|3|Updated Apr 8, 2026

Search Tags:#real-time #transit #pilotctl #service-agents #gbfs #citybikes #tfl

Ready to run

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-traffic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pilot-service-agents-traffic
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-service-agents-traffic
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-traffic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate live transit and bike-share data across agents.

Core Features & Use Cases

Unified access to CityBikes GBFS feeds and TfL line statuses/arrivals across multiple agents.
Real-time data discovery and querying via pilotctl to support transit-aware dashboards and routing.
Scalable cataloging of multiple operators and networks within a single agent ecosystem.

Quick Start

Install the Pilot Protocol daemon, ensure the backbone is joined, and start querying transit agents with pilotctl.

Frequently Asked Questions about pilot-service-agents-traffic

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

FAQPage Schema

How do I coordinate live transit data across multiple agents?▼

To coordinate live transit data across multiple agents, you apply this Skill in urban mobility contexts to unify GBFS feeds and TfL line statuses. It requires a running pilot-protocol daemon, the core skill, and pilotctl on PATH connected to the backbone.

Can I query CityBikes and TfL arrivals together using pilotctl?▼

Yes, you can query CityBikes GBFS feeds and TfL line statuses together using pilotctl. This Skill provides real-time data discovery across multiple operators and networks to support transit-aware dashboards within a single agent ecosystem.

What is needed to access real-time bike-share data via pilotctl?▼

Accessing real-time bike-share data via pilotctl requires a running pilot-protocol daemon connected to the backbone (Network 0), the pilot-protocol core skill, and pilotctl installed on your PATH to query the transit agents.

Does this Skill support querying multiple GBFS feeds simultaneously?▼

Yes, this Skill supports querying multiple GBFS feeds simultaneously by scalable cataloging of multiple operators and networks. It enables unified access to CityBikes data and TfL line statuses across multiple agents within a single ecosystem.

Why does my pilotctl transit query require the pilot-protocol daemon?▼

Your pilotctl transit query requires the pilot-protocol daemon because it provides the backbone (Network 0) connection needed to route real-time data discovery and querying across the distributed transit agents in your ecosystem.

What are the limitations when using pilotctl for real-time transit data?▼

Limitations when using pilotctl for real-time transit data include the strict requirement for the pilot-protocol daemon and core skill to be running, and your environment must be connected to Network 0 to successfully catalog and query operators.