CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

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/list-structure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 concise, well-structured instruction-only skill body: an unambiguous check/fix procedure with concrete guidance and an exemplary progressive-disclosure split to a real one-level reference file. The main improvements are removing the duplication between Quick Reference and Check, explaining less of the why in the main file, and promoting fix verification to an explicit workflow step.

Suggestions

Merge the "## Check" section into the Quick Reference bullet it duplicates, or replace it with how to check (e.g. inspect the accessibility tree or run an axe/Lighthouse scan) instead of restating the rule.

Make verification an explicit step in the workflow (e.g. "After fixing, re-inspect the accessibility tree to confirm the list announces the correct item count") rather than only output guidance in the Code Review section.

Trim the "## Explain" section (and the intro sentence) since references/rule.md's "Why It Matters" already covers the rationale — Claude can pull it from there when needed.

DimensionReasoningScore

Conciseness

The body is lean (short bullets, terse Check/Fix sections), but the "## Check" section restates the first Quick Reference bullet almost verbatim ("ensure only li elements are direct children of ul or ol"), and the intro plus "## Explain" re-explain why list semantics matter — knowledge Claude already has — so minor trimming is warranted.

4 / 5

Actionability

Concrete, executable instructions are present ("Remove or move any non-li elements from within ul and ol tags", "Check the structure of all lists"), and code examples are appropriately delegated to the reference file; however, no inline example or verification command is given, leaving a minor gap.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear for a simple single-purpose skill, but verifying the fix is not a distinct step — it only appears as output guidance ("note how to verify the fix with browser accessibility tooling"), a minor validation gap.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep pointer to references/rule.md for "full implementation details, code examples, and framework-specific guidance"; the referenced file exists and contains no nested references, so navigation is easy and content is appropriately split.

5 / 5

Total

17

/

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.

A solid description with an explicit "Use when" trigger and several concrete inspection actions, written in the imperative style of the good examples. Its weaknesses are an awkward rule-name insertion instead of natural trigger synonyms, a "what" that describes procedure rather than purpose, and a generic accessibility-review preamble that risks collisions with sibling rules.

Suggestions

Replace "related to Use correct list structure" with natural trigger phrases users would say, e.g. "Use when auditing HTML lists, ul/ol markup, or accessibility issues with list structure".

State the skill's purpose up front in third person, e.g. "Verifies that ul/ol elements contain only li children and guides fixes for incorrect list markup".

Add distinguishing keywords (accessibility, a11y, screen readers, ul/ol/li) so it does not compete with sibling accessibility rules sharing the same generic "reviewing rendered HTML" trigger.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but it never states the skill's outcome and the phrase "related to Use correct list structure" reads as a tacked-on rule name rather than a capability, leaving minor gaps in coverage.

4 / 5

Completeness

Both are present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns" trigger plus a what ("Check native semantics first, then inspect..."). It falls short of 5 because the "what" describes an inspection procedure rather than clearly stating what the skill does (verify and fix list markup).

4 / 5

Trigger Term Quality

Natural terms like "rendered HTML", "list structure", "focus flow", and "screen-reader output" are present, but common variations users would actually say — "accessibility", "a11y", "ul/ol/li", "lists" — are missing, which fits good-but-incomplete keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The generic preamble "reviewing rendered HTML, interactive components, or design-system patterns" would equally trigger every sibling accessibility rule in the same family; distinctiveness rests entirely on the appended rule name "Use correct list structure", so overlap with closely related skills remains likely.

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/list-structure/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.