Conciseness

The body is efficient — parameter table, compact response shape, one worked example, terse error list. But the opening paragraph ('Use this skill when the user asks about airport disruption… Alerts carry IATA/ICAO codes, delay type, severity, and quantified impact') restates the frontmatter description, and the 'Content safety' section gives generic guidance — minor trimmable instances matching anchor 4 rather than anchor 5's 'every token earns its place'.

Actionability

Fully executable, copy-paste ready: the exact endpoint ('GET https://api.worldmonitor.app/api/aviation/v1/list-airport-delays'), the auth header ('X-WorldMonitor-Key: $WM_API_KEY'), a complete curl example piped to jq with a concrete filter, a full response JSON sample, and named error codes with remedies. Matches anchor 5.

Workflow Clarity

A simple single-purpose skill (one authenticated GET call) whose single action is unambiguous, so the simple-skill exception applies; it is read-only, so the destructive/batch validation cap does not. Error recovery is explicit ('429 — rate limited; retry with backoff') and the 'When NOT to use' section cleanly routes edge cases to sibling endpoints. Anchor 5 fits.

Progressive Disclosure

No bundle files exist, so nothing is inlined that should be split; the body is organized into clear sections (Authentication, Endpoint, Parameters, Response shape, Worked example, Errors, When NOT to use, References) and pointers are one level deep and clearly signaled ('OpenAPI: …operation ListAirportDelays', 'Auth matrix: …'). Matches anchor 5's clear overview with well-signaled references.

Specificity

Names the domain and a concrete action ('Retrieve current airport delay and cancellation alerts worldwide') and fully enumerates the returned data ('delay type, severity, average delay minutes, and affected-flight percentages per airport'). It stops short of anchor 5 because it describes a single retrieve action rather than multiple specific concrete actions, and omits capability details like region filtering.

Completeness

Explicitly answers both what ('Retrieve current airport delay and cancellation alerts worldwide — delay type, severity, average delay minutes, and affected-flight percentages per airport') and when ('Use when the user asks whether an airport is delayed, disrupted, or experiencing cancellations') with concrete trigger phrases — a direct match for anchor 5.

Trigger Term Quality

'Use when the user asks whether an airport is delayed, disrupted, or experiencing cancellations' covers natural user phrasings well, but misses common variations such as 'flight delays', 'airport status', or 'how bad is the weather at X airport'. Good coverage with a few natural terms missing — anchor 4, not comprehensive enough for anchor 5.

Distinctiveness Conflict Risk

'airport delay and cancellation alerts worldwide' carves out a clear niche distinct from flight-status, carrier-ops, or general aviation skills, and the triggers ('delayed, disrupted, or experiencing cancellations') are domain-specific with minimal overlap risk. Anchor 5 fits.