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.
A lean, well-structured single-purpose skill with a clean Check/Fix/Explain workflow and exemplary progressive disclosure through one clearly signaled reference file. Its weaknesses are modest: a redundant concept explanation Claude does not need, and a missing explicit re-verification step after the fix.
Suggestions
Drop the opening sentence and the 'Provides a clear starting point' bullet — Claude already knows what a main landmark does; keep only the rule statement.
Add an explicit verification loop after Fix, e.g. 'Re-count main elements to confirm exactly one remains' or 'Re-run the accessibility checker to confirm the violation is resolved'.
Include one concrete detection snippet in the Check section, such as document.querySelectorAll('main, [role=main]').length, instead of the prose-only instruction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body opens by explaining what a main landmark does for screen reader users ("allows keyboard and screen reader users to jump directly to the primary content") and the Quick Reference bullet "Provides a clear starting point for the page's primary content" repeats it — both are concepts Claude already knows, and the Code Review section largely restates the frontmatter description in generic terms. This matches anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened") better than anchor 4, where over-explanation would be only a minor instance rather than a full intro paragraph plus a redundant bullet. | 3 / 5 |
Actionability | The Check and Fix sections give concrete, executable direction — "Count the number of <main> elements or elements with role='main' on the page" and "Combine multiple main content areas into a single <main> element or remove the 'role=main' attribute from extra containers" — and code examples are appropriately deferred to references/rule.md. It is not anchor 5 because no concrete command or selector is given inline (e.g. a querySelectorAll expression or axe rule id) and the Code Review section stays at the level of general instruction; it is well above anchor 3, whose guidance is incomplete or pseudocode. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sequence is clearly laid out with unambiguous steps for this simple single-purpose skill. It falls short of anchor 5 because there is no explicit validation checkpoint after the fix — the workflow never says to re-count the main elements or re-run the checker to confirm exactly one remains, only a vague mention of noting "how to verify the fix with browser accessibility tooling" — matching anchor 4's "clear sequence with most checkpoints present; minor validation gaps". | 4 / 5 |
Progressive Disclosure | The body is a concise overview and the single reference is clearly signaled and one level deep: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and references/rule.md exists and contains exactly that material (code examples, best practices, verification steps). No nesting, no buried references, no inline content that belongs in a separate file; this matches the anchor-5 example of a clear overview with well-signaled one-level-deep references. | 5 / 5 |
Total | 16 / 20 Passed |