CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

link-in-text-block

Use when applies to hyperlinks (`<a>` elements) that appear inline within paragraphs or text blocks. Does not apply to navigation menus, button-style links, or standalone links that are visually isolated from body text. Use when reviewing CSS that removes text-decoration from inline body copy links.

Quality

73%

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/link-in-text-block/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 well-structured, actionable accessibility-review skill with clean progressive disclosure into references/rule.md. Its main weakness is redundancy: the contrast thresholds are repeated four times and the opening statistics paragraph plus the 'Quick Reference' section could be trimmed without losing operative guidance.

Suggestions

State the 3:1/4.5:1 thresholds once (in Check or Fix) and drop or compress the 'Quick Reference' section that repeats them.

Trim the opening color-blindness statistics paragraph to one sentence of 'why it matters', since the WCAG rationale already appears in 'Explain'.

Name a concrete verification tool (e.g., 'run axe DevTools or Lighthouse on the page') in the Code Review section instead of 'browser accessibility tooling'.

DimensionReasoningScore

Conciseness

The body is short (~47 lines) and well-sectioned, but includes unnecessary material: the opening color-blindness statistics paragraph explains context Claude largely already knows, and the 3:1/4.5:1 contrast thresholds are stated four times across 'Quick Reference', 'Check', 'Fix', and 'Explain'. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); it does not reach anchor 4 because the redundancy (Quick Reference duplicating Check/Fix) is more than a 'minor instance' that could be trimmed.

3 / 5

Actionability

Concrete, executable guidance: inspect '<a> elements within text-heavy containers (paragraphs, article body, list items containing prose)', check 'text-decoration: none', verify 'at least 3:1 contrast ratio against the surrounding non-link text color AND at least 4.5:1 against the background', check ':hover and :focus states'. Falls short of anchor 5 because 'calculate the contrast... using the WCAG relative luminance formula' and 'verify the fix with browser accessibility tooling' are directions rather than copy-paste-ready commands or a named tool (e.g., axe DevTools).

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review section flow gives a clear, logical sequence for a review skill, with measurable pass criteria (contrast ratios, hover/focus cues) embedded in the Check step. It matches anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5 because there is no explicit post-fix re-verification step in the workflow — verification is mentioned only obliquely in the Code Review section.

4 / 5

Progressive Disclosure

Clear overview with a well-signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`.' The pointer resolves to a real file containing the CSS examples, code is appropriately kept out of the overview, and the body's sections (Quick Reference / Check / Fix / Explain / Code Review) are easy to navigate — matching anchor 5's pattern.

5 / 5

Total

16

/

20

Passed

Description

65%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 highly targeted trigger description with excellent boundary/exclusion language and good natural keywords, weakened by a missing capability statement: it never says what the skill does when it applies. The opening clause 'Use when applies to hyperlinks...' is also grammatically malformed, slightly obscuring intent.

Suggestions

State the capability explicitly, e.g., 'Checks that inline links are distinguishable from surrounding text by more than color alone, and flags/fixes violations' before the 'Use when' clauses.

Fix the malformed opening clause: 'Use when applies to hyperlinks...' should read 'Applies to hyperlinks...' or 'Use when the task involves hyperlinks...'.

Add a few natural trigger synonyms users would actually say — 'underline', 'link color', 'link contrast', 'accessibility' — to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names its domain concretely ("hyperlinks (`<a>` elements) that appear inline within paragraphs or text blocks", "CSS that removes text-decoration") but names only one implied action ("reviewing CSS"), and never states what the skill actually does (check/flag/fix link distinguishability). This matches 'names domain and 1-2 concrete actions, but not comprehensive' better than anchor 2, whose domain naming is far more generic ('Processes PDF files'); it falls short of anchor 4, which requires several listed specific actions.

3 / 5

Completeness

The 'when' is explicit and strong (two 'Use when...' clauses plus explicit exclusions), but the 'what' is only implied: the description says what the rule 'applies to' without ever stating what the skill does (e.g., 'Checks that inline links are distinguishable by more than color'). This is the mirror image of anchor 3 ('clear what, weak when') — better than anchor 2's 'only when present without what' because the scope statements ('applies to hyperlinks... within paragraphs or text blocks') convey a partial what, but it cannot reach anchor 4, which requires both what and when explicitly.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms a user or reviewer would say: 'hyperlinks', '<a> elements', 'inline', 'paragraphs', 'text blocks', 'CSS', 'text-decoration', 'body copy links', 'navigation menus'. A few common variations are missing — 'underline', 'link color', 'contrast', 'accessibility/WCAG' — so it does not reach anchor 5's comprehensive synonym coverage, but it is clearly above anchor 3's thin coverage ('Works with PDF files').

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers and explicit boundary language: 'Does not apply to navigation menus, button-style links, or standalone links that are visually isolated from body text.' This is more distinct than anchor 4's 'minor overlap risk' example — the inclusion/exclusion criteria sharply separate it from generic link-styling or navigation accessibility skills.

5 / 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/link-in-text-block/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.