invalid-links

Use when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use `<a href>` tags, or checking that dynamically generated links have valid href values.

Quality

75%

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/invalid-links/SKILL.md

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.

The body is well-structured and actionable with concrete before/after examples and a properly disclosed reference file. Its main weakness is redundancy — three sections largely restate the same link-validity rules.

Suggestions

Merge 'Code Review' into 'Check' — both sections enumerate the same href flag conditions and the duplicate adds tokens without new guidance.

Remove the 'Quick Reference' section or the intro paragraph; they both state that invalid <a> tags are not crawlable and block PageRank.

Add a short verification step at the end of 'Fix' instructing to re-run the check and confirm the flagged count is zero, closing the feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes redundant sections: the 'Quick Reference' bullets restate the intro, 'Explain' re-summarizes what the intro already said, and 'Code Review' substantially duplicates 'Check'. Not a 2 because there is no padding with concepts Claude already knows.	3 / 5
Actionability	Concrete flag criteria (empty href, 'javascript:', 'mailto:', missing fragments, absent href) plus before/after HTML fix examples make the guidance directly usable. Not a 5 because there is no runnable audit snippet or command for the check step.	4 / 5
Workflow Clarity	A clear Check-then-Fix sequence with per-type reporting ('Report the count per type') serves as a checkpoint. Not a 5 because there is no explicit re-audit/verification step after applying fixes.	4 / 5
Progressive Disclosure	Well-organized sections with a single clearly-signaled one-level reference ('see references/rule.md') that exists in the bundle, and the body keeps only overview-level content.	5 / 5
	Total	16 / 20 Passed

Description

78%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 well-crafted description with explicit trigger guidance and concrete domain-specific actions. Its main weakness is that the capability ('what') is expressed only through the trigger scenarios rather than stated up front.

Dimension	Reasoning	Score
Specificity	Names three concrete actions in a specific domain ('auditing a page's link elements for crawlability', 'reviewing JavaScript-heavy SPAs', 'checking that dynamically generated links have valid href values'). Not a 5 because the full task scope (fixing and reporting) isn't comprehensively covered.	4 / 5
Completeness	An explicit 'Use when' clause with three concrete trigger scenarios answers 'when' clearly, and the 'what' is conveyed through the named actions, but the capability itself is embedded in the trigger clauses rather than stated as a leading statement. Not a 3 because both what and when are present.	4 / 5
Trigger Term Quality	Contains natural phrases users would say like 'auditing', 'link elements', 'crawlability', 'JavaScript-heavy SPAs', and 'valid href'. Not a 5 because common synonyms such as 'broken links', 'anchor tags', or 'SEO' are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (link crawlability for SEO) with distinct triggers ('JavaScript-heavy SPAs where navigation may not use <a href> tags', 'valid href values') that are unlikely to fire for adjacent skills; conflict risk is minimal.	5 / 5
	Total	17 / 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/invalid-links/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.