Content
57%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 an exemplary one-level reference split keeping SKILL.md lean, but redundancy (duplicated fix advice, a description-parroting Code Review section, an Explain meta-section) and a Check step lacking an executable scan method or in-body verification keep the guidance from being fully actionable.
Suggestions
Merge the Quick Reference and Fix bullets into one statement of the rule and fix, and delete the Code Review paragraph's verbatim restatement of the description.
Make the Check step executable: list the focusable selector (a[href], button, input, select, textarea, [tabindex]) or name the axe rule (aria-hidden-focus) instead of just "links, buttons, or inputs".
Add an explicit verify step in the body (re-run the checker or keyboard-tab the container after applying tabindex="-1"/inert) instead of leaving verification only in references/rule.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening "When a keyboard user tabs into an aria-hidden element, the screen reader remains silent..." explains a concept Claude already knows, the tabindex="-1"/inert advice is duplicated between Quick Reference and Fix, the "Explain" section is a meta-instruction rather than content, and the Code Review paragraph restates the description nearly verbatim. Mostly efficient but with repeated unnecessary material — the 3 anchor, not 4 (only minor over-explanation). | 3 / 5 |
Actionability | "Scan aria-hidden=\"true\" containers for focusable elements like links, buttons, or inputs" and "Add tabindex=\"-1\" ... or use the inert attribute" are concrete, but the body gives no executable scan method (a focusable-element selector or an axe rule id) and no code example, deferring all details to references/rule.md. Some concrete guidance but incomplete — the 3 anchor, not 4 (mostly executable guidance). | 3 / 5 |
Workflow Clarity | The Check → Fix sequence is present and ordered, and "note how to verify the fix with browser accessibility tooling" gestures at verification, but no explicit verification checkpoint or feedback loop appears in the body — it lives only in references/rule.md and is not surfaced as a step. Steps listed with checkpoints missing — the 3 anchor, not 4. This is a review skill, not a destructive/batch operation, so no lower cap applies. | 3 / 5 |
Progressive Disclosure | A ~44-line body with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single, clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — which exists and appropriately holds the code examples, exceptions, and verification detail. This matches the 5 anchor and the simple-skill scoring note. | 5 / 5 |
Total | 14 / 20 Passed |