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

71%

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

85%

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-organized and actionable, with a clean review workflow and proper progressive disclosure to a real reference file. Its only real weakness is mild verbosity from re-explaining screen-reader/HTML concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but the Explain section re-explains screen-reader behavior and HTML validity that Claude already knows, and Quick Reference overlaps the Check/Explain content — matching 'mostly efficient but includes some unnecessary explanation or could be tightened'.	2 / 3
Actionability	Check gives concrete, specific criteria (flag `<li>` whose parent is `<div>`, `<section>`, `<nav>`, `<span>`, etc.) and Fix gives numbered, specific remediation steps; for an instruction-only review skill this is concrete and actionable, so the absence of inline code is not penalized.	3 / 3
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is clear, Fix is numbered, and verification is surfaced ('note how to verify the fix with browser accessibility tooling or assistive tech'); for a simple single-purpose skill this is well-organized enough for the top anchor.	3 / 3
Progressive Disclosure	SKILL.md is a lean overview with clearly signaled one-level-deep navigation to `references/rule.md` ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that referenced file exists, matching 'clear overview with well-signaled one-level-deep references'.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 accessibility niche and gives a 'Use when' trigger, but it never states the skill's actions and relies on technical jargon over natural user phrasing, leaving what/when only half explicit. It sits at the mid-band on most dimensions.

Suggestions

Add an explicit action verb up front, e.g. 'Checks that every `<li>` is a direct child of `<ul>`, `<ol>`, or `<menu>` and flags orphan list items' so the 'what' is stated, not implied.

Include natural user phrasing alongside the technical terms — 'list items', 'screen reader announcements', 'navigation menus' — to broaden trigger coverage.

Fix the grammatically odd opener 'Use when applies to...' (missing subject) to a clean trigger such as 'Use when reviewing HTML for list-item containment or ARIA list ownership issues.'

Dimension	Reasoning	Score
Specificity	Names the concrete domain (`<li>` elements, ARIA `role='listitem'`/`role='list'`) and specific violation contexts (templating systems, CSS resets), but states no actions the skill performs (e.g. check, flag, fix) — closer to 'names domain and some actions, but not comprehensive' than the multiple-concrete-actions anchor.	2 / 3
Completeness	The 'Use when...' trigger clause is present ('Use when applies to HTML documents with `<li>` elements'), but what the skill does is only implied (no verb like 'Checks/Flags orphan list items'), so one side of what+when is not explicit — capping completeness at 2 per the missing-side guideline.	2 / 3
Trigger Term Quality	Relevant keywords are present (`<li>` elements, ARIA lists, templating systems, CSS resets) but the phrasing leans technical (`role='listitem' must be owned by role='list'`) and omits natural variations like 'list items', 'screen reader', or 'navigation list', matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche (list-item containment and ARIA listitem ownership) with distinct triggers unlikely to fire for unrelated skills, matching 'clear niche with distinct triggers; unlikely to conflict'.	3 / 3
	Total	9 / 12 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: 48405aa

Reviewed: about 10 hours 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.