CtrlK
BlogDocsLog inGet started
Tessl Logo

unique-id

Use when reviewing templates, rendered HTML, or shared components related to Ensure all IDs are unique. Validate the final browser-facing markup, not just the source framework abstraction.

60

Quality

70%

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

Quality

Content

72%

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 tight, well-structured overview that delegates detail to a single real reference file, but it lacks executable code and an explicit post-fix verification step in the workflow.

Suggestions

Add a short executable snippet for finding duplicate IDs (e.g., a querySelectorAll scan) so the Check/Fix steps are actionable without leaving SKILL.md.

Add an explicit verification checkpoint after Fix (e.g., 're-scan the rendered HTML to confirm no duplicate IDs remain and that label/ARIA references resolve') to close the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids padded concept explanations; the only inefficiency is the 4th Quick Reference bullet nearly duplicating the intro line.

3 / 3

Actionability

It names concrete targets ('labels, ARIA attributes, or JavaScript selectors', 'component libraries') but provides no executable code or commands in the body itself, only descriptive directives.

2 / 3

Workflow Clarity

Check -> Fix -> Explain -> Code Review gives a sequence, but there is no explicit validate-after-fix checkpoint for what are destructive markup edits, capping clarity at 2 per the rubric note.

2 / 3

Progressive Disclosure

A concise overview with well-organized sections and a clearly signaled, one-level-deep pointer to the existing 'references/rule.md' for details; content is appropriately split.

3 / 3

Total

10

/

12

Passed

Description

67%

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 has an explicit 'Use when' trigger and states what to validate, but its action vocabulary is generic and its trigger phrasing overlaps with related skills in the same checklist family.

Suggestions

Add concrete, user-natural trigger terms such as 'duplicate IDs', 'same id', and 'id attributes' so the description matches how users actually phrase the need.

List specific concrete actions (e.g., 'find duplicate id attributes, fix references in labels/ARIA/JS selectors') instead of the generic 'reviewing'/'Validate' verbs to lift specificity.

Lead with the unique-ID niche (e.g., 'Use when checking rendered HTML for duplicate id attributes') so it is distinguishable from sibling HTML-review skills.

DimensionReasoningScore

Specificity

Names the domain and a couple of actions ('reviewing templates, rendered HTML, or shared components', 'Validate the final browser-facing markup') but does not list multiple specific concrete actions like the score-3 anchor.

2 / 3

Completeness

Explicitly answers both when ('Use when reviewing templates, rendered HTML, or shared components related to Ensure all IDs are unique') and what ('Validate the final browser-facing markup, not just the source framework abstraction') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes relevant terms ('templates', 'rendered HTML', 'shared components', 'browser-facing markup') but misses common user phrasings such as 'duplicate IDs', 'same id', or 'id attributes'.

2 / 3

Distinctiveness Conflict Risk

The 'reviewing templates, rendered HTML, or shared components' trigger overlaps with sibling frontend-checklist skills; only the embedded rule name 'Ensure all IDs are unique' distinguishes it, so conflict risk remains.

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.