CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

h1

Use when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/h1/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable audit/fix body with a clean reference pointer, held back by redundancy and background explanation. The Check and Code Review sections overlap heavily, and the Explain section covers SEO rationale Claude already knows.

Suggestions

Merge the Check and Code Review sections into one pass — they both instruct querying the DOM for `<h1>` elements and asserting count/text, so consolidating removes near-duplicate guidance.

Move the Explain section's SEO rationale (Mueller confirmation, ranking-signal discussion) into `references/rule.md`; it is background justification rather than overview content Claude needs to act.

De-duplicate the Before/After H1 example between SKILL.md and `references/rule.md`, keeping the inline instance as a one-line illustration and letting the reference carry the full code examples.

DimensionReasoningScore

Conciseness

The intro ('The H1 is the most prominent heading on a page… Google uses it to understand…') and the Explain section ('Google's John Mueller has confirmed that H1 tags help Google understand page structure') restate SEO knowledge Claude already has, and Check ('Count all `<h1>` elements. Flag: (1)–(5)') duplicates Code Review ('Query the DOM for all `<h1>` elements. Assert exactly one exists per page'). Mostly efficient, but noticeably tightenable — not the 'several padded sections' of anchor 2, more than the minor trims of anchor 4.

3 / 5

Actionability

Guidance is concrete and near-executable — 'Assert exactly one exists per page', 'Check that `innerText.trim()` is non-empty', 'not hidden via CSS `display:none`', plus a Before/After HTML example — with a 6-step Fix list. It stops short of anchor 5's copy-paste-ready code (no runnable selector/snippet is provided), and this is an instruction-only skill so the absence of code is not itself penalized.

4 / 5

Workflow Clarity

A clear Check → Fix → Code Review sequence is present, with a verification step inside Fix ('Verify the H1 is visible in the rendered DOM') and the Code Review section acting as a validation pass. Checkpoints exist but the cross-section sequence is implied by section ordering rather than explicit, and there is no re-check loop — matching 'clear sequence with most checkpoints; minor validation gaps' rather than anchor 5's explicit feedback loops.

4 / 5

Progressive Disclosure

The body closes with a clearly signaled, one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — the file exists and links no further files). Minor organization gaps remain: the Before/After example is duplicated between the body and `references/rule.md`, and the Explain rationale arguably belongs in the reference, fitting 'good structure; minor organization gaps' below anchor 5's cleanly split content.

4 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit, concrete 'Use when…' triggers covering auditing, generation, and template review scenarios. Its only weakness is structural: capabilities are embedded in trigger clauses rather than stated as a direct 'what' declaration.

DimensionReasoningScore

Specificity

Three concrete actions are named — 'auditing a page's heading structure', 'generating H1 text for landing pages or blog posts', 'reviewing a CMS template that may produce empty or missing H1 elements' — but they are framed only as trigger contexts with no direct capability declaration, so coverage is strong with a minor gap rather than comprehensive.

4 / 5

Completeness

The 'when' is explicit ('Use when auditing… generating… or reviewing…') with three concrete trigger phrases, and the 'what' (audit, generate, review) is conveyed but only embedded in the gerund phrases rather than declared separately — matching 'both present; could be more explicit' and falling short of anchor 5's explicitly-declared what-and-when.

4 / 5

Trigger Term Quality

Natural phrases users would say are well covered: 'heading structure', 'H1', 'landing pages', 'blog posts', 'CMS template', 'empty or missing H1 elements'. A few natural variants are missing (e.g., 'main heading', 'heading tags', 'SEO'), which keeps it below the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — H1/heading-structure auditing and generation — with distinct triggers ('H1 text', 'CMS template', 'heading structure') that are unlikely to fire for sibling SEO skills like meta-title or heading-order checks.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/h1/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.