CtrlK
BlogDocsLog inGet started
Tessl Logo

check-chokepoint-status

Retrieve live disruption status for the 13 monitored maritime chokepoints (Suez, Hormuz, Malacca, Bab el-Mandeb, Panama, and more). Use when the user asks whether a strait or canal is disrupted, congested, or safe for shipping right now.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, fully executable API skill: exact endpoint, auth, worked example, error recovery, and an unusually strong degradation contract that prevents misreading withheld data as zeros. The only structural note is that everything is inlined in SKILL.md with no bundle files, which is defensible for a single endpoint but leaves the response contract occupying a large share of the body.

DimensionReasoningScore

Conciseness

Every section earns its place — auth header, endpoint, one parameter, a compact response contract, one curl example, error codes, and scope boundaries. No padding or explanation of concepts Claude already knows; the response JSON even uses '…' placeholders to stay lean. Not below 5 since nothing reads as trimmable over-explanation.

5 / 5

Actionability

Fully executable throughout: exact endpoint URL, required header with example value, a copy-paste curl+jq worked example, a JMESPath projection example, and concrete error codes with retry guidance ('429 — rate limited; retry with backoff', '503 — retry once after 2s').

5 / 5

Workflow Clarity

This is a single-action skill (one GET) and the action is unambiguous with explicit validation-like checkpoints: the degradation contract tells the agent how to interpret each availability flag before trusting values, and the Errors section gives per-code recovery behavior. The 'When NOT to use' section cleanly routes misfit requests to the right endpoint.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and clearly signaled external references (OpenAPI, auth matrix, documentation). However, the ~100-line body is entirely inline — the 30-line response shape and degradation contract could live in a reference file — so it doesn't fully meet the simple-skill (under 50 lines) exception or the anchor-5 'content appropriately split' criterion.

4 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: concrete, third-person, explicitly scoped to 13 named chokepoints, with a clear 'Use when...' trigger clause covering the natural phrasings users would employ. Its only limitation is a single action verb, which slightly caps capability coverage rather than clarity.

DimensionReasoningScore

Specificity

The description states a concrete action — 'Retrieve live disruption status for the 13 monitored maritime chokepoints' — and grounds it with named instances (Suez, Hormuz, Malacca, Bab el-Mandeb, Panama). It stays at one primary action verb, so it doesn't reach the multi-action comprehensiveness of a 5, but it is well above the 1-2 generic actions of a 3.

4 / 5

Completeness

Both parts are explicit: 'what' is 'Retrieve live disruption status for the 13 monitored maritime chokepoints' and 'when' is 'Use when the user asks whether a strait or canal is disrupted, congested, or safe for shipping right now' — a concrete trigger phrase, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

'strait or canal', 'disrupted, congested, or safe for shipping' plus proper nouns (Suez, Hormuz, Malacca, Panama) cover the natural synonyms users would actually say. Coverage is comprehensive for this domain, including both generic terms and specific named instances.

5 / 5

Distinctiveness Conflict Risk

'Maritime chokepoint disruption status' is a clear niche with distinct trigger terms and named geographic instances; minimal overlap risk with any generic skill. No vague terms like 'helps with shipping data' appear.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
koala73/worldmonitor
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.