anchor-text

Use when auditing metadata, crawlability, structured data, or indexability related to Use descriptive anchor text. Verify the rendered HTML and HTTP response rather than relying only on source files.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/anchor-text/SKILL.md

Quality

Content

65%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 well-structured with clean progressive disclosure to a real one-level-deep reference, and is mostly concise. It is weaker on actionability and workflow clarity because concrete code, verification tooling, and explicit validation checkpoints live in the reference rather than the body.

Suggestions

Move at least one inline executable snippet into the body (e.g., a one-line grep or DOM query to find generic anchor text like 'click here') so the check is actionable without opening the reference.

Add an explicit validation checkpoint in the Check or Code Review section (e.g., 'After fixing, re-render the page and confirm no generic anchor text remains') to turn the implicit verify step into a real checkpoint.

Trim or repurpose the opening explanatory sentence about what descriptive anchor text does, since Claude already knows this; lead with the actionable rule instead.

Dimension	Reasoning	Score
Conciseness	The body is lean with short bullet and one-line sections; the only trimmable part is the opening sentence explaining what descriptive anchor text does, which is a concept Claude already knows. Not a 5 because that explanatory sentence is mild over-explanation.	4 / 5
Actionability	Gives concrete examples ('click here', 'read more') and clear directives (replace generic text with descriptive phrases including relevant keywords), but the executable details — code examples and verification tooling — are deferred to references/rule.md, leaving key details out of the body. Not a 4 because the body lacks specific methods/commands for the check.	3 / 5
Workflow Clarity	A rough Check → Fix → Explain → Code Review sequence is present, and Code Review mentions 'describe how to verify the final page output', but validation checkpoints are only implicit rather than explicit. Not a 4 because there are no concrete verify-then-proceed checkpoints; not lower because it is a simple single-purpose skill.	3 / 5
Progressive Disclosure	The body is a concise overview split into clear sections and points to a single one-level-deep reference ('see references/rule.md') which exists as a real file; navigation is easy and content is appropriately split between SKILL.md and rule.md.	5 / 5
	Total	15 / 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.

The description includes an explicit trigger and concrete verification actions, but is built on a templated phrase shared across many SEO rule skills, which weakens distinctiveness and makes the 'what' read awkwardly. It is solid but not exemplary.

Suggestions

Rewrite the 'what' so it states the skill's action in the skill author's voice (e.g., 'Audits links for descriptive, keyword-rich anchor text') instead of the templated 'auditing metadata, crawlability, structured data, or indexability related to Use descriptive anchor text'.

Add a distinguishing trigger phrase that names anchor text or link text specifically so the skill does not collide with sibling SEO metadata/crawlability skills.

Tighten the 'when' clause to anchor-text-specific situations (e.g., 'Use when reviewing internal links or anchor text for SEO and accessibility') to reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('auditing metadata, crawlability, structured data, or indexability', 'Verify the rendered HTML and HTTP response') with minor coverage gaps; not a 5 because the verbs are essentially just 'auditing' and 'verify' applied to broad domains rather than many distinct concrete actions.	4 / 5
Completeness	Has an explicit 'Use when...' trigger clause and a what/how via 'Verify the rendered HTML and HTTP response rather than relying only on source files'; not a 5 because the 'what' is awkwardly stated ('related to Use descriptive anchor text') and the when could be more specific.	4 / 5
Trigger Term Quality	Good coverage of natural SEO terms a user would say ('metadata', 'crawlability', 'structured data', 'indexability', 'anchor text', 'rendered HTML', 'HTTP response'); not a 5 because some common synonyms/variations are missing.	4 / 5
Distinctiveness Conflict Risk	The trigger domains ('auditing metadata, crawlability, structured data, or indexability') read like a template shared across a family of SEO rule skills, so it could overlap with sibling skills; only the embedded rule name 'Use descriptive anchor text' differentiates, leaving overlap risk with closely related skills.	3 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/anchor-text/SKILL.md
Commit: 30756a7

Reviewed: 25 days ago

Table of Contents

Discovery Implementation Validation

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.