Content
78%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 concise, well-structured single-purpose skill: the body gives concrete check/fix guidance and cleanly defers code examples to a real, one-level reference file. Main gaps are the absence of any inline HTML snippet and an implicit rather than explicit verification checkpoint.
Suggestions
Replace the opening rationale sentence with a minimal correct-vs-incorrect HTML snippet so the most common case is fixable without opening the reference.
Make the verification step explicit in the Check or Code Review section (e.g., a named tool/command such as an accessibility-tree inspection or axe DevTools) instead of the vague 'where relevant'.
Drop or merge the 'Code Review' paragraph, which restates the frontmatter description, to remove redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean (~30 lines) with a quick-reference list and terse Check/Fix sections, but the opening sentence explains why accessible names matter (which Claude already knows) and the 'Code Review' paragraph largely restates the frontmatter description, so a few tokens could be trimmed. | 4 / 5 |
Actionability | Concrete, executable guidance is present ('Use the `<label>` element with a matching `for` attribute', 'aria-label or aria-labelledby', 'matches the `id` of the `<select>` tag'), and the one-level reference carries full correct/incorrect HTML examples, but the body itself contains no code snippet and omits details like the title-attribute fallback, leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence exists with a verification mention ('note how to verify the fix with browser accessibility tooling'), but the validation step is loose ('where relevant') rather than an explicit checkpoint, so it sits between anchors 4 and 5 — not the fully explicit validation loop of a 5. | 4 / 5 |
Progressive Disclosure | A short, well-sectioned overview delegates full implementation details, code examples, and framework guidance to a single well-signaled, one-level-deep reference (`references/rule.md`, which exists and contains real content), matching the clear-overview pattern the rubric rewards for simple skills. | 5 / 5 |
Total | 17 / 20 Passed |