Content
63%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 appropriately split one-level reference to references/rule.md, and the Check/Fix flow is clear for a simple single-purpose skill. Weaknesses are mild padding (an intro and Explain section that restate what Claude already knows) and actionability that stops short of an inline code example, leaving executable detail entirely in the reference file.
Suggestions
Cut the opening paragraph explaining what landmark regions do and fold the vague "Explain" section into "Fix" — Claude already knows why landmarks matter.
Inline one minimal snippet (a nav/main/footer skeleton with aria-label on a second nav) so the fix is executable without opening the reference; move the rest to rule.md as now.
Make the "Check" section concrete (e.g. "confirm exactly one <main>, and that sibling <nav> elements are distinguished via aria-label") instead of "verify that they are correctly structured".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph ("Landmark regions allow screen reader users to quickly identify and jump to major sections of a page, significantly improving navigation efficiency") explains a concept Claude already knows, and the "Explain" section restates it as filler. The rest is lean, so it fits anchor 3 (mostly efficient, some unnecessary explanation); not 4 because two sections add no information Claude lacks. | 3 / 5 |
Actionability | Concrete specifics are present (the landmark elements <header>, <nav>, <main>, <footer>; "labels for multiple landmarks of the same type using aria-label"; "Replace generic <div> containers with semantic landmark elements"), but the body contains no code example and "Check" stays abstract ("Verify that the page uses appropriate HTML5 landmark elements"). Fits anchor 3 (some concrete guidance, incomplete); not 4 because the executable example exists only in the reference file, not the body. | 3 / 5 |
Workflow Clarity | As a simple single-purpose review skill, the Check → Fix → Code Review flow is unambiguous and verification is invoked ("note how to verify the fix with browser accessibility tooling or assistive tech"), with concrete validation steps (axe/Lighthouse, accessibility tree, keyboard test) correctly delegated to references/rule.md. Fits anchor 4 (clear sequence, minor validation gaps in-body); not 5 since the body itself has no explicit validation checkpoint. | 4 / 5 |
Progressive Disclosure | The body is a concise, well-sectioned overview (Quick Reference / Check / Fix / Explain / Code Review) with a clearly signaled one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and delivers exactly those details (code example, rationale, verification steps). Matches anchor 5 (clear overview, well-signaled one-level-deep references); anchor 4 would require organization gaps that are not present. | 5 / 5 |
Total | 15 / 20 Passed |