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

60%

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

Quality

Content

53%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 well-structured and token-efficient with a clean one-level reference, but its guidance is abstract rather than executable and lacks verification checkpoints for confirming a fix.

Suggestions

Add a concrete detection method in the Check section, e.g. a DevTools snippet like `document.querySelectorAll('[id]')` grouped by repeated id, or an axe-core rule reference.

Include a short before/after markup example in the Fix section showing a duplicate id being made unique.

Add a verification step (e.g. re-run the duplicate-id scan or check focus order with the browser accessibility inspector) so the workflow has an explicit validation checkpoint.

Dimension	Reasoning	Score
Conciseness	Sections are lean and assume Claude's competence (no explanation of what HTML or IDs are); the single opening sentence on why duplicates matter is the only mild over-explanation, keeping it just below a 5.	4 / 5
Actionability	Guidance is high-level ("Search for duplicate id attributes", "Assign a unique id to each active element") with no concrete selectors, commands, or code in the body, matching 'minimal concrete guidance; high-level hints but missing specific steps'.	2 / 5
Workflow Clarity	The Check/Fix/Explain/Code Review sections give a rough sequence, but there are no validation checkpoints or feedback loops for verifying the fix, matching 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Clear section structure with a well-signaled one-level-deep pointer to references/rule.md (verified to exist); not a 5 because the body inlines some content that overlaps the reference and the pointer could be more prominent.	4 / 5
	Total	13 / 20 Passed

Description

67%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 provides concrete inspection actions and an explicit Use-when trigger, but embeds the rule title awkwardly and omits the rule-specific natural keywords (duplicate id, focusable elements) that a user would actually say.

Suggestions

Reword the trigger clause so the rule name is not embedded mid-sentence, e.g. 'Use when auditing rendered HTML for duplicate id attributes on focusable or active elements.'

Add the rule-specific natural trigger terms ('duplicate id', 'id attribute', 'focusable elements', 'ARIA') so users searching for this exact issue will match.

Tighten the 'what' to a single concrete verb phrase rather than a layered review/inspect list.

Dimension	Reasoning	Score
Specificity	Lists several concrete inspection actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), placing it at the 'several specific actions, minor gaps' anchor; not a 5 because coverage is not exhaustive.	4 / 5
Completeness	Both the 'what' (review/inspect active elements) and an explicit 'Use when...' clause are present; not a 5 because the when-clause is tangled with the embedded rule title and could be more explicit.	4 / 5
Trigger Term Quality	Contains relevant general a11y-review terms ("rendered HTML", "interactive components", "keyboard behavior", "screen-reader output") but misses the rule-specific natural triggers ("duplicate id", "id attribute", "focusable elements"), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Narrowed by the specific rule reference ("Use unique IDs for active elements"), giving a mostly distinct niche; not a 5 because the broad 'reviewing rendered HTML, interactive components, or design-system patterns' framing overlaps with general accessibility skills.	4 / 5
	Total	15 / 20 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/duplicate-id-active/SKILL.md
Commit: 30756a7

Reviewed: 22 days 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.