CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

duplicate-id-aria

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

Quality

74%

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

Quality

Content

63%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 compact, well-structured review skill with clear Check/Fix/Explain sections and exemplary use of a single real reference file. The weaker spots are redundant restatements of the same rule across four sections and a Fix section that names the goal rather than a concrete remediation method.

Suggestions

Collapse the three near-identical Quick Reference bullets into one and drop the 'Explain' section's restatement of known ARIA behavior.

Make the Fix section concrete: name the actual remediation (generate unique IDs, e.g. React's useId, and update every aria-* reference), or surface the good/bad markup example from references/rule.md inline.

Add an explicit post-fix verification step (re-run an axe/Lighthouse check or re-inspect the accessibility tree) to the body's sequence.

DimensionReasoningScore

Conciseness

The body is compact but redundant: the three Quick Reference bullets ('Ensure IDs referenced by ARIA attributes... are unique', 'Avoid duplicate IDs that lead to ambiguous accessibility relationships', 'Verify that ARIA controls correctly target their intended elements') each restate the same single rule, and the intro plus the 'Explain' section re-explain duplicate-ID behavior Claude already knows. More than minor trimming is needed, though there is no tutorial-style padding.

3 / 5

Actionability

The Check section gives a precise, actionable criterion ('Identify elements where an ARIA attribute references an id that appears multiple times in the DOM'), but the Fix section only restates the goal ('Ensure all elements referenced by ARIA attributes have unique IDs and update the references accordingly') without a method, and the body contains no commands, selectors, or example markup — all executable detail is deferred to references/rule.md.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with headed sections, and the Code Review section includes verification guidance ('note how to verify the fix with browser accessibility tooling or assistive tech'). Verification is a passing mention rather than an explicit checkpoint and there is no re-check loop after fixing, so it falls short of the top anchor.

4 / 5

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that file exists with real, well-organized content (code examples, tools, verification steps) rather than nested pointers. Content is appropriately split between overview and reference.

5 / 5

Total

15

/

20

Passed

Description

75%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' trigger and several concrete inspection actions. Its main defects are a template-substitution artifact ('related to Use unique IDs for ARIA references') that garbles the core capability, and missing natural trigger terms such as 'accessibility', 'a11y', and 'duplicate id'.

Suggestions

Rewrite the trigger clause to remove the inline rule-name artifact, e.g. 'Detect duplicate element IDs referenced by ARIA attributes (aria-labelledby, aria-describedby, aria-controls) in rendered HTML'.

Add natural trigger terms users would actually say: 'accessibility', 'a11y', 'duplicate id', and specific attribute names like aria-labelledby.

State the core 'what' as an explicit action (flag elements whose ARIA references resolve to a duplicated id) instead of relying on the rule title.

DimensionReasoningScore

Specificity

Lists several concrete inspection actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), but the core capability is only conveyed through the awkward inline phrase 'related to Use unique IDs for ARIA references', leaving minor gaps in coverage.

4 / 5

Completeness

Both parts are present: an explicit 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns') and a 'what' (the concrete inspection actions). Not a 5 because the actual capability — flagging duplicate IDs referenced by ARIA attributes — is stated only through the garbled rule-name insertion rather than explicitly.

4 / 5

Trigger Term Quality

Good keyword coverage including 'rendered HTML', 'interactive components', 'ARIA references', 'keyboard behavior', 'focus flow', 'accessible names', and 'screen-reader output', but common natural terms are missing: 'accessibility'/'a11y' never appears, 'duplicate id' as users phrase it is absent, and attribute names like aria-labelledby appear only in passing.

4 / 5

Distinctiveness Conflict Risk

The trigger names a specific niche ('Use unique IDs for ARIA references') that distinguishes it from sibling rules, but the generic inspection list ('keyboard behavior, focus flow, accessible names, and screen-reader output') likely repeats across related accessibility-review skills, creating minor overlap risk.

4 / 5

Total

16

/

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