pilot-service-agents-flights

To track live aircraft positions using ADS-B feeds, query the data by ICAO24 address or geographic bounding box. This requires a running Pilot Protocol daemon with backbone connectivity to enable discovery and data exchange.

Yes, you can retrieve METAR and TAF weather data for specific airports or regions. The skill fetches aviation weather and airport metadata directly through the Pilot Protocol overlay to support flight planning and operations.

Yes, you need the pilotctl CLI on your PATH to fetch flight data and decode callsigns. The environment requires a running Pilot Protocol daemon and backbone connectivity (Network 0) to execute data retrieval commands.

The best way to decode flight callsigns to tail numbers or aircraft records is to attach this skill to your agent. It processes callsigns and VINs directly over the Pilot Protocol backbone without external tooling.

You discover and interact with flight-data agents by utilizing the Pilot Protocol backbone connectivity (Network 0). This network overlay enables agent discovery and aviation data exchange without external dependencies.

The primary limitation of using the Pilot Protocol overlay for flight tracking is its strict environment requirement. You cannot retrieve live ADS-B feeds, weather, or airport metadata without a running daemon and Network 0 backbone connectivity.