CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

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

Quality

Content

71%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 body is a well-structured, token-efficient overview that delegates implementation detail to a real, one-level-deep reference file — exemplary progressive disclosure. Its weakness is actionability: the in-body guidance names what to check and fix but provides no detection technique or example, relying entirely on the reference for executable detail.

Suggestions

Add one concrete detection cue to the Check section, e.g. an example of the offending markup (<h2></h2>, whitespace-only, or icon-only headings) or a tool reference like axe's 'empty-heading' rule, so the check is executable without opening the reference.

Merge or differentiate the Quick Reference bullets from the Check/Fix sections to remove duplication and tighten the workflow.

Trim the '## Explain' section ('Explain why meaningful heading content is vital for document navigation and accessibility') — it is a directive that adds no actionable content beyond what Check and Fix already convey.

DimensionReasoningScore

Conciseness

The body is lean with one-line Check/Fix sections and no explanation of concepts Claude already knows, but the '## Explain' section and the generic 'Code Review' boilerplate paragraph are trimmable padding.

4 / 5

Actionability

Check and Fix give specific direction ('Find any heading tags (h1 through h6) that are empty or contain only non-perceivable whitespace', 'Add descriptive text content to the empty heading or remove the heading tag'), but there is no detection method (selector, axe rule, grep pattern), no example markup, and all code examples are delegated to the reference file.

3 / 5

Workflow Clarity

As a simple single-task skill the Check → Fix → verify flow is discernible and verification is mentioned ('note how to verify the fix with browser accessibility tooling or assistive tech'), but the sequence is only implied by section order and the Quick Reference bullets duplicate the Check/Fix content.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists and contains exactly the promised detail, with the split appropriately made.

5 / 5

Total

16

/

20

Passed

Description

71%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 explicitly covers both what the skill does and when to use it, with several concrete review actions and good natural keywords. Its main weaknesses are boilerplate phrasing that blurs distinctiveness against sibling accessibility skills and a missing user-facing synonym like 'empty heading'.

Suggestions

Rewrite the when-clause around concrete user trigger phrases, e.g. 'Use when the user mentions empty headings, heading structure, or document outline accessibility issues' instead of the broad 'reviewing rendered HTML, interactive components, or design-system patterns' lead-in.

Replace the embedded rule-name phrasing 'related to Ensure headings contain text' with natural language such as 'related to empty or textless headings' so the description reads as capabilities rather than a rule title.

Add natural synonyms like 'accessibility', 'a11y', and 'empty heading' to improve trigger-term coverage and distinguish the skill from sibling accessibility rules.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') but the awkwardly embedded rule name ('related to Ensure headings contain text') and the absence of any fix-related action keep it from comprehensive coverage.

4 / 5

Completeness

Both what ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') and when ('Use when reviewing rendered HTML, interactive components, or design-system patterns') are explicitly present, but the when-clause lacks concrete trigger phrases and is overly broad.

4 / 5

Trigger Term Quality

Good natural keywords are present ('rendered HTML', 'headings', 'keyboard', 'screen-reader', 'focus'), but common user phrasings like 'empty heading', 'accessibility', or 'a11y' are missing, so synonym coverage is incomplete.

4 / 5

Distinctiveness Conflict Risk

The broad lead-in 'reviewing rendered HTML, interactive components, or design-system patterns' appears to be shared boilerplate across sibling accessibility-rule skills, so only the trailing rule-name clause distinguishes it, leaving real overlap risk with similar accessibility skills.

3 / 5

Total

15

/

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