Content
71%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 well-organized, brief review skill that appropriately pushes detail to references/rule.md. It is weakest on actionability, since the body states what to check but keeps verification tooling generic and offloads executable specifics to the reference file.
Suggestions
Name a concrete verification tool inline (e.g., 'Use the HeadingsMap browser extension or axe DevTools to generate the heading outline') so the body is actionable without requiring the reference.
De-duplicate the 'never skip levels' and 'don't use headings for styling' rules across Quick Reference, Check, and Fix so each section adds distinct value.
Add a short feedback loop to the Check/Fix flow (e.g., 'Re-run the heading outline after fixes to confirm exactly one h1 and no skipped levels').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-sectioned, but the Quick Reference, Check, and Fix sections repeat the same rules ('never skip levels', 'don't use headings for styling'), so not every token earns its place. | 4 / 5 |
Actionability | Concrete checks are named ('verify exactly one h1', 'sequential order', 'generate a heading outline') but verification tooling is left generic ('accessibility tools', 'browser accessibility tooling or assistive tech') with the executable specifics deferred entirely to references/rule.md. | 3 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence with a Quick Reference checklist serves as the validation checkpoint, though there is no explicit feedback loop for error recovery. | 4 / 5 |
Progressive Disclosure | A concise overview body with a single, clearly signaled one-level-deep reference ('see references/rule.md') that exists in the bundle and holds the detailed code examples and framework guidance. | 5 / 5 |
Total | 16 / 20 Passed |