CtrlK
BlogDocsLog inGet started
Tessl Logo

list-structure

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

68

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, concise single-purpose skill with clear section sequencing and an appropriately split one-level-deep reference that genuinely exists. The only gap is that the executable code example lives only in the reference, leaving the body's guidance more descriptive than directly executable.

Suggestions

Include one small inline incorrect/correct HTML snippet in the body (or in the Quick Reference) so the core fix is actionable without opening references/rule.md.

Add a brief one-line verification cue in the Check or Fix section (e.g., 'Confirm in the browser a11y tree that each ul/ol shows the expected item count') to close the guidance loop inline.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padded explanations of concepts Claude already knows; every section (Quick Reference, Check, Fix, Explain, Code Review) earns its place and assumes competence.

5 / 5

Actionability

Guidance is concrete and directional ('Remove or move any non-`<li>` elements from within `<ul>` and `<ol>` tags'), but the executable code example is deferred to references/rule.md rather than appearing inline, leaving the body itself more descriptive than copy-paste ready.

3 / 5

Workflow Clarity

For a simple, single-purpose, non-destructive review skill, the Check -> Fix -> Explain -> Code Review sections give an unambiguous sequence; no validation checkpoint is required for a read-only audit.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with a well-signaled one-level-deep reference (references/rule.md) that genuinely exists and holds the code example, why-it-matters, exceptions, and verification details, with content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

83%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 clearly answers both what and when with a concrete, multi-action capability list and explicit 'Use when' trigger guidance. The main weakness is the awkwardly embedded phrase 'related to Use correct list structure' and slightly broad framing that could overlap with other a11y skills.

Suggestions

Reword 'related to Use correct list structure' into natural trigger phrasing (e.g., 'Use when auditing list markup for correct ul/ol/li semantics') so the niche reads as a genuine trigger term rather than an embedded heading.

Add common synonyms users would actually say ('lists', 'list semantics', 'ul/ol', 'a11y') to broaden natural keyword coverage.

Narrow the opening scope from 'rendered HTML, interactive components, or design-system patterns' to list-specific contexts to reduce overlap with general accessibility skills.

DimensionReasoningScore

Specificity

Names the domain (rendered HTML, interactive components, design-system patterns) and lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), but the awkward embedded phrase 'related to Use correct list structure' slightly muddies the action set, keeping it just below a 5.

4 / 5

Completeness

Explicitly answers 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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('rendered HTML', 'interactive components', 'design-system patterns', 'keyboard behavior', 'focus flow', 'screen-reader output'), but missing common variations a user might actually say such as 'lists', 'list semantics', or 'ul/ol/li', so it is not quite comprehensive.

4 / 5

Distinctiveness Conflict Risk

The list-structure niche gives it a distinct focus, but the broad framing around 'rendered HTML, interactive components, or design-system patterns' creates minor overlap risk with general accessibility skills.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.