Content
57%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 well-structured, appropriately short overview with excellent progressive disclosure to a real one-level reference, but it is padded with redundant/templated sections and its guidance stays high-level: no executable checks or named verification tooling appear in SKILL.md itself. Tightening the duplication and making the verify step concrete would lift the weaker dimensions.
Suggestions
Merge 'Quick Reference' into 'Check' and delete the intro sentence explaining why heading order matters, since Claude already knows this.
Add a concrete verification step with named tooling (e.g., 'Verify: run axe or Lighthouse, or inspect the accessibility tree, and confirm no level skips remain') instead of the vague 'browser accessibility tooling or assistive tech'.
Rewrite the templated 'Code Review' section in natural prose so the rule name is not awkwardly embedded ('...that affect Maintain logical heading order').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short but includes unnecessary material: an intro sentence explaining why heading order matters (a concept Claude already knows), a 'Quick Reference' section that largely duplicates 'Check', and templated filler such as 'Review the rendered markup and interactive states that affect Maintain logical heading order.' | 3 / 5 |
Actionability | There are concrete micro-examples ('check that an <h2> follows an <h1>', 'change an <h3> to an <h2> if it follows an <h1>') but no executable commands or specific tooling in the body — verification is deferred vaguely to 'browser accessibility tooling or assistive tech' without naming any tool. | 3 / 5 |
Workflow Clarity | The Check -> Fix -> Explain -> Code Review sequence is a coherent order for a simple single-purpose skill, but validation checkpoints are only implicit ('note how to verify the fix with browser accessibility tooling') with no explicit verify step or feedback loop in the body. | 3 / 5 |
Progressive Disclosure | The body is a concise overview with a single clearly signaled one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'); the reference file exists, contains the detailed material (code examples, best practices, verification), and nests no further. | 5 / 5 |
Total | 14 / 20 Passed |