Content
100%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |