CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

identical-links-same-purpose

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure identical links have consistent destinations. 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/identical-links-same-purpose/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.

A lean, well-structured skill body with a clear Check/Fix/Explain flow and exemplary progressive disclosure to a single real reference file. Its main weakness is redundancy — the core rationale is repeated across three sections and the Code Review section duplicates the frontmatter description almost word-for-word.

Suggestions

Merge the intro paragraph, the third Quick Reference bullet, and the Explain section into a single rationale statement — the same screen-reader link-list point is made three times.

Rewrite the Code Review section with skill-specific guidance (e.g., how to flag elements, which selector or link-list technique to use) instead of restating the frontmatter description.

Make verification an explicit final step naming a concrete technique or tool rather than only mentioning "browser accessibility tooling or assistive tech" in passing.

DimensionReasoningScore

Conciseness

The same rationale (identical text → different destinations confuses users, especially screen-reader users navigating by link list) is stated three times — in the intro paragraph ("creates confusion and unpredictability, especially for users who rely on a list of links"), the Quick Reference bullet ("Reduces confusion for screen reader users navigating by link list"), and the Explain section — and the Code Review section restates the frontmatter description nearly verbatim. Mostly efficient but includes repetition that could be tightened into one place; it avoids score 4 because the duplication is more than minor, and stays above 2 because there is no padding explaining concepts Claude already knows.

3 / 5

Actionability

The Check section gives a direct, executable instruction ("Identify any links on the page that have identical link text but point to different URLs") and Fix gives the concrete remedy ("Change the link text to be unique for each destination"), with code examples deferred to a real reference file. Mostly executable with minor gaps — no detection method or specific tooling is named in the body — which fits 4 rather than 5; not 3 because the guidance is concrete and specific, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, coherent sequence, and the Code Review section names verification ("note how to verify the fix with browser accessibility tooling or assistive tech"). It fits 4 — clear sequence with most checkpoints present but verification left implicit rather than an explicit step — rather than 5, where validation would be an explicit checkpoint. No destructive/batch cap applies since this is a review task.

4 / 5

Progressive Disclosure

The body is a short, well-sectioned overview that appropriately defers detail: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a clearly signaled, one-level-deep reference that exists in the bundle and itself contains the code examples without further nesting. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

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.

A solid description with an explicit 'Use when...' trigger and a concrete, ordered list of inspection actions. Its main weaknesses are templated breadth in the trigger framing that blurs distinctiveness against sibling accessibility skills, and awkward embedding of the rule title as a noun phrase.

Suggestions

Rewrite the trigger to name the concrete symptom users would mention, e.g. "Use when links with the same text (e.g. 'Read more', 'Click here') point to different URLs" — this adds natural synonyms and sharply reduces overlap with sibling accessibility skills.

State the remediation capability explicitly (e.g. "differentiate the link text or add accessible names so identical links have consistent destinations") so the 'what' covers both checking and fixing.

Drop or integrate the awkward "related to Ensure identical links have consistent destinations" clause into natural keyword phrasing instead of quoting the rule title.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — which matches the anchor for several specific actions with minor gaps. It stays at 4 rather than 5 because the remediation side (differentiating or fixing inconsistent links) is absent, and above 3 because more than 1-2 actions are named.

4 / 5

Completeness

Both parts are explicit: the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and the when ("Use when reviewing rendered HTML, interactive components, or design-system patterns..."). Not 5 because the 'when' is generic templated phrasing awkwardly embedding the rule title ("related to Ensure identical links have consistent destinations") rather than concrete user-trigger phrases; not 3 because both what and when are clearly stated.

4 / 5

Trigger Term Quality

Natural terms are present — "rendered HTML", "interactive components", "identical links", "consistent destinations", "screen-reader" — giving good keyword coverage. It falls short of 5 because common variations users would say ("same link text", "link purpose", "WCAG", "read more links") are missing, and above 3 because coverage goes beyond just 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The opening "reviewing rendered HTML, interactive components, or design-system patterns" is broad and would read identically across many sibling accessibility rules; only the embedded rule name distinguishes it. This matches 'somewhat specific but could still overlap with similar skills' — the boilerplate review framing creates real conflict risk with sibling frontendchecklist skills, keeping it below 4.

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/identical-links-same-purpose/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.