link-checker

Use when reviewing templates, rendered HTML, or shared components related to Check for broken links. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/link-checker/SKILL.md

Quality

Content

57%

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

The skill body is well-structured with appropriate progressive disclosure to a real reference file, but it lacks executable commands, validation feedback loops, and carries mild explanatory padding. As an instruction-style skill it is serviceable but not maximally actionable.

Suggestions

Add at least one executable command example (e.g., a lychee or linkchecker invocation) so guidance is copy-paste ready.

Insert a validation step in the Check/Fix flow (e.g., re-run the checker after fixes and confirm zero broken links).

Trim the opening SEO/credibility rationale, which restates knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	The body is short and well-organized, but the opening rationale ('hurt SEO rankings... damage credibility') and some descriptive Check/Fix lines restate knowledge Claude already has, so it could be tightened.	2 / 3
Actionability	It names concrete tools ('lychee, linkchecker, or broken-link-checker npm packages') and link types, but provides no executable commands or copy-paste examples, leaving guidance incomplete.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections give a loose sequence, but there are no validation checkpoints or feedback loops for what is effectively a batch link-scanning operation, capping clarity at 2.	2 / 3
Progressive Disclosure	The body is a concise overview with a clearly signaled, one-level-deep reference ('see references/rule.md'), and that bundle file exists, matching the top anchor.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 has an explicit 'Use when' trigger and clear domain framing, but the trigger term coverage and action specificity are incomplete, and the broad template/component scope introduces some overlap risk. Voice is correctly third person.

Suggestions

Add more concrete actions (e.g., 'scan for 404s, validate anchors, check redirects') to raise specificity.

Expand trigger terms to include natural phrases like 'dead links', '404s', and 'link checker'.

Narrow the 'reviewing templates, rendered HTML, or shared components' scope to emphasize link validation specifically.

Dimension	Reasoning	Score
Specificity	It names the domain ('templates, rendered HTML, or shared components') and a concrete action ('Validate the final browser-facing markup'), but does not enumerate multiple distinct actions, so it falls short of the top anchor.	2 / 3
Completeness	It explicitly states both what it does ('Validate the final browser-facing markup') and when to use it ('Use when reviewing templates, rendered HTML, or shared components'), satisfying the top anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural terms like 'broken links' and 'rendered HTML', but misses common variations a user might say such as '404', 'dead links', or 'link checker'.	2 / 3
Distinctiveness Conflict Risk	The broken-link niche is fairly specific, but the broad 'reviewing templates, rendered HTML, or shared components' framing could overlap with general HTML or component-review skills.	2 / 3
	Total	9 / 12 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/link-checker/SKILL.md
Commit: 48405aa

Reviewed: about 9 hours 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.