sigint-osint-feeds

Ingest ADS-B, AIS, and APRS feeds into PostGIS geospatial events.

8|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drewid74/ai_skills --skill sigint-osint-feeds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sigint-osint-feeds
Source: https://github.com/drewid74/ai_skills/tree/main/sigint-osint-feeds
Command: npx skills add https://github.com/drewid74/ai_skills --skill sigint-osint-feeds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you keep SIGINT/OSINT feed ingestion reliable and fast while turning high-volume, multi-source signals into correlated, geospatially searchable events.

Core Features & Use Cases

  • Decoupled feed ingestion: Use an async, fault-tolerant worker design so one failing source doesn’t block the event pipeline.
  • Real-time geospatial event storage: Normalize events into a common schema with PostGIS geography types for accurate Earth-surface distance.
  • Cross-source correlation and anomaly alerts: Link entities across callsigns and identifiers, flag spatial/temporal overlaps, and enqueue anomalies for downstream processing.
  • High-volume deduplication: Apply Bloom-filter style dedup at ingestion to reduce database write load and keep dashboards responsive.
  • Use case: Monitor aircraft and vessel movements by ingesting ADS-B, AIS, and APRS streams, then correlate overlapping sightings into confidence-scored alerts on a live dashboard.

Quick Start

Use the sigint-osint-feeds skill to set up a Redis Streams–based ingestion pipeline that normalizes and correlates streaming and polling RF/OSINT sources into PostGIS-backed, near-real-time geospatial alerts.

Frequently Asked Questions about sigint-osint-feeds

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

FAQPage Schema
How do I build a real-time OSINT feed ingestion pipeline for ADS-B and AIS data?

Deduplicate high-volume SIGINT feeds by applying Bloom-filter style deduplication at the ingestion layer, which reduces database write load and keeps operational dashboards responsive during peak event rates.

How does geospatial correlation work for multi-source SIGINT tracking data?

Redis Streams supports SIGINT stream ingestion by providing replayable delivery, ensuring that asynchronous workers can recover from failures without losing high-volume OSINT tracking events during pipeline processing.

Do I need PostGIS to store and query correlated OSINT events accurately?

To set up near-real-time geospatial alerts, configure a Redis Streams-based ingestion pipeline that normalizes streaming RF sources, correlates spatiotemporal events, and outputs confidence-scored alerts to a live dashboard.

What is the best way to handle asynchronous ingestion when one OSINT feed source fails?

Limitations of high-volume stream ingestion include database write bottlenecks and blocking pipelines; mitigate these by using Bloom-filter style deduplication and decoupled asynchronous workers with backoff and jitter.