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 single-file API skill: everything needed to make a correct authenticated call is present exactly once, with no padding, an executable worked example, an explicit degradation contract that prevents the worst misinterpretation (reading no-data as no-ships), and clear routing to sibling skills for adjacent use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean throughout: a parameter table instead of prose, a compact response shape, and no explanation of concepts Claude already knows (AIS, curl, JMESPath, HTTP errors). The one borderline section ("Content safety") earns its tokens for an external-data API. Matches the 5-anchor — every section carries non-obvious information. | 5 / 5 |
Actionability | Fully executable: exact endpoint URL, exact auth header with a realistic key format, a copy-paste-ready worked example (curl --get with --data-urlencode piped to jq), and concrete error responses with an action (429 → back off). Matches the 5-anchor's "copy-paste ready… covers the common cases". | 5 / 5 |
Workflow Clarity | A simple single-task skill (one GET request) whose single action is unambiguous — the rubric's simple-skill exception applies. It also includes the feedback/failure handling the anchors reward: the degradation contract ("no data, never 'no ships'") and per-error guidance. Not a destructive or batch operation, so no validation cap applies. | 5 / 5 |
Progressive Disclosure | No bundle files exist; the ~74-line single-purpose body is well-sectioned (Auth → Endpoint → Parameters → Response → Example → Errors → When NOT to use → References) with external references (OpenAPI, auth matrix) clearly signaled one level deep. Nothing inlined that clearly belongs in a separate file. | 5 / 5 |
Total | 20 / 20 Passed |