Tencent SkillHub · Developer Tools

Air France - KLM

Track Air France flights using the Air France–KLM Open Data APIs (Flight Status). Use when the user gives a flight number/date (e.g., AF007 on 2026-01-29) and wants monitoring, alerts (delay/gate/aircraft changes), or analysis (previous-flight chain, aircraft tail number → cabin recency / Wi‑Fi). Also use when setting up or tuning polling schedules within API rate limits.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: README.md, scripts/aircraft_intel.mjs, scripts/afkl_watch_flight.mjs, scripts/afkl_flightstatus_query.mjs, scripts/afkl_http.mjs, SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.1

Provenance

Publisher: iclems
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 5 sections Open source page

Quick start (one-off status)

Create an API key (and optional secret) Register on: https://developer.airfranceklm.com Subscribe to the Open Data product(s) you need (at least Flight Status API) Generate credentials (API key; some accounts also provide an API secret) Provide API credentials (do not print them): Preferred: env vars AFKL_API_KEY (and optional AFKL_API_SECRET) Or files in your state dir (CLAWDBOT_STATE_DIR or ./state): afkl_api_key.txt (chmod 600) afkl_api_secret.txt (chmod 600, optional) Query flight status: Run: node skills/airfrance-afkl/scripts/afkl_flightstatus_query.mjs --carrier AF --flight 7 --origin JFK --dep-date 2026-01-29 Notes: Send Accept: */* (API returns application/hal+json). Keep within limits: <= 1 request/sec. When making multiple calls, sleep ~1100ms between them.

Start monitoring (watcher)

Use when the user wants proactive updates. Run: node skills/airfrance-afkl/scripts/afkl_watch_flight.mjs --carrier AF --flight 7 --origin JFK --dep-date 2026-01-29 What it does: Fetches the operational flight(s) for the date window. Emits a single message only when something meaningful changes. Also follows the previous-flight chain (flightRelations.previousFlightData.id) up to a configurable depth and alerts if a previous segment is delayed/cancelled. Polling strategy (default): 36h before departure: at most every 60 min 36h→12h: every 30 min 12h→3h: every 15 min 3h→departure: every 5–10 min (stay under daily quota) After departure: every 30 min until arrival Implementation detail: run cron every 5–15 min, but the script self-throttles using a state file so it won’t hit the API when it’s not time. The watcher prints no output when nothing changed (so cron jobs can send only when stdout is non-empty).

Input shorthand

Preferred user-facing format: AF7 demain / AF7 jeudi Interpretation rule: The day always refers to the departure date (not arrival). Implementation notes: Convert relative day words to a departure date in the user’s timezone unless the origin timezone is explicitly known. When ambiguous (long-haul crossing midnight), prefer the departure local date at the origin if origin is known. (For scripts, still pass --origin + --dep-date YYYY-MM-DD.)

Interpret “interesting” fields

See references/fields.md for: flightRelations (prev/next) places.* (terminal/gate/check-in zone) times.* (scheduled/estimated/latest/actual) aircraft (type, registration) “parking position” / stand-type hints (when present) Wi‑Fi hints and how to reason about cabin recency

Cabin recency / upgrade heuristics

When aircraft registration is available: Use tail number to infer sub-fleet and likely cabin generation. If data suggests older config (or no Wi‑Fi), upgrading can be more/less worth it. Be conservative: Open Data often doesn’t expose exact seat model; treat this as best-effort.

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

4 Scripts2 Docs

SKILL.md Primary doc
README.md Docs
scripts/afkl_flightstatus_query.mjs Scripts
scripts/afkl_http.mjs Scripts
scripts/afkl_watch_flight.mjs Scripts
scripts/aircraft_intel.mjs Scripts