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.
The body is a well-structured, token-efficient overview that delegates implementation detail to a real, one-level-deep reference file — exemplary progressive disclosure. Its weakness is actionability: the in-body guidance names what to check and fix but provides no detection technique or example, relying entirely on the reference for executable detail.
Suggestions
Add one concrete detection cue to the Check section, e.g. an example of the offending markup (<h2></h2>, whitespace-only, or icon-only headings) or a tool reference like axe's 'empty-heading' rule, so the check is executable without opening the reference.
Merge or differentiate the Quick Reference bullets from the Check/Fix sections to remove duplication and tighten the workflow.
Trim the '## Explain' section ('Explain why meaningful heading content is vital for document navigation and accessibility') — it is a directive that adds no actionable content beyond what Check and Fix already convey.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with one-line Check/Fix sections and no explanation of concepts Claude already knows, but the '## Explain' section and the generic 'Code Review' boilerplate paragraph are trimmable padding. | 4 / 5 |
Actionability | Check and Fix give specific direction ('Find any heading tags (h1 through h6) that are empty or contain only non-perceivable whitespace', 'Add descriptive text content to the empty heading or remove the heading tag'), but there is no detection method (selector, axe rule, grep pattern), no example markup, and all code examples are delegated to the reference file. | 3 / 5 |
Workflow Clarity | As a simple single-task skill the Check → Fix → verify flow is discernible and verification is mentioned ('note how to verify the fix with browser accessibility tooling or assistive tech'), but the sequence is only implied by section order and the Quick Reference bullets duplicate the Check/Fix content. | 4 / 5 |
Progressive Disclosure | The body is a concise overview with a clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists and contains exactly the promised detail, with the split appropriately made. | 5 / 5 |
Total | 16 / 20 Passed |