CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dlitem

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Wrap definition items in a definition list. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

81%

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

85%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 well-structured, lean single-rule skill: an unambiguous check/fix workflow with a verification note, and clean progressive disclosure to a real one-level-deep reference file. The only notable flaws are minor duplication between Quick Reference and the Check/Fix sections and the use of escaped HTML entities instead of literal tags, which makes the guidance read as "&lt;dt&gt;" rather than "<dt>".

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — a one-line rationale, then Check/Fix/Explain/Code Review sections with no concept explanations Claude already knows. It falls short of anchor 5 only because the Quick Reference bullets ("Place all dt (terms) and dd (descriptions) within a dl") duplicate the Check and Fix sections.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: "Locate any dt or dd elements that are not children of a dl element" and "Wrap orphaned dt and dd elements in a parent dl container". It misses anchor 5 because no correct/bad markup example appears at the top level (it is deferred to the reference) and the escaped entity text ("&lt;dt&gt;" rather than "<dt>") slightly muddies the literal guidance.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (under 50 lines, one task) and the single action is unambiguous: Check defines detection, Fix defines the remedy, and the Code Review section closes the loop with "note how to verify the fix with browser accessibility tooling or assistive tech". Per the simple-skill guideline this earns the top score.

5 / 5

Progressive Disclosure

A clear overview with one well-signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and genuinely holds the details (code examples, why-it-matters, validation guidance, tooling links). Content is appropriately split between overview and reference with easy navigation.

5 / 5

Total

18

/

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" clause, third-person voice, and several concrete inspection actions. Its main weaknesses are the generic, family-wide trigger surface that risks conflicts with sibling accessibility skills, and the absence of the rule's distinctive vocabulary (dl/dt/dd, definition list terms) in the trigger.

Suggestions

Narrow the trigger clause to rule-specific phrases, e.g., "Use when reviewing markup that contains dt, dd, or dl elements, definition/description lists, or glossary markup" — this both sharpens the 'when' and supplies the missing natural keywords.

Drop or de-emphasize the generic triggers ("interactive components, or design-system patterns") that would fire for every sibling accessibility rule skill.

State the core capability in the 'what' portion (e.g., "locate dt/dd elements not contained in a dl and flag them") so the description covers what the skill actually does, not just how to inspect.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — which goes beyond naming the domain. It stops short of anchor 5 because the actions are generic review verbs and never state the rule's core operation (verifying dt/dd are children of a dl, or wrapping orphans).

4 / 5

Completeness

Both parts are explicitly present: the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Wrap definition items in a definition list" trigger clause. It is not a 5 because the 'when' leans on the rule title rather than concrete trigger phrases (e.g., mentions of dt/dd/dl or definition-list audits).

4 / 5

Trigger Term Quality

Good keyword coverage including natural phrases like "rendered HTML", "definition list", "keyboard behavior", "focus flow", "accessible names", and "screen-reader output". It misses a few natural terms users would actually say for this rule — the element names dl/dt/dd, "glossary", and "accessibility/a11y" — so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The only narrow differentiator is "related to Wrap definition items in a definition list"; the rest of the trigger surface — "reviewing rendered HTML, interactive components, or design-system patterns" plus keyboard/focus/screen-reader inspection — would match virtually every sibling accessibility-rule skill. This is somewhat specific but carries real overlap risk with similar skills (anchor 3), not the minor overlap of anchor 4 and not the unqualified breadth of anchor 2.

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