CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

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

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 a well-structured, actionable rule evaluation with excellent progressive disclosure — concrete detection criteria, three specific fix paths, and a verified one-level-deep reference holding the code examples and verification details. Its main weakness is redundancy: screen-reader rationale is explained twice, Quick Reference bullets restate other sections, and the Code Review section is generic boilerplate that could be cut or made rule-specific.

Suggestions

Merge the opening paragraph into the Explain section — both cover screen-reader announcement loss ('NVDA and JAWS will not say list of 5 items', 'announce the list type and the total item count').

Trim the Quick Reference bullets that restate Check/Explain content, keeping only the parent-element rule and the ARIA ownership requirement once.

Replace the generic Code Review boilerplate ('Flag exact elements, roles, labels, focus behavior, or keyboard interactions...') with rule-specific review guidance, or fold it into Check and cite references/rule.md's Verification section.

DimensionReasoningScore

Conciseness

The body is mostly efficient and contains non-obvious, valuable specifics (NVDA/JAWS/VoiceOver announcement behavior, the 'list-style: none' semantics-stripping caveat), but it has real duplication: the intro paragraph and the Explain section both cover screen-reader announcement loss, the Quick Reference bullets restate rules already given in Check and Explain ('Similarly, role='listitem' must be owned by a role='list''), and the Code Review section is generic boilerplate applicable to any accessibility rule ('Flag exact elements, roles, labels, focus behavior, or keyboard interactions... browser accessibility tooling'). This matches anchor 3 — some unnecessary explanation that could be tightened — rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

The Check section is a concrete, executable procedure ('check that its direct parent element is `<ul>`, `<ol>`, or `<menu>`. Flag any `<li>` whose parent is `<div>`, `<section>`, `<nav>`, `<span>`...') and Fix gives three specific, numbered remediation paths with exact replacement elements. This matches anchor 4; not 5 because the body contains no code examples (deferred to references/rule.md) and one check is slightly vague ('their closest ancestor with a list-related role'), and not 3 because the guidance is genuinely concrete rather than pseudocode-level.

4 / 5

Workflow Clarity

The Check → Fix → verify sequence is clear and the single evaluation task is unambiguous, with verification pointed to in the Code Review section ('note how to verify the fix with browser accessibility tooling or assistive tech'). This matches anchor 4: clear sequence with most checkpoints present but a minor validation gap — the body's verification is generic, with the concrete checks (axe, Lighthouse, keyboard testing) deferred to references/rule.md. Not 5 because the in-body validation checkpoint is not explicit or specific; not 3 because the sequence is coherent and checkpoints are present.

4 / 5

Progressive Disclosure

The ~30-line body is well organized into Quick Reference, Check, Fix, Explain, and Code Review sections, keeps code examples and detailed verification appropriately out of the main file, and clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`') — a file verified to exist and to contain exactly that deferred content. This matches anchor 5: clear overview with well-signaled one-level-deep references and appropriately split content.

5 / 5

Total

16

/

20

Passed

Description

61%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 excels at concrete domain scoping and explicit 'when' guidance with distinct, technical trigger terms, but it never states what the skill does — the capability (checking and fixing list-item placement) is left entirely implicit. Adding an action statement and a few user-natural terms like 'accessibility' or 'orphan list items' would raise it substantially.

Suggestions

Open with an explicit capability statement using action verbs, e.g. 'Checks that every `<li>` element has a `<ul>`, `<ol>`, or `<menu>` parent and flags orphan list items with concrete fixes.'

Add natural trigger terms users would actually say — 'accessibility', 'screen readers', 'semantic HTML', 'orphan list items' — alongside the existing technical vocabulary.

State the skill's deliverable (detection criteria, remediation steps, and verification guidance) so the 'what' is explicit rather than inferred from rule conditions.

DimensionReasoningScore

Specificity

The description names the domain concretely ('HTML documents with `<li>` elements', 'custom ARIA lists where `role='listitem'` must be owned by `role='list'`', 'templating systems where list markup is split across components', 'CSS resets where developers use `<li>` for layout') but never states what the skill actually does — no action verbs like check, flag, or fix appear. This matches anchor 3's concrete-but-incomplete coverage; it is not 4 because several specific actions are absent, and not 2 because the language is rich with concrete specifics rather than minimal or generic.

3 / 5

Completeness

The 'when' is explicit and detailed ('Use when applies to HTML documents with `<li>` elements. Also applies to custom ARIA lists...'), but the 'what' is only implied through rule-scope conditions ('must be owned by `role='list'`', 'without proper list parents') — the skill's function is never stated. This sits between anchor 2 ('only when present without what') and anchor 3; the strongly conveyed subject matter lifts it to 3, while the absent capability statement keeps it below 4.

3 / 5

Trigger Term Quality

Good keyword coverage: '<li> elements', 'ARIA lists', "role='listitem'", "role='list'", 'list markup', 'templating systems', 'CSS resets', 'list parents'. These are the natural technical terms for this problem, matching anchor 4. It is not 5 because common natural phrasings a user might say — 'accessibility', 'screen readers', 'semantic HTML', 'orphan list items' — are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — orphan `<li>` detection and ARIA listitem role ownership are specific triggers — but the opening clause 'Use when applies to HTML documents with `<li>` elements' is broad enough to fire on virtually any HTML work, creating minor overlap risk with sibling HTML/accessibility rules. This matches anchor 4; not 5 because of that broad opening trigger, not 3 because the core triggers (role='listitem' ownership, templating/CSS-reset violations) are highly specific.

4 / 5

Total

14

/

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/listitem/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.