CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

duplicate-id-active

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use unique IDs for active elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

76%

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/duplicate-id-active/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-organized, lean overview with a clean one-level-deep pointer to references/rule.md, but the in-body guidance stays high-level — no concrete detection command or explicit verification step — leaving execution details entirely to the reference file.

Suggestions

Add one concrete detection step to the Check section, e.g. a grep pattern for repeated id="..." values or a browser snippet like grouping document.querySelectorAll('[id]') to spot duplicates.

Make verification an explicit step in the body (e.g. "After fixing, re-run axe/Lighthouse and re-test keyboard navigation") rather than only instructing the reviewer to note how to verify.

Merge or drop the Quick Reference bullets, since they restate the intro sentence and the rule itself three times over.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with clear sections, but the intro sentence and the Quick Reference bullets ("Avoid duplicate IDs that can break keyboard navigation and focus management") restate the same rule three ways and restate knowledge Claude already has, so minor trimming is possible.

4 / 5

Actionability

"Search for duplicate id attributes on focusable or active HTML elements" names the target but gives no method (no grep pattern, selector, or axe/Lighthouse invocation in the body), and "Assign a unique id to each active element" is a generic one-liner — some concrete guidance with key execution details left to the reference file.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review is a clear sequence for this simple skill, and the Code Review section says to "note how to verify the fix with browser accessibility tooling", but there is no explicit validate-after-fix checkpoint step in the body itself — a minor validation gap.

4 / 5

Progressive Disclosure

The body is a concise overview and the sole reference is one level deep, clearly signaled ("see `references/rule.md`"), and the file exists containing the promised implementation details, code examples, and validation tools — a clean overview-to-detail split.

5 / 5

Total

16

/

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.

The description covers both what and when with several concrete review actions, but the templated phrasing ("related to Use unique IDs for active elements") reads awkwardly and omits the most natural trigger terms such as "duplicate IDs" and "accessibility".

Suggestions

Replace the inlined rule title with natural trigger phrasing, e.g. "Use when auditing rendered HTML for duplicate id attributes on links, buttons, and inputs".

Add the natural synonyms users would actually say — "duplicate IDs", "accessibility", "a11y", "axe" — to the trigger clause.

Ground the when-clause in user-recognizable scenarios (e.g. "when the user reports keyboard focus landing on the wrong control or a screen reader skipping buttons") instead of restating the rule title.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" lists several concrete review actions, but the awkwardly inlined title "related to Use unique IDs for active elements" blurs the action list, keeping it below anchor 5 and above anchor 3 (more than 1-2 actions).

4 / 5

Completeness

Both "what" ("Check native semantics first, then inspect keyboard behavior...") and "when" ("Use when reviewing rendered HTML, interactive components, or design-system patterns") are present, but the when-clause circularly restates the rule's own title rather than naming concrete user triggers, falling short of anchor 5.

4 / 5

Trigger Term Quality

Terms like "rendered HTML", "interactive components", "keyboard behavior", and "screen-reader output" are natural phrases, but the most common user trigger words for this rule — "duplicate IDs", "accessibility", "a11y" — are missing, matching the "good coverage, a few natural terms missing" anchor.

4 / 5

Distinctiveness Conflict Risk

The generic opening "Use when reviewing rendered HTML, interactive components, or design-system patterns" would equally match many sibling accessibility-rule skills; only the appended rule title distinguishes it, so overlap with closely related skills remains likely.

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/duplicate-id-active/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.