Conciseness

The intro ("The H1 is the most prominent heading on a page and a strong on-page ranking signal. Google uses it to understand the page's primary topic") and the "Explain" section ("Google's John Mueller has confirmed that H1 tags help Google understand page structure...") both restate background SEO knowledge Claude already has, and partially duplicate each other. Not a 4 because two separate background-justification passages are more than minor over-explanation; not a 2 because the actionable sections (Check, Fix, Code Review) are tight and unpadded.

Actionability

Concrete, testable guidance throughout: the Check section enumerates five specific flag conditions, Fix includes a Before/After example ("<h1>Acme Corp</h1>" → "<h1>Project Management Software for Enterprise Teams</h1>"), and Code Review specifies assertions like "Check that innerText.trim() is non-empty". Per the instruction-only scoring note, absent code is not penalized since the guidance is actionable; not a 5 because no runnable selector/command (e.g., document.querySelectorAll('h1')) is given to execute the checks.

Workflow Clarity

A clear Check → Fix → Code Review sequence covers identification, remediation, and verification, with concrete checkpoints (count <h1> elements, assert exactly one, compare to <title>). Not a 5 because there is no explicit re-validation loop ("after fixing, re-run the check") — the destructive/batch cap does not apply since this is a non-destructive audit skill; not a 3 because verification checkpoints are explicitly present in the Code Review section rather than missing.

Progressive Disclosure

The body is a well-organized ~40-line overview (Quick Reference, Check, Fix, Explain, Code Review) with a single clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists in the bundle (112 lines of code examples and framework guidance). Not a 4 because content is appropriately split and navigation is unambiguous, with no inline material that clearly belongs in the reference file.

Specificity

"auditing a page's heading structure", "generating H1 text for landing pages or blog posts", and "reviewing a CMS template that may produce empty or missing H1 elements" name several concrete actions with specific contexts. Not a 5 because coverage has minor gaps (e.g., duplicate-H1 detection and title-consistency checking are only implied by "auditing"), and not a 3 because more than 1-2 concrete actions are explicitly listed.

Completeness

The "Use when..." clause is explicit with three concrete trigger scenarios, and the gerunds (auditing, generating, reviewing) convey what the skill does, so both what and when are present. Not a 5 because the what and when are fused into one sentence with no separate capability statement (e.g., "Audit heading structure and generate H1 text. Use when..."); not a 3 because the when is explicit and specific rather than missing or weakly implied.

Trigger Term Quality

Natural terms users would say are present: "H1", "heading structure", "landing pages", "blog posts", "CMS template", "empty or missing H1". Not a 5 because common variations like "main heading", "heading tag", or "SEO" are absent; not a 3 because keyword coverage goes well beyond a single generic term.

Distinctiveness Conflict Risk

Every trigger is anchored to the H1/heading-structure niche ("H1 text", "heading structure", "empty or missing H1 elements"), giving a clear niche with distinct triggers and minimal conflict risk — no plausible sibling skill would claim these triggers. Not a 4 because the overlap risk with general copywriting or SEO-audit skills is negligible given the H1-specific framing.