CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

69%

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

50%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 compact, well-structured overview that correctly delegates detail to references/rule.md, but it offers no executable detection or verification method — the Check and Fix steps are high-level directions rather than something Claude can run. Some redundancy between the intro, Quick Reference, and Check sections could be trimmed.

Suggestions

Add a concrete detection method in the Check section, e.g., a one-line command or snippet to find duplicate IDs in rendered HTML (such as querying all [id] attributes and checking for repeats).

Add an explicit validation step after Fix (re-scan the rendered markup to confirm no duplicate IDs remain and that label/ARIA/selector references still resolve).

Trim the Quick Reference bullets that restate the opening sentence and the Check/Fix sections to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is short, but the 'Quick Reference' bullets largely restate the opening sentence and the Check/Fix sections (e.g., 'Duplicate IDs break form labels, ARIA, and getElementById' appears in both the intro and the bullet list, and uniqueness is stated three times). This repetition plus the vague 'Explain' section matches 'mostly efficient but includes some unnecessary explanation or could be tightened', not 4, which requires only minor trimmable instances.

3 / 5

Actionability

Guidance stays at the hint level: 'Scan this HTML document to ensure all ID attributes are unique' and 'Remove duplicate ID values... update any references' give no executable method — no command, script, or selector to actually detect duplicates. This matches anchor 2 ('high-level hints but missing the specific steps to execute'); it is above anchor 1 because the actions to perform are named, and below anchor 3 because there is no concrete detection/fix mechanism at all.

2 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a recognizable sequence for a review skill, but there is no validation checkpoint (e.g., re-scan the rendered markup to confirm duplicates are gone after fixing). This fits anchor 3 ('sequence present but checkpoints missing or implicit'); it cannot score 4 without at least an explicit verify-after-fix step.

3 / 5

Progressive Disclosure

The body is a lean overview under 50 lines, and implementation details are appropriately split into the real, one-level-deep bundle file, clearly signaled: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' (the file exists in the bundle). Sections are well-organized with no inlined content that belongs in the reference, matching the clear-overview anchor.

5 / 5

Total

13

/

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.

The description explicitly answers both what (ensure unique IDs, validate rendered markup) and when (reviewing templates, rendered HTML, or shared components), with mostly natural trigger terms. Its weaknesses are the templated, slightly awkward phrasing ('related to Ensure all IDs are unique') and a trigger clause that likely collides with sibling rule skills.

Suggestions

Reword the templated phrase 'related to Ensure all IDs are unique' into a natural action, e.g., 'Ensures all ID attributes are unique within a document'.

Add natural synonyms to the trigger clause such as 'duplicate IDs' or 'ID conflicts' so users searching those phrases match this skill.

Differentiate the 'when' clause from sibling rule skills by mentioning the concrete failure modes users would report (broken labels, ARIA, getElementById).

DimensionReasoningScore

Specificity

The description names the domain ("Ensure all IDs are unique", "rendered HTML") and two concrete actions ("reviewing templates... or shared components", "Validate the final browser-facing markup"), but coverage is not comprehensive — it never mentions detecting/removing duplicates or fixing references. It sits at the 'names domain and 1-2 concrete actions' anchor, not 4, because it lists only two generic review actions with minor gaps unmet.

3 / 5

Completeness

Both parts are explicitly present: the 'when' via "Use when reviewing templates, rendered HTML, or shared components related to..." and the 'what' via "Ensure all IDs are unique. Validate the final browser-facing markup, not just the source framework abstraction." This matches anchor 5 with concrete trigger phrases and an explicit what-and-when pair; it is above anchor 4 because the 'when' clause is explicit rather than merely improvable.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say when reviewing frontend markup: "reviewing templates, rendered HTML, or shared components" and "browser-facing markup". A few natural terms are missing — "duplicate IDs", "ID conflicts", or "markup review" — so it does not reach the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The unique-ID rule itself is a specific niche, but the trigger clause ("reviewing templates, rendered HTML, or shared components related to <rule>") is a generic pattern that would overlap with sibling frontend-checklist rule skills sharing the same trigger phrasing. It fits 'somewhat specific but could still overlap with similar skills' rather than 4, where overlap would be limited to closely related skills only.

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/unique-id/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.