aviation-military-intel

Ingest aviation and maritime telemetry data into a unified AviationTrack schema.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill aviation-military-intel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aviation-military-intel
Source: https://github.com/ShubhamManachekar/GeoSupply/tree/main/.agent/skills/aviation-military-intel
Command: npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill aviation-military-intel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingests aviation and maritime telemetry data to support supply chain stability, ensuring FA v2 compliant processing and secure data handling with OAuth2-based authentication and structured transformation.

Core Features & Use Cases

  • OpenSky OAuth2-based ingestion for ADS-B and AIS streams with proactive token management and 403/rate-limit handling.
  • AviationWorker transforms 18-element OpenSky state vectors into AviationTrack schema for downstream analytics.
  • AISWorker maintains WebSocket connectivity with auto-reconnect, 60s heartbeats, and SQLite-based buffering to handle data gaps.
  • Data quality and classification: validate MMSI values and classify tracks as military, cargo, or tanker; enforce geographic bounds per Indian EEZ.

Quick Start

Initialize and run the OpenSky OAuth2 flow to start ingesting ADS-B and AIS data and observe real-time tracks.

Frequently Asked Questions about aviation-military-intel

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

FAQPage Schema
How do I ingest ADS-B and AIS telemetry data using OAuth2 authentication?

The pipeline ingests ADS-B and AIS telemetry using OpenSky OAuth2 for token management, proactively handling 403 and rate-limit errors to maintain a secure and continuous data stream.

How does WebSocket handling maintain maritime AIS data connectivity during network drops?

Maritime AIS WebSocket connectivity is maintained via auto-reconnect protocols and 60-second heartbeats, utilizing SQLite-based buffering to preserve data integrity during network interruptions.

How are OpenSky state vectors transformed for downstream supply chain analytics?

OpenSky state vectors are processed by an AviationWorker that transforms the 18-element arrays into a unified AviationTrack schema, enabling structured downstream supply chain analytics.

Can I classify telemetry tracks as military, cargo, or tanker and enforce geographic bounds?

Yes, the pipeline validates MMSI values and classifies tracks as military, cargo, or tanker, while strictly enforcing geographic bounds per the Indian EEZ for data quality assurance.

Does this aviation and maritime data pipeline require external dependencies to run?

No, the pipeline operates with zero external dependencies, handling OAuth2 authentication, WebSocket ingestion, and SQLite buffering internally to ensure FA v2 compliant processing.

Why does my OpenSky data ingestion fail with 403 or rate-limit errors?

OpenSky ingestion 403 or rate-limit errors occur when authentication fails or API thresholds are exceeded; the pipeline mitigates this through proactive OAuth2 token management and automated retry handling.