Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The SKILL.md body is a well-structured, lean overview that correctly defers detail to a real, one-level-deep reference file. Its main weaknesses are actionability and workflow clarity: the Check/Fix guidance is somewhat abstract and lacks an inline verification checkpoint, even though the reference file contains a thorough Verification section.
Suggestions
Tighten the Check and Fix sections into concrete, criteria-based steps (e.g. "List each <div> used for page structure and state the semantic element it should become") rather than descriptive instructions.
Add a brief inline verification checkpoint in the body (e.g. "Confirm exactly one <main> per page and that no <div> carries a landmark role") so the workflow has an explicit validation step before deferring to references/rule.md.
Pull one small concrete anti-pattern/example pair into the body so the review guidance is immediately actionable without needing to open the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean: short Quick Reference bullets and brief Check/Fix/Explain/Code Review sections with no padding; the single opening sentence frames the purpose without explaining concepts Claude already knows at length, so every token earns its place. | 3 / 3 |
Actionability | The Quick Reference gives concrete element mappings ("Use <article> for self-contained content", "Only one <main> per page"), but the Check and Fix sections are descriptive ("Review this HTML structure to ensure it uses appropriate semantic elements...", "Replace generic div elements with semantic HTML5 elements") rather than providing concrete, copy-ready review procedures or criteria. | 2 / 3 |
Workflow Clarity | The Check/Fix/Explain/Code Review sections imply a loose sequence, but no explicit validation or verification checkpoint is present in the body — verification is deferred to the reference file rather than stated inline, leaving the workflow sequence without an explicit checkpoint. | 2 / 3 |
Progressive Disclosure | The body is a concise overview that clearly signals a single one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), and that file exists and holds the detailed material, matching the score-3 anchor for well-signaled one-level references. | 3 / 3 |
Total | 10 / 12 Passed |