CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html5-semantic-elements

Use when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

75%

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/html5-semantic-elements/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.

A well-structured, appropriately split skill body: concrete element-level guidance with a clean pointer to a real single reference file. The main cost is tokens spent teaching Claude HTML5 basics it already knows, plus a slightly ambiguous 'this HTML structure' referent in the Check section.

Suggestions

Cut or drastically trim the screen-reader/SEO rationale sentence and the Quick Reference bullets — Claude already knows HTML5 element semantics; keep only rule-specific facts (e.g., 'only one <main> per page').

Replace 'Review this HTML structure' with a concrete instruction about what to inspect (the rendered markup of the files under review) since no specific structure is shown in the body.

Add one compact before/after example (div soup replaced by semantic elements) inline, or confirm it is prominently placed in references/rule.md so the common case is executable without opening the reference.

DimensionReasoningScore

Conciseness

The body is short (~35 lines), but the opening rationale ('Screen readers use semantic elements to navigate pages... Search engines also use semantics...') and the Quick Reference bullets restate basic HTML5 semantics Claude already knows, which is unnecessary explanation. This is more than the 'minor instances' of anchor 4 but not the heavily padded multi-section verbosity of anchor 2.

3 / 5

Actionability

Guidance is concrete for an instruction-only skill: it names the exact elements to look for ('header, main, section, article, aside, and footer instead of generic div elements') and what to flag ('exact elements, attributes, and routes'). It stops short of anchor 5 because no inline violation-to-fix example is given — examples are deferred entirely to the reference — but key specifics are all present, above anchor 3.

4 / 5

Workflow Clarity

Check, Fix, Explain, and Code Review sections give a clear sectioned sequence for a simple, non-destructive review skill, so the destructive-operation validation cap does not apply. Minor ambiguity ('Review this HTML structure' lacks a referent, and whether Code Review is a mode or a step is unclear) keeps it below the unambiguous single-action anchor 5.

4 / 5

Progressive Disclosure

The body is a genuine overview and the bundle contains exactly one reference, 'references/rule.md', which exists, is one level deep, and is clearly signaled with a description of its contents ('full implementation details, code examples, and framework-specific guidance'). This matches the anchor for a clear overview with well-signaled one-level-deep references and appropriately split content.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid description with an explicit when-clause, natural trigger terms, and a distinctive framework-rendered-markup angle. Its main weaknesses are the grammatically broken 'related to Use semantic HTML elements' phrase, an action list that stops at two verbs, and missing common synonyms/extensions.

Suggestions

Rewrite the mid-sentence artifact 'related to Use semantic HTML elements' into a direct capability statement, e.g., 'Check rendered HTML for semantic HTML5 elements (header, main, section, article, aside, footer) and flag generic div-based structure.'

Add natural trigger synonyms and file extensions such as '.html files', 'markup', or 'div soup' to broaden natural keyword coverage.

State the full capability set in the 'what' clause (check, fix, and explain semantic markup) so the description covers everything the skill body actually offers.

DimensionReasoningScore

Specificity

The description names the domain (semantic HTML elements) and two concrete actions ('reviewing templates, rendered HTML, or shared components', 'Validate the final browser-facing markup'), matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage. It does not list the fuller action set (check, fix, explain, flag violations), so it falls short of anchor 4, while being clearly more concrete than the generic minimal-action anchor 2.

3 / 5

Completeness

An explicit 'Use when...' clause answers when, and 'Validate the final browser-facing markup, not just the source framework abstraction' answers what, so both are present. The 'what' is weakened by the awkward embedded rule name ('related to Use semantic HTML elements') and does not state the full capability set, keeping it below the clearly-stated anchor 5 while above anchor 3 since the when-clause is explicit and concrete.

4 / 5

Trigger Term Quality

Phrases like 'templates, rendered HTML, shared components', 'semantic HTML elements', and 'browser-facing markup' are natural terms a user would say in this context, giving good keyword coverage. It misses common synonyms and file extensions (e.g., '.html', 'markup review', 'div soup'), so it does not reach the comprehensive anchor 5, but coverage exceeds the partial-coverage anchor 3.

4 / 5

Distinctiveness Conflict Risk

'semantic HTML elements' carves a clear niche distinct from sibling HTML rules (image alt, form labels), and the framework-abstraction angle is distinctive. The fairly broad 'reviewing templates, rendered HTML, or shared components' trigger could overlap with other markup-review skills, matching anchor 4 (minor overlap risk with closely related skills) rather than the minimal-conflict anchor 5.

4 / 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/html5-semantic-elements/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.