Content
78%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.
A lean, well-structured navigation hub: excellent conciseness and progressive disclosure with a verified, one-level reference table. Its main weakness is that the body itself is pure directory — it gives no concrete starting point, snippet, or task-level workflow, so a reader must open a reference before doing anything.
Suggestions
Add one concrete first step for the commonest task, e.g. 'Creating a figure from scratch: open tutorials.md and follow the walkthrough for your figure type; check api.md for signatures and PALETTE.'
Inline a minimal anchor of the house style (one short code or config snippet showing the palette import / export call) so the skill is actionable without opening a reference first.
State an ordering convention for the table (e.g. tutorials → common-patterns → api → design-theory → demos) so multi-reference tasks have an explicit sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~25 lines with zero padding: no matplotlib tutorials, no explanation of concepts Claude already knows. Phrases like 'Open `references/` only as needed; do not preload every file' and the compact two-column table mean every token earns its place. | 5 / 5 |
Actionability | The guidance is concrete as navigation ('Open when' conditions per file, e.g. 'references/api.md | Function signatures, `PALETTE`, validation rules') but the body contains no executable content itself — no code snippet, command, or concrete first step for actually producing a figure; everything actionable is deferred to references. This sits between anchor 4 ('mostly executable guidance') and the 'describes rather than instructs' end, landing on 3: some concrete guidance but incomplete in the body. | 3 / 5 |
Workflow Clarity | There is a clear navigation sequence — 'Start from the table below, then follow links inside the document you opened' — with explicit load conditions per reference. It is not a 5 because the body never sequences a figure-making task end-to-end (e.g. which reference to open first when creating a new figure), and there are no checkpoints; the simple-skill exception is partially earned since the single action (pick the right reference) is nearly unambiguous. | 4 / 5 |
Progressive Disclosure | Clear overview with a well-signaled, one-level-deep reference table; all five referenced files (tutorials.md, api.md, common-patterns.md, design-theory.md, demos.md) exist in references/ and contain the promised content (verified PALETTE in api.md, figure_* demos in demos.md). The body explicitly instructs progressive loading rather than preloading, and cross-links between references are surfaced rather than buried. This matches the anchor-5 example structure exactly. | 5 / 5 |
Total | 17 / 20 Passed |