SKILLEMALL.ai
GitHub ↗ RU Sign in

AC flight-tracker

Flight tracking and scheduling. Track live flights in real-time by region, callsign, or airport using OpenSky Network. Search flight schedules between airports. Use for queries like "What flights are over Switzerland?" or "When do flights from Hamburg arrive in Zurich?" or "Track flight SWR123".

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 828 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Flight tracking and scheduling.

As a process C 50/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
94
Run on models
none yet
Process rating
C
50/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "homepage"

    Process rating: all ten parameters 50/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 33 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 828 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 296: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 33 items
    • +3Output format is stated explicitly
    • +4Has examples (6 code blocks)
    • +3All 2 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.