heading-order

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

Quality

63%

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-order/SKILL.md

Quality

Content

63%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.

The content is a well-structured overview with excellent progressive disclosure to references/rule.md and a clear review workflow, but it carries redundant sections and explains a known concept while keeping the concrete verification steps out of the main body. Inlining a brief verification method and trimming redundancy would lift the score.

Suggestions

Remove the opening paragraph explaining why heading order matters, or fold it into the Explain section, since Claude already knows this concept.

Merge the Quick Reference bullets with the Check section to eliminate duplication, or repurpose Quick Reference as the sole prescriptive list.

Inline one concrete verification step (e.g. "Inspect the accessibility tree / run axe and confirm no skipped levels remain") so the main body is actionable without requiring references/rule.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the opening sentence explains why heading order matters (a concept Claude already knows) and the Quick Reference bullets duplicate the Check/Fix sections, so it could be tightened.	3 / 5
Actionability	It gives concrete examples ("change an <h3> to an <h2> if it follows an <h1>"), but the specific verification method is deferred to references/rule.md and the Code Review section stays vague ("Flag exact elements, roles, labels..."), leaving key details inline.	3 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is clear and this is a non-destructive review skill, but an explicit inline verification checkpoint is only weakly present, so a minor validation gap remains.	4 / 5
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ("see `references/rule.md`") which is a real file holding the code examples and detailed guidance, matching the ideal split.	5 / 5
	Total	15 / 20 Passed

Description

63%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.

The description answers both what and when with several concrete actions, but its trigger terms lack common synonyms and its broad accessibility scope creates overlap risk with related skills. Tightening the triggers and niching the actions to headings would raise the score.

Suggestions

Add natural trigger synonyms users actually say, e.g. "heading hierarchy", "skipped heading levels", or "h1 to h2 ordering".

Narrow the described actions to heading-specific checks (heading order, skipped levels, single h1) instead of generic accessibility review to reduce overlap with sibling a11y skills.

Rewrite the awkward clause "related to Maintain logical heading order" into a concrete trigger phrase such as "Use when reviewing page heading structure or when heading levels may be skipped."

Dimension	Reasoning	Score
Specificity	The description lists several concrete inspection actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but these are generic accessibility-review actions rather than heading-specific ones, leaving minor coverage gaps.	4 / 5
Completeness	Both the "what" (the inspection actions) and the "when" ("Use when reviewing rendered HTML, interactive components, or design-system patterns") are present, but the trigger phrasing "related to Maintain logical heading order" is awkward and could be more explicit.	4 / 5
Trigger Term Quality	It includes some natural terms ("heading order", "rendered HTML", "screen-reader") but misses common variations a user would say, such as "heading hierarchy", "skip heading levels", or "h1/h2".	3 / 5
Distinctiveness Conflict Risk	Although tied to heading order, the described scope (keyboard behavior, focus flow, accessible names) is broad accessibility review and could overlap with sibling accessibility skills, so it is only somewhat distinct.	3 / 5
	Total	14 / 20 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-order/SKILL.md
Commit: 30756a7

Reviewed: 9 days 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.