heading-hierarchy

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use logical heading hierarchy. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/heading-hierarchy/SKILL.md

Quality

Content

57%

Reviews 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 clean progressive disclosure to a real reference file, but it carries mild redundancy, vague tooling pointers, and validation steps that are implicit rather than inline.

Suggestions

Deduplicate the "never skip heading levels" guidance and the screen-reader-navigation explanation so each appears once.

Name the concrete verification tools inline (e.g. HeadingsMap extension, DevTools heading outline) and add an explicit verify step rather than deferring all tooling to references/rule.md.

Dimension	Reasoning	Score
Conciseness	Mostly lean, but "never skip heading levels" recurs across Quick Reference, Check, and Fix, and the known concept "Screen reader users navigate by headings like a table of contents" is restated in both the intro and Explain sections.	2 / 3
Actionability	Rules are specific (one h1, h1 → h2 → h3, descriptive text) but the tooling guidance is vague ("Use accessibility tools to generate a heading outline") and the concrete tool names live only in references/rule.md.	2 / 3
Workflow Clarity	The Check → Fix → Code Review sequence is present, but validation/verification checkpoints are implicit since the actual verification tooling is delegated to references/rule.md rather than stated inline.	2 / 3
Progressive Disclosure	A concise overview with a single, clearly signaled one-level-deep reference ("see references/rule.md"), and the referenced bundle file exists.	3 / 3
	Total	9 / 12 Passed

Description

77%

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 well-formed description with an explicit Use-when trigger and concrete checking actions, but its trigger terms are somewhat technical and its broad a11y scope creates moderate overlap risk with sibling skills.

Suggestions

Add natural trigger terms a user would actually say, e.g. "headings", "h1/h2", "skipped heading levels", or "page outline".

Narrow the scope language so it reads as heading-hierarchy-specific rather than covering keyboard, focus, and accessible names, which overlap other accessibility skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete checking actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — matching the multi-action anchor.	3 / 3
Completeness	Explicit "Use when reviewing..." trigger satisfies the when clause, and the checking actions clearly state what the skill does.	3 / 3
Trigger Term Quality	Includes relevant terms ("heading hierarchy", "rendered HTML", "interactive components", "design-system patterns") but leans technical and omits common natural variations users would say ("headings", "h1/h2", "skipped levels", "page outline").	2 / 3
Distinctiveness Conflict Risk	Scoped to heading hierarchy but the broad accessibility language (keyboard behavior, focus flow, accessible names) could overlap with other accessibility skills.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/heading-hierarchy/SKILL.md
Commit: 48405aa

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.