CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

semantic-lists

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic list elements. 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/semantic-lists/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, actionable overview with a properly signaled one-level-deep reference to real bundle content. Its main cost is token redundancy — the screen-reader announcement fact and generic review boilerplate are repeated — and the absence of an inline validation step for the fix.

Suggestions

State the 'list with X items' screen-reader fact once (intro or Quick Reference) and cut the duplicate mentions in the Quick Reference bullet and Explain section.

Trim the generic 'Code Review' boilerplate to skill-specific instructions, e.g. 'Flag div/span groups styled as lists; note that wrapping them in ul/ol/li restores the screen-reader list announcement.'

Add a one-line verification step to Fix, e.g. 'Verify: the element list in the accessibility tree or a screen reader now announces "list with N items".'

DimensionReasoningScore

Conciseness

The body is short but repeats the 'list with X items' screen-reader fact three times (intro, Quick Reference bullet, and the Explain section) and includes a generic boilerplate 'Code Review' section ('Flag exact elements, roles, labels, focus behavior, or keyboard interactions…'). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the minor-trimming anchor at 4.

3 / 5

Actionability

Gives concrete, executable guidance: a specific element mapping ('Use <ul> for unordered lists (navigation, features, bullets)', 'Use <ol> for ordered sequences', 'Use &lt;dl&gt; for term-definition pairs') and a concrete Fix step ('Wrap related items in appropriate list elements… Use li for list items and proper dt/dd'). It is not 5 because no bad→good markup example appears inline; that is deferred to references/rule.md, which the scoring note permits for instruction-only skills.

4 / 5

Workflow Clarity

The Check → Fix → Explain sections give a clear, unambiguous sequence for this simple single-purpose skill, and the Code Review section mentions verifying the fix 'with browser accessibility tooling or assistive tech'. It does not reach 5 because there is no explicit validation checkpoint (e.g. how to confirm the announcement changed) after applying the fix.

4 / 5

Progressive Disclosure

The SKILL.md is a lean overview and clearly signals a single one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists with the detailed examples, plus the rule-page URL. Content is appropriately split with easy navigation, matching the top anchor.

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 follows the 'Use when…' pattern with several concrete review actions and domain-relevant trigger terms. Its main weaknesses are the ungrammatical embedding of the rule name ('related to Use semantic list elements') and generic review-procedure wording that overlaps with other accessibility skills.

Suggestions

Rewrite the trigger clause to be grammatical and keyword-rich, e.g. 'Use when reviewing rendered HTML for semantic list markup (ul, ol, dl) — navigation menus, feature lists, step sequences, or definition lists styled with divs/spans.'

State the skill's concrete purpose up front (e.g. 'Reviews markup for semantic list elements and flags div/span-based faux lists') so the 'what' is explicit rather than implied by the rule name.

Add natural synonyms users would say — 'accessibility', 'a11y', 'screen reader', 'list markup' — to improve trigger-term coverage and distinctiveness from sibling accessibility skills.

DimensionReasoningScore

Specificity

Lists several concrete review actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — matching the several-specific-actions anchor. It falls short of 5 because 'related to Use semantic list elements' embeds the rule name awkwardly, leaving the core capability statement slightly garbled rather than comprehensive.

4 / 5

Completeness

Both parts are present: an explicit 'Use when reviewing rendered HTML, interactive components, or design-system patterns' trigger and a 'what' describing the check-then-inspect procedure. It does not reach 5 because the when-clause's 'related to Use semantic list elements' reads as template substitution, making the trigger less concrete and natural than the anchor's clear trigger phrases.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say such as 'rendered HTML', 'keyboard behavior', 'focus flow', and 'screen-reader output', giving good keyword coverage. It is not 5 because common variations like 'accessibility', 'a11y', 'screen reader' (unhyphenated), and 'ul/ol/dl list markup' are missing.

4 / 5

Distinctiveness Conflict Risk

The inspection procedure (keyboard behavior, focus flow, accessible names, screen-reader output) is boilerplate shared across accessibility-review skills, so it could still overlap with closely related a11y skills. Only the embedded rule name 'Use semantic list elements' distinguishes it, which fits the 'somewhat specific but could still overlap' anchor better than the minor-overlap anchor above.

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/semantic-lists/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.