CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

track-vessel-traffic

Retrieve a point-in-time AIS vessel-traffic snapshot with disruption candidates and optional tanker overlay, filterable by bounding box. Use when the user asks what ships are in an area, or whether maritime traffic is disrupted.

Quality

92%

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

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

An exemplary API skill body: lean, fully executable, and rich in non-obvious operational knowledge (auth quirks, rate-limit warning, degradation contract, dark-fleet/transponder caveats) instead of generic explanation. The 'When NOT to use' routing section adds real value for skill selection.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout — it never explains what AIS, a bounding box, or JMESPath is, and every section carries only skill-specific facts ("Authorization: Bearer … is for MCP/OAuth or Clerk JWTs — not raw API keys", "per-IP limit is tighter here than most endpoints"). The only arguably trimmable text is the one-sentence intro restating the description and the brief content-safety paragraph, both of which still earn their place for an external-data skill.

5 / 5

Actionability

Fully executable, copy-paste-ready: the exact endpoint URL, the `X-WorldMonitor-Key` header with a realistic key format, a complete parameter table (names, shapes, limits), a runnable curl example with real Hormuz coordinates and jq post-processing, and concrete error responses with what to do (back off on 429). Nothing is pseudocode or hand-wavy.

5 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous: present the key header, GET the endpoint with the documented parameters, then interpret the result. It even includes interpretation checkpoints beyond the norm — the degradation contract ("empty/absent snapshot with fetchedAt: 0 … means 'no data', never 'no ships'") and the transponder-off caveat — plus explicit 401/429 recovery guidance.

5 / 5

Progressive Disclosure

No bundle files exist, and none are needed: the single SKILL.md is well-organized with clear section headers and nothing inline that belongs in a separate file (the parameter table and one worked example are exactly what an agent needs on every call). External references (OpenAPI operation `GetVesselSnapshot`, auth matrix) are clearly labeled in a References section and one level deep.

5 / 5

Total

20

/

20

Passed

Description

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

A strong description that answers what and when explicitly, with natural trigger phrasing and a clearly bounded niche. The only room for improvement is pulling a few more synonyms (e.g., shipping activity, tanker movements) into the description and sharpening the disruption trigger to avoid overlap with the chokepoint-status sibling skill.

DimensionReasoningScore

Specificity

"Retrieve a point-in-time AIS vessel-traffic snapshot with disruption candidates and optional tanker overlay, filterable by bounding box" names the domain and several concrete capabilities (candidates, tanker overlay, bbox filtering) in third-person imperative voice. It sits between anchor 3 (one–two concrete actions) and anchor 5 (multiple distinct actions) because the capability is a single retrieve action whose specifics are modifiers rather than a list of distinct actions.

4 / 5

Completeness

Both halves are explicit: the what ("Retrieve a point-in-time AIS vessel-traffic snapshot with disruption candidates and optional tanker overlay, filterable by bounding box") and the when ("Use when the user asks what ships are in an area, or whether maritime traffic is disrupted") with concrete trigger phrases — a direct match for the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural user phrasing is present — "what ships are in an area", "whether maritime traffic is disrupted" — plus technical terms (AIS, vessel-traffic, tanker). A few natural synonyms are missing from the description itself ("shipping activity", "vessel positions", "tanker movements" appear only in the body), which keeps it at good-not-comprehensive coverage per anchor 4.

4 / 5

Distinctiveness Conflict Risk

The AIS vessel-traffic niche is clear and distinct from generic skills, but the trigger "whether maritime traffic is disrupted" has minor overlap risk with the sibling chokepoint-status skill (which owns disruption aggregates per the body's own routing note). Mostly distinct with minor overlap against a closely related skill matches anchor 4 rather than anchor 5.

4 / 5

Total

17

/

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

Path

skills/track-vessel-traffic/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.