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-structured with a clear review workflow and exemplary progressive disclosure to a single real reference file. It is held back by a concept-explanation intro Claude does not need, some duplicated guidance between Quick Reference and Fix, and a Check step that lacks an executable detection technique.
Suggestions
Delete or compress the opening paragraph explaining what invalid ARIA roles do; Claude already knows this.
Make the Check section executable, e.g. a grep pattern for role attributes or a named tool (axe DevTools, accessibility inspector) to detect invalid values.
De-duplicate the native-controls guidance between Quick Reference and Fix so it appears once.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The intro sentence "Invalid or misspelled ARIA roles are ignored by browsers and assistive technologies, rendering the intended accessibility features useless..." explains a concept Claude already knows, and "Prefer native HTML controls over custom ARIA widgets" in Quick Reference restates the Fix section's advice. Mostly efficient but could be tightened. | 3 / 5 |
Actionability | Concrete specifics exist ("use `checkbox`, not `check-box`"; "native `<button>`, `<input>`, `<select>`"), but the Check step ("Search for any role attributes that use non-standard or misspelled ARIA role values") provides no executable technique (grep pattern, axe, DevTools inspection), and all code examples are deferred to the reference file rather than included inline. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a clearly labeled, coherent sequence appropriate to this single-purpose review skill. Verification is mentioned ("note how to verify the fix with browser accessibility tooling") but only in passing within Code Review rather than as an explicit checkpoint step, so it falls just short of a 5. | 4 / 5 |
Progressive Disclosure | "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" is a well-signaled, one-level-deep reference to a real file that verifiably contains the code examples and details promised. The body is a concise overview with the bulk appropriately split out, making navigation easy. | 5 / 5 |
Total | 15 / 20 Passed |