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 well-structured, lean skill body: concrete tabindex rules in a scannable Quick Reference, a coherent check/fix/explain/review workflow, and a correctly delegated one-level reference file that exists and delivers the promised code examples. Weaknesses are minor: some redundancy between Quick Reference and the Check/Fix sections, and verification specifics left entirely to the reference file.
Suggestions
Merge the "Check" and "Fix" sections into the Quick Reference (or drop the prose restatement) to eliminate duplicated guidance.
Add one concrete detection step in the body, e.g. `grep -rnE 'tabindex="[1-9]'` or "run axe/Lighthouse", so the Check step is executable without opening the reference.
Surface one in-body verification checkpoint (e.g., "re-test tab order with keyboard-only navigation after fixing") instead of deferring all verification details to references/rule.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no concept over-explanation, but the "Check" and "Fix" sections restate the Quick Reference bullets in prose form ("Avoid positive values... break natural tab order" vs "Remove positive tabindex values"), a minor trim opportunity that fits anchor 4 rather than anchor 5's 'every token earns its place'. | 4 / 5 |
Actionability | Concrete guidance throughout: exact values (`tabindex="0"`, `tabindex="-1"`), explicit prohibition of positive values, and direct fix instructions, with code examples correctly delegated to references/rule.md (verified to exist and contain executable HTML). It stops short of anchor 5 because no method is given for finding violations (e.g., a grep pattern or axe/Lighthouse check) in the body itself. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sequence is clearly ordered and unambiguous, and the Code Review section signals verification ("note how to verify the fix with browser accessibility tooling or assistive tech"). Concrete verification steps live only in the reference file rather than the body, so it matches anchor 4 ('most checkpoints present; minor validation gaps') rather than anchor 5's explicit in-body validation steps. | 4 / 5 |
Progressive Disclosure | A concise overview body with a single clearly-signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the referenced file exists with that content. Nothing that belongs in a separate file is inlined, matching anchor 5's clear overview with well-signaled references. | 5 / 5 |
Total | 17 / 20 Passed |