CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chokepoint-check

Check shipping disruption at maritime chokepoints such as Hormuz, Suez, Bab el-Mandeb, Malacca and Panama - vessel transits today, week-over-week change, risk level and incidents - from World Monitor. Use when the user asks whether a strait or canal is disrupted, congested or safe for shipping.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

The body is a model of token-efficient instruction writing: exact tool invocations, explicit data-integrity rules, and important negative guidance (riskSummary is always empty; do not invent baselines; no advice-giving). The only gap is the unspecified arguments for the conditional get_energy_intelligence call.

DimensionReasoningScore

Conciseness

At ~27 lines the body is lean and efficient: a tool table, three steps, and three rules with no concept explanations or padding — it never explains what a chokepoint is or why transit data matters. Every token earns its place, matching the 5 anchor.

5 / 5

Actionability

Step 1 is copy-paste concrete ("Call get_chokepoint_status with dataset: [\"transit-summaries\"]" plus exact name fragments "hormuz", "suez", "malacca", "bab", "panama"), and the guardrails are specific. Not a 5 because step 3 gives no parameters for get_energy_intelligence, leaving a minor executable gap.

4 / 5

Workflow Clarity

A simple single-purpose skill with a clear numbered sequence, explicit conditional branching, and explicit data-quality checkpoints ("State the observation time, and say so plainly when the data is stale or dataAvailable is false"). Per the simple-skill guidance the single action is unambiguous, and the stale-data/empty-field checks serve as validation; the 4 anchor's "minor validation gaps" does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed and no bundle files present, and the body is organized into clean Tools/Steps/Rules sections. Per the rubric guideline, this earns a 5 with just well-organized sections.

5 / 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 well-crafted: concrete capability enumeration, explicit third-person 'what' and 'when' clauses, named chokepoints as triggers, and a clearly bounded niche. Its only weakness is a minor coverage gap (the conditional energy-supply analysis in the body is absent).

DimensionReasoningScore

Specificity

Enumerates concrete capabilities — "vessel transits today, week-over-week change, risk level and incidents" — plus the data source ("from World Monitor"), which is several specific actions. Not a 5 because the conditional energy-disruption capability from the body is not mentioned, a minor coverage gap.

4 / 5

Completeness

Explicitly answers both: what ("Check shipping disruption at maritime chokepoints... vessel transits today, week-over-week change, risk level and incidents") and when ("Use when the user asks whether a strait or canal is disrupted, congested or safe for shipping"). This mirrors the 5 anchor's structure exactly; the 4 anchor requires a less explicit 'when', which is not the case here.

5 / 5

Trigger Term Quality

Covers natural terms users would say: named chokepoints ("Hormuz, Suez, Bab el-Mandeb, Malacca and Panama") plus synonyms "strait or canal" and "disrupted, congested or safe for shipping". This matches the comprehensive synonym coverage of the 5 anchor; the 4 anchor would require missing natural terms, which it does not.

5 / 5

Distinctiveness Conflict Risk

A clear niche (maritime chokepoint monitoring from a specific source) with distinct triggers — named straits and "disrupted, congested or safe for shipping" — making conflict with other skills minimal. Matches the 5 anchor's "clear niche with distinct triggers".

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

koala73/worldmonitor

Path

claude-plugin/skills/chokepoint-check/SKILL.md

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.