Content
71%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 a well-organized, lean overview with a clean one-level-deep pointer to references/rule.md, but the in-body guidance stays high-level — no concrete detection command or explicit verification step — leaving execution details entirely to the reference file.
Suggestions
Add one concrete detection step to the Check section, e.g. a grep pattern for repeated id="..." values or a browser snippet like grouping document.querySelectorAll('[id]') to spot duplicates.
Make verification an explicit step in the body (e.g. "After fixing, re-run axe/Lighthouse and re-test keyboard navigation") rather than only instructing the reviewer to note how to verify.
Merge or drop the Quick Reference bullets, since they restate the intro sentence and the rule itself three times over.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean (~30 lines) with clear sections, but the intro sentence and the Quick Reference bullets ("Avoid duplicate IDs that can break keyboard navigation and focus management") restate the same rule three ways and restate knowledge Claude already has, so minor trimming is possible. | 4 / 5 |
Actionability | "Search for duplicate id attributes on focusable or active HTML elements" names the target but gives no method (no grep pattern, selector, or axe/Lighthouse invocation in the body), and "Assign a unique id to each active element" is a generic one-liner — some concrete guidance with key execution details left to the reference file. | 3 / 5 |
Workflow Clarity | Check → Fix → Explain → Code Review is a clear sequence for this simple skill, and the Code Review section says to "note how to verify the fix with browser accessibility tooling", but there is no explicit validate-after-fix checkpoint step in the body itself — a minor validation gap. | 4 / 5 |
Progressive Disclosure | The body is a concise overview and the sole reference is one level deep, clearly signaled ("see `references/rule.md`"), and the file exists containing the promised implementation details, code examples, and validation tools — a clean overview-to-detail split. | 5 / 5 |
Total | 16 / 20 Passed |