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 well-structured, appropriately split skill body: concrete element-level guidance with a clean pointer to a real single reference file. The main cost is tokens spent teaching Claude HTML5 basics it already knows, plus a slightly ambiguous 'this HTML structure' referent in the Check section.
Suggestions
Cut or drastically trim the screen-reader/SEO rationale sentence and the Quick Reference bullets — Claude already knows HTML5 element semantics; keep only rule-specific facts (e.g., 'only one <main> per page').
Replace 'Review this HTML structure' with a concrete instruction about what to inspect (the rendered markup of the files under review) since no specific structure is shown in the body.
Add one compact before/after example (div soup replaced by semantic elements) inline, or confirm it is prominently placed in references/rule.md so the common case is executable without opening the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short (~35 lines), but the opening rationale ('Screen readers use semantic elements to navigate pages... Search engines also use semantics...') and the Quick Reference bullets restate basic HTML5 semantics Claude already knows, which is unnecessary explanation. This is more than the 'minor instances' of anchor 4 but not the heavily padded multi-section verbosity of anchor 2. | 3 / 5 |
Actionability | Guidance is concrete for an instruction-only skill: it names the exact elements to look for ('header, main, section, article, aside, and footer instead of generic div elements') and what to flag ('exact elements, attributes, and routes'). It stops short of anchor 5 because no inline violation-to-fix example is given — examples are deferred entirely to the reference — but key specifics are all present, above anchor 3. | 4 / 5 |
Workflow Clarity | Check, Fix, Explain, and Code Review sections give a clear sectioned sequence for a simple, non-destructive review skill, so the destructive-operation validation cap does not apply. Minor ambiguity ('Review this HTML structure' lacks a referent, and whether Code Review is a mode or a step is unclear) keeps it below the unambiguous single-action anchor 5. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview and the bundle contains exactly one reference, 'references/rule.md', which exists, is one level deep, and is clearly signaled with a description of its contents ('full implementation details, code examples, and framework-specific guidance'). This matches the anchor for a clear overview with well-signaled one-level-deep references and appropriately split content. | 5 / 5 |
Total | 16 / 20 Passed |