CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, well-structured overview that defers detail to a single reference file; it is actionable but slightly padded with concepts Claude already knows and lacks an explicit verification checkpoint.

Suggestions

Trim the restated screen-reader explanation in the intro and 'Explain' sections, since Claude already knows how list semantics are announced.

Add an explicit verify step (e.g., confirm 'list with X items' announcement via axe or a screen reader) to turn the review lenses into a sequenced, checkpointed workflow.

Replace the repeated boilerplate 'Use semantic list elements' phrasing with tighter, direct instructions.

DimensionReasoningScore

Conciseness

Mostly efficient, but the intro and 'Explain' section restate the screen-reader announcement concept Claude already knows, and 'Use semantic list elements' is repeated as templated filler.

2 / 3

Actionability

Gives concrete element-level guidance — 'Use ul/ol/dl', 'Use li', 'proper dt/dd' — which is specific and directly actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Check/Fix/Explain/Code Review read as parallel review lenses rather than a sequenced process, and there are no explicit validation checkpoints between steps.

2 / 3

Progressive Disclosure

A concise overview with well-signaled, one-level-deep pointer to the verified 'references/rule.md' for implementation details and examples.

3 / 3

Total

10

/

12

Passed

Description

92%

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 strong description with explicit triggers and concrete review actions; its main weakness is overlap risk with other accessibility rule skills because the trigger surface is broad.

Suggestions

Narrow the 'Use when' clause toward list-specific triggers (e.g., 'lists, navigation menus, step sequences, or definition/glossary markup') to reduce conflict with sibling a11y skills.

Remove the awkward templated phrase 'related to Use semantic list elements' which reads as boilerplate rather than natural guidance.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (check semantics, inspect keyboard/focus/names/screen-reader) and when via the 'Use when reviewing...' trigger clause.

3 / 3

Trigger Term Quality

Uses natural accessibility-review phrasing a user would say — 'rendered HTML, interactive components, keyboard behavior, focus flow, accessible names, screen-reader output'.

3 / 3

Distinctiveness Conflict Risk

Anchored to the specific rule, but the broad triggers 'rendered HTML, interactive components, or design-system patterns' would plausibly fire for sibling accessibility rule skills.

2 / 3

Total

11

/

12

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.