Content
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized with a clear review workflow and a properly signaled single-level reference to a real bundle file. It is held back by a concept-restating opening/Explain section and abstract bullets where concrete examples would help.
Suggestions
Drop or tighten the opening framing sentence and the "Explain" section — Claude already knows why required ARIA attributes matter; keep only guidance it cannot infer.
Replace abstract Quick Reference bullets ("Identify roles that require...", "Validate that all required ARIA attributes are correctly implemented") with concrete checks, e.g. naming specific roles and their required attributes or the axe/Lighthouse rule IDs to look for.
Surface one minimal inline code snippet (a slider with aria-valuenow/valuemin/valuemax) in the body so the core fix is actionable without opening the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and well-structured, but the opening sentence ("Certain ARIA roles are incomplete without their required attributes, preventing assistive technologies from correctly communicating the element's state or value") explains a concept Claude already knows, and the standalone "Explain" section largely restates it. | 2 / 3 |
Actionability | There is some concrete guidance — "Add the missing required ARIA attributes to elements with specific roles (e.g., aria-valuenow for role=\"slider\")" — but several items ("Identify roles that require specific state or property attributes", "Validate that all required ARIA attributes are correctly implemented") are abstract, and the executable examples live only in the referenced file. | 2 / 3 |
Workflow Clarity | For this simple single-task review skill the Check → Fix → Explain → Code Review sections form a clear, unambiguous sequence, and verification is explicitly called out ("note how to verify the fix with browser accessibility tooling or assistive tech"). | 3 / 3 |
Progressive Disclosure | The body is a concise overview that clearly signals a single one-level-deep reference — "see references/rule.md" — and that file exists and holds the code examples and detailed guidance, matching the top anchor. | 3 / 3 |
Total | 10 / 12 Passed |