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 compact, well-structured review skill with clear Check/Fix/Explain sections and exemplary use of a single real reference file. The weaker spots are redundant restatements of the same rule across four sections and a Fix section that names the goal rather than a concrete remediation method.
Suggestions
Collapse the three near-identical Quick Reference bullets into one and drop the 'Explain' section's restatement of known ARIA behavior.
Make the Fix section concrete: name the actual remediation (generate unique IDs, e.g. React's useId, and update every aria-* reference), or surface the good/bad markup example from references/rule.md inline.
Add an explicit post-fix verification step (re-run an axe/Lighthouse check or re-inspect the accessibility tree) to the body's sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is compact but redundant: the three Quick Reference bullets ('Ensure IDs referenced by ARIA attributes... are unique', 'Avoid duplicate IDs that lead to ambiguous accessibility relationships', 'Verify that ARIA controls correctly target their intended elements') each restate the same single rule, and the intro plus the 'Explain' section re-explain duplicate-ID behavior Claude already knows. More than minor trimming is needed, though there is no tutorial-style padding. | 3 / 5 |
Actionability | The Check section gives a precise, actionable criterion ('Identify elements where an ARIA attribute references an id that appears multiple times in the DOM'), but the Fix section only restates the goal ('Ensure all elements referenced by ARIA attributes have unique IDs and update the references accordingly') without a method, and the body contains no commands, selectors, or example markup — all executable detail is deferred to references/rule.md. | 3 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence with headed sections, and the Code Review section includes verification guidance ('note how to verify the fix with browser accessibility tooling or assistive tech'). Verification is a passing mention rather than an explicit checkpoint and there is no re-check loop after fixing, so it falls short of the top anchor. | 4 / 5 |
Progressive Disclosure | The body is a concise overview that clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that file exists with real, well-organized content (code examples, tools, verification steps) rather than nested pointers. Content is appropriately split between overview and reference. | 5 / 5 |
Total | 15 / 20 Passed |