broken-link-checker

Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".

Quality

70%

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/broken-link-checker/SKILL.md

Quality

Content

47%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 maximally lean but is an empty redirect stub: it delegates entirely to a canonical file that is not present in the bundle or environment, so the skill delivers no executable guidance on its own. Actionability, workflow clarity, and progressive disclosure all suffer from the broken delegation.

Suggestions

Fix or inline the delegation target: either ship the canonical workflow content in this skill's body/references, or correct the relative path so ../../seo/broken-link-checker/SKILL.md actually resolves.

If delegation is intentional, add a fallback summary of the core workflow (crawl internal pages, check outbound links, report source pages) so the skill remains actionable when the canonical file is unavailable.

Add a validation checkpoint to the delegated workflow (e.g., re-checking reported 404s or confirming the URL is reachable before crawling) since batch link-checking is the kind of operation that warrants verification.

Dimension	Reasoning	Score
Conciseness	The body is two sentences with zero padding — "Read [...] completely, then follow it as the active workflow" plus a reference-resolution rule — so every token earns its place, matching the lean 5 anchor rather than the could-be-trimmed 4.	5 / 5
Actionability	The directive names a specific path and rule but the target file ../../seo/broken-link-checker/SKILL.md does not exist, and the body contains none of the actual link-checking steps or commands — "high-level hints but missing the specific steps to execute" (2), not 3 since no partially executable guidance is present.	2 / 5
Workflow Clarity	Only a single redirect directive exists; the crawl → check → report sequence is absent and there are no validation checkpoints for an inherently batch HTTP-checking operation, fitting the "many gaps; validation absent" 2 anchor rather than 1 (the directive itself is coherent).	2 / 5
Progressive Disclosure	The one reference is clearly signaled with an explicit resolution rule, but it points outside the skill bundle to a missing file and no references/scripts/assets directories exist, leaving the content effectively unreachable — the buried/unreachable reference of the 2 anchor rather than the improvable-but-organized structure of 3.	2 / 5
	Total	11 / 20 Passed

Description

92%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 is excellent: concrete third-person capabilities, an explicit trigger clause with four natural user phrases, and a well-defined niche. Its only weakness is modest synonym coverage (e.g., "dead links") in the trigger terms.

Suggestions

Add common synonyms such as "dead links", "link rot", or "check my site for 404s" to the trigger clause to push trigger-term coverage from good to comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, third-person actions — "Scans a website to find broken links (404s, 500s)", "Crawls internal pages", "identifies broken outbound links", "reports source pages" — with comprehensive coverage matching the top anchor; the 4 anchor implies coverage gaps that aren't present.	5 / 5
Completeness	Explicitly answers both what (crawl, identify broken links, report source pages) and when ("Use this when the user asks to 'check for broken links', 'find 404s'...") with concrete trigger phrases — an exact match to the 5 anchor.	5 / 5
Trigger Term Quality	Four natural user phrases ("check for broken links", "find 404s", "audit my links", "is my site healthy") give good coverage, but common synonyms like "dead links" or "link rot" are missing, so it doesn't reach the comprehensive-synonyms bar of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Clear niche (website link health / 404 auditing) with distinct quoted triggers that users would not say when needing other skills, matching the minimal-conflict-risk anchor; not 4 since no meaningful overlap with closely related skills is apparent.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: nowork-studio/notfair-plugin
Path: skills/broken-link-checker/SKILL.md
Commit: 5094263

Reviewed: 5 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.