Content
63%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 well-organized with a clean Check/Fix/Explain/Code Review flow and exemplary progressive disclosure, delegating details to a real one-level-deep reference. Its weaknesses are redundancy — the single-h1/no-skipped-levels rule is restated across three sections — and actionability gaps where no concrete tool or command is named for generating a heading outline.
Suggestions
Merge the Quick Reference bullets into the Check section (or vice versa) so each fact appears once, cutting roughly a third of the body.
Name a concrete tool or command for the heading outline, e.g. "Run axe DevTools or Lighthouse's heading-structure audit" or a one-line DOM snippet like `document.querySelectorAll('h1,h2,h3,h4,h5,h6').map((el,i)=>`${' '.repeat(+el.tagName[1]-1)}${el.tagName} ${el.textContent.trim()}`)`.
Add an explicit verification step after Fix, e.g. "Regenerate the heading outline after restructuring to confirm exactly one h1 and no skipped levels."
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body restates the same facts three times — Quick Reference's "Use exactly one h1 per page", Check's "Verify pages have exactly one h1, headings follow sequential order without skipping levels", and Fix's "Start with h1 for the page title" — plus an intro sentence repeating the screen-reader rationale. Mostly efficient with short sections, but the triple restatement is more than a minor trim, fitting anchor 3 rather than 4; not 2 because there is no padded explanation of concepts Claude already knows. | 3 / 5 |
Actionability | The checks are directive ("Verify pages have exactly one h1, headings follow sequential order") but key details are missing: "Use accessibility tools to generate a heading outline" names no tool or command (e.g. axe, Lighthouse, a heading-outline snippet), and the Fix section gives structural direction without an example. This matches anchor 3's "some concrete guidance but incomplete"; not 4 because no executable command, tool, or code appears in the body. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections give a clear, well-ordered sequence for this simple single-task skill, and Code Review's "note how to verify the fix with browser accessibility tooling" hints at verification. Not 5 because no explicit re-check loop exists (e.g. "regenerate the heading outline after fixing to confirm"); not 3 because the sequence is coherent, well-sectioned, and verification is at least mentioned. | 4 / 5 |
Progressive Disclosure | The body is a lean, well-sectioned overview that delegates detail via a clearly signaled, one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists, is on-topic, and contains no further nested references. This matches anchor 5 exactly: clear overview with well-signaled one-level-deep references. | 5 / 5 |
Total | 15 / 20 Passed |