Content
96%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.
The body is a lean, highly actionable workflow with clear sequencing, explicit validation checkpoints, a feedback loop, and a completion checklist — matching the good-example pattern. The only structural improvement is moving the DESIGN.md section contract into a referenced template file to tighten progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is operational — use-when bullets, a scoped relationship note, a five-step workflow, and a completion checklist — with no explanations of concepts Claude already knows. The 14-section contract list is dense but is itself the required deliverable content, so every token earns its place (anchor 5). | 5 / 5 |
Actionability | The guidance is fully executable for an instruction-only skill: exact required DESIGN.md sections with contents specified per section (e.g. "Status (Draft | Active | Needs refresh), date, product surfaces, evidence reviewed"), explicit interview topics, and explicit prohibitions ("Do not invent a parallel design-system layer"). Per the scoring notes, absence of code is not penalized when the guidance is this concrete. | 5 / 5 |
Workflow Clarity | The five-step workflow (discover → interview → create/refresh → apply → handoff) has explicit validation checkpoints: "Separate observations from inferences; note absent evidence", a feedback loop ("update the file or add an open question when implementation exposes a contradiction"), and a completion checklist ("Complete only when design docs/assets/components/screenshots were inspected or noted absent..."). This matches the anchor-5 pattern of clear sequence with explicit validation and checklists; there are no destructive or batch operations that would impose a cap. | 5 / 5 |
Progressive Disclosure | The single file is well-organized with clear sections, and its one external reference (templates/AGENTS.md) is clearly signaled one level deep. It falls short of 5 because no bundle files exist while the 14-section DESIGN.md contract is arguably template material belonging in a separate reference file, and the referenced path (../../templates/AGENTS.md) lives outside the skill directory, leaving a minor organization gap (anchor 4). | 4 / 5 |
Total | 19 / 20 Passed |