external-client-add

Integrate external HTTP data sources into FlightJar enrichment with typed HttpClients and gzip caching.

55|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/MrSuttonmann/flightjar --skill external-client-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-client-add
Source: https://github.com/MrSuttonmann/flightjar/tree/main/.claude/skills/external-client-add
Command: npx skills add https://github.com/MrSuttonmann/flightjar --skill external-client-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate external HTTP data sources into the FlightJar enrichment pipeline using typed HttpClients and CachedLookup with on-disk gzip caching and rate-limiting.

Core Features & Use Cases

  • Typed HttpClient per upstream source with a standard caching and throttling pattern.
  • CachedLookup + disk cache + 429 throttle to guard against rate limits and ensure offline resilience.
  • Use cases include adding sources like FlightRadar24, NOAA winds aloft, or OurAirports runway data; these are wired into the snapshot enrichment, without bundling local reference data.

Quick Start

Add a new typed HttpClient for the upstream source, wire it into the snapshot enrichment, and enable it via configuration.

Frequently Asked Questions about external-client-add

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

FAQPage Schema
How do I add an external HTTP data source to a .NET enrichment pipeline?

You can add an external HTTP data source to a .NET enrichment pipeline by wiring a typed HttpClient into the snapshot enrichment process, enabling it via app configuration to fetch upstream data like weather or airport metadata.

How does on-disk gzip caching work for upstream API lookups?

On-disk gzip caching stores upstream API lookup results locally with a schema version and TTL, providing offline resilience and preventing redundant network requests when enriching data snapshots.

How do I handle HTTP 429 throttling when integrating external data feeds?

Handle HTTP 429 throttling by implementing a CachedLookup pattern with per-key deduplication, which guards against upstream rate limits and ensures stable data fetching during enrichment.

Can I configure external data fetching to be toggled on or off via app options?

Yes, external data fetching is configurable via app options, allowing you to enable or disable specific upstream sources and preserving existing enrichment behavior when a source is not needed.

What is the best way to enrich snapshots with flight data without bundling local reference databases?

The best way to enrich snapshots without bundling local reference databases is to use typed HttpClients with CachedLookup, fetching upstream data like FlightRadar24 or NOAA winds aloft on demand with on-disk caching.

Does this external client integration support per-key deduplication for concurrent lookups?

Yes, the external client integration supports per-key deduplication, ensuring that concurrent lookup requests for the same data key do not trigger multiple upstream HTTP calls during the enrichment process.