empty-heading

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

Quality

68%

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

Quality

Content

61%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 concise, well-sectioned overview that correctly offloads detailed examples to a real references/rule.md file. It is held back by high-level rather than concrete actionable steps in the body and the absence of an explicit validation/verification checkpoint in the workflow.

Suggestions

Add one concrete inline example (e.g., a CSS selector or axe/Lighthouse command) in the Check or Fix section so the body is executable without opening the reference.

Insert an explicit verification checkpoint into the workflow, e.g. 'Verify: confirm the heading now appears in the accessibility tree with a non-empty accessible name before closing the task.'

Link references/rule.md contextually next to the relevant section (e.g., under Check or Fix) rather than only in a trailing prose paragraph.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean, with only minor over-explanation such as the opening 'ghost stops' framing and the meta 'Explain' directive; not a 5 because those could be trimmed.	4 / 5
Actionability	Directions like 'Find any heading tags (h1 through h6) that are empty' and 'Flag exact elements, roles, labels, focus behavior' are actionable but high-level, with no concrete selectors, commands, or code in the body — specifics are deferred to references/rule.md.	3 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is present and 'note how to verify the fix' nods at validation, but there is no explicit validation checkpoint or feedback loop.	3 / 5
Progressive Disclosure	The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep reference to references/rule.md, which exists; minor gap is the reference is signaled only in a bottom prose paragraph rather than contextually per section.	4 / 5
	Total	14 / 20 Passed

Description

75%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 is well-structured with an explicit 'Use when' trigger and a concrete list of inspection actions, covering both what and when clearly. Its main weakness is the awkward 'Ensure headings contain text' phrasing as a trigger and slightly generic inspection verbs.

Dimension	Reasoning	Score
Specificity	Lists several concrete inspection actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — but they are review-oriented rather than a comprehensive set of distinct capabilities.	4 / 5
Completeness	Explicitly answers both what ('Check native semantics...inspect keyboard behavior, focus flow, accessible names, and screen-reader output') and when ('Use when reviewing rendered HTML, interactive components, or design-system patterns'), with the 'when' slightly awkward in phrasing.	4 / 5
Trigger Term Quality	Good natural-term coverage with 'reviewing rendered HTML, interactive components, or design-system patterns', though 'Ensure headings contain text' reads as a rule name rather than a phrase users naturally say.	4 / 5
Distinctiveness Conflict Risk	Targets a clear accessibility niche (empty-heading rule) with distinct triggers, with only minor overlap risk against closely related semantic/heading accessibility skills.	4 / 5
	Total	16 / 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/empty-heading/SKILL.md
Commit: 30756a7

Reviewed: 15 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.