listitem

Use when applies to HTML documents with `<li>` elements. Also applies to custom ARIA lists where `role='listitem'` must be owned by `role='list'`. Common violations occur in templating systems where list markup is split across components or in CSS resets where developers use `<li>` for layout without proper list parents.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/listitem/SKILL.md

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 well-structured and actionable, with a concrete check/fix procedure and a clean single-reference progressive-disclosure design. Its main weakness is redundancy between the intro, Quick Reference, and Explain sections, plus a generic templated Code Review section that adds little.

Suggestions

Merge the 'Explain' section into the intro or Quick Reference — the spec requirement, screen-reader announcement behavior, and `list-style: none` caveat are each stated twice.

Trim the generic 'Code Review' boilerplate ('Review the rendered markup and interactive states that affect...') to one concrete sentence about what to flag and how to verify with axe/Lighthouse or the browser accessibility tree.

Shorten the intro's screen-reader narration to one line; the per-screen-reader detail (NVDA, JAWS, VoiceOver) is context Claude already has and belongs in the reference file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the 'Explain' section re-states material already covered (spec requirement, screen-reader announcement behavior, the `list-style: none` caveat appears in both the intro and Explain), and the 'Code Review' section is templated filler ('Review the rendered markup and interactive states that affect...'). The intro also over-explains screen-reader behavior Claude largely knows.	3 / 5
Actionability	The Check section gives concrete, executable criteria ('check that its direct parent element is `<ul>`, `<ol>`, or `<menu>`; flag any `<li>` whose parent is `<div>`, `<section>`, `<nav>`, `<span>`') and the Fix section gives numbered, specific remedies. Minor gap: no code example inline (they live in references/rule.md), which is acceptable for an instruction-only skill.	4 / 5
Workflow Clarity	A clear Check → Fix → Explain → Code Review sequence exists, and verification is mentioned ('note how to verify the fix with browser accessibility tooling or assistive tech'), but concrete verification steps are deferred to the reference file rather than stated as explicit checkpoints in the body — a minor validation gap.	4 / 5
Progressive Disclosure	The body is a well-organized ~45-line overview with clear section headers, and it cleanly offloads implementation details to a single one-level-deep reference that exists ('For full implementation details, code examples, and framework-specific guidance, see `references/rule.md` — verified present on disk). Navigation is easy and nothing is nested beyond one level.	5 / 5
	Total	16 / 20 Passed

Description

51%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 identifies a distinct, well-scoped niche (list-item container semantics in HTML/ARIA) but never states what the skill does, and its opening clause "Use when applies to" is grammatically broken, leaving the capability entirely implicit. Trigger-term coverage is good though it misses a few natural synonyms.

Suggestions

State the 'what' explicitly, e.g., 'Checks that every `<li>` element and `role='listitem'` sits inside a valid list container (`<ul>`, `<ol>`, `<menu>`, or `role='list'`) and flags/fixes orphan list items. Use when reviewing HTML or templates for list semantics, accessibility, or invalid list markup.'

Fix the broken opening clause 'Use when applies to HTML documents' into a proper trigger phrase such as 'Use when reviewing or fixing HTML documents with `<li>` elements'.

Add natural synonyms users would say — 'list items', 'unordered/ordered lists', 'screen readers', 'accessibility' — to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("HTML documents with `<li>` elements", "custom ARIA lists where `role='listitem'` must be owned by `role='list'") but lists no concrete actions the skill performs — no checking, flagging, or fixing verbs, and the opening "Use when applies to" is broken phrasing that conveys no capability.	2 / 5
Completeness	Only a 'when' is present ("Use when applies to HTML documents with `<li>` elements") and the 'what' — what the skill actually does — is never stated, matching the anchor 'only when is present without what' (e.g., 'Use when working with documents'). The rule context hints at the topic but not the skill's action.	2 / 5
Trigger Term Quality	Good keyword coverage for the niche: "HTML documents", "`<li>` elements", "ARIA lists", "role='listitem'", "role='list'", "templating systems", "CSS resets". A few natural terms are missing — plain phrases like "list items", "unordered list", and "accessibility"/"screen readers" that users would commonly say.	4 / 5
Distinctiveness Conflict Risk	Clear niche with distinct triggers: orphan `<li>`/`role='listitem'` ownership in HTML and ARIA lists is highly specific and unlikely to fire for unrelated skills. It is clearly distinguishable from generic HTML or accessibility skills.	5 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/listitem/SKILL.md
Commit: 7bfd868

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.