CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly lean accessibility review skill with a clear check→fix workflow and excellent progressive disclosure via a verified one-level reference. The main weaknesses are mild introductory prose redundancy and the absence of an inline executable code example in the body itself.

Suggestions

Trim the opening prose paragraph and the overlap between Quick Reference and Explain to reduce token redundancy.

Add a small inline CSS snippet in the Fix section (e.g., the underline approach) so the body is copy-paste ready without opening the reference.

Tighten the Code Review section with concrete element/state targets instead of generic phrasing like 'Flag exact elements, roles, labels'.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence, but the opening prose ('universal, color-independent signal understood across cultures') and redundancy between Quick Reference and the Explain section could be tightened; not padded with basics, so above a 1.

2 / 3

Actionability

Provides concrete, specific guidance — exact 3:1/4.5:1 thresholds, named CSS properties, and WCAG technique G183 — but the body itself lacks an inline executable code example and the Code Review section is somewhat generic; just short of fully copy-paste-ready.

2 / 3

Workflow Clarity

The Check section sequences a clear find → inspect CSS → verify contrast → check hover/focus flow with an explicit verification checkpoint (contrast-ratio validation), which suits this single-purpose review skill.

3 / 3

Progressive Disclosure

A well-organized overview body with a clearly signaled, verified one-level-deep reference ('see references/rule.md') that holds the detailed code examples, matching the clear-overview anchor.

3 / 3

Total

10

/

12

Passed

Description

100%

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 precise, well-scoped description with explicit trigger guidance and strong negative boundary-setting that minimizes conflict risk. It is written in correct third-person voice and names concrete actions and natural trigger terms. The leading 'Use when applies to' phrasing is slightly awkward grammatically but does not undermine the strong what/when clarity.

DimensionReasoningScore

Specificity

Names multiple concrete actions — identifying inline `<a>` elements within text blocks and reviewing CSS that removes `text-decoration` from inline body copy links — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (inline link distinguishability within text blocks) and 'when' via two 'Use when...' clauses, satisfying the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Covers natural terms users would say — 'hyperlinks', '`<a>` elements', 'links', 'CSS', 'text-decoration', 'inline body copy links' — with two explicit 'Use when...' triggers.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche — inline body-copy links — with explicit negative scoping ('Does not apply to navigation menus, button-style links, or standalone links'), making conflict with other link/nav skills unlikely.

3 / 3

Total

12

/

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.