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.
A lean, well-structured overview body that delegates detail appropriately to a real one-level-deep reference file. The main gaps are in-body actionability — no roles-to-required-attributes mapping, code snippet, or named verification tool — and mild redundancy/padding (background intro, Explain section, Quick Reference overlap).
Suggestions
Cut the background intro sentence and the Explain section (they restate ARIA knowledge Claude already has) and merge the Quick Reference bullets into Check/Fix to remove redundancy.
Inline the minimal executable core in the body: a short table or list mapping common roles to their required attributes (slider → aria-valuenow/min/max, scrollbar → aria-controls/valuenow, checkbox → aria-checked) with one small HTML snippet, instead of deferring all specifics to references/rule.md.
Make the verification checkpoint concrete by naming the tooling (e.g., "run axe or Lighthouse" and "inspect the accessibility tree") rather than "browser accessibility tooling or assistive tech".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short but includes unnecessary explanation Claude already knows — "Certain ARIA roles are incomplete without their required attributes, preventing assistive technologies from correctly communicating the element's state or value" and an Explain section restating why screen readers need ARIA — and the Quick Reference bullets largely repeat the Check and Fix sections. It fits the 'mostly efficient but could be tightened' anchor rather than the 'minor trims' anchor above. | 3 / 5 |
Actionability | Only one concrete detail appears in the body — "aria-valuenow for role=\"slider\"" — while the core knowledge needed to execute (which roles require which attributes, any code example, any concrete tool command) is entirely deferred to references/rule.md. This is 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable anchor above. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections imply a clear sequence for this single-task skill, and the Code Review section mentions verification ("note how to verify the fix with browser accessibility tooling or assistive tech"), but the verification step is only vaguely specified in the body rather than being a concrete checkpoint — matching 'clear sequence with most checkpoints; minor validation gaps'. | 4 / 5 |
Progressive Disclosure | The body is a concise overview with a clearly signaled, verified one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the referenced file exists and carries the bulk content (examples, exceptions, standards, verification), matching the clear-overview anchor. | 5 / 5 |
Total | 15 / 20 Passed |