CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

broken-links

Use when auditing metadata, crawlability, structured data, or indexability related to Resolve internal broken links. 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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/broken-links/SKILL.md
SKILL.md
Quality
Evals
Security

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 a lean, well-organized overview with exemplary progressive disclosure into a real one-level reference file. Its weakness is execution detail: the Check and Fix steps are high-level directions with no concrete scan/verify procedure, and the workflow lacks an explicit post-fix validation loop in the body itself.

Suggestions

Add a concrete, executable check step, e.g. extracting internal hrefs from rendered HTML and checking each with curl's status code output, instead of the bare 'Scan the website' instruction.

Insert an explicit validation loop after Fix — re-crawl the affected routes and confirm the links no longer return 404/5xx before considering the rule satisfied — rather than deferring all verification to the reference file.

Inline the one or two most important verification commands from references/rule.md (e.g. inspecting rendered HTML and HTTP headers) so the main workflow is self-sufficient.

DimensionReasoningScore

Conciseness

The ~30-line body is tightly sectioned (Quick Reference, Check, Fix, Explain, Code Review) with almost no padding; the single motivational opener ('frustrate users and waste crawl budget...') explains a concept Claude already knows, a minor trimmable instance matching anchor 4. Not 3 because there are no padded sections beyond that one sentence.

4 / 5

Actionability

Some concrete guidance exists — specific status codes ('404 (Not Found) or 5xx (Server Error)'), 'Flag exact routes or templates', 'verify the final page output' — but the core operations are high-level hints: 'Scan the website for any internal links' and 'Update the broken link to the correct URL' give no command, tool, or procedure. This fits 'some concrete guidance but incomplete; missing key details' rather than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

A sequence is present (Quick Reference → Check → Fix → Explain → Code Review) but validation checkpoints are only implicit ('describe how to verify the final page output'), with the actual verification steps (re-crawl, Search Console check) living solely in the reference file. Because link scanning is a batch operation with no explicit validate-after-fix feedback loop in the body, workflow clarity is capped at 3 per the rubric's feedback-loops guidance.

3 / 5

Progressive Disclosure

The body is a short, well-sectioned overview with one clearly signaled, one-level-deep reference ('see references/rule.md') that exists and appropriately holds the implementation details, code example, and verification procedures. This matches the top anchor: clear overview, appropriately split content, easy navigation.

5 / 5

Total

15

/

20

Passed

Description

58%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 has an explicit trigger clause and a distinct core topic, but is dragged down by template boilerplate: the awkwardly embedded skill title, generic audit-term triggers that inflate conflict risk, and the absence of natural synonyms like '404' or 'dead links'. It answers when more clearly than what.

Suggestions

Rewrite the first sentence so the capability is stated as a verb phrase, e.g. 'Detects and fixes internal links returning 404 or 5xx errors', instead of embedding the skill title mid-sentence.

Add the natural trigger terms users would actually say — '404', 'dead links', 'link check' — and drop the boilerplate 'metadata, crawlability, structured data, or indexability' list that overlaps with sibling SEO skills.

Clarify the what by listing the concrete actions (scan internal links, verify rendered HTML/HTTP status, fix or remove dead links) rather than a single methodology note.

DimensionReasoningScore

Specificity

The description names the domain (internal broken links) and two concrete actions — 'Verify the rendered HTML and HTTP response' and auditing the listed SEO properties — matching the '1-2 concrete actions, not comprehensive' anchor. It falls short of anchor 4 because it does not list several specific actions such as scanning, fixing, or re-validating.

3 / 5

Completeness

An explicit 'Use when...' trigger clause is present, and the what is conveyed via 'Resolve internal broken links' plus the verification directive, fitting anchor 4 ('both what and when; when could be more explicit'). Not 5 because the what is muddled — the skill title is pasted mid-sentence and the second sentence describes methodology rather than capabilities.

4 / 5

Trigger Term Quality

Relevant keywords like 'broken links', 'rendered HTML', and 'HTTP response' are present, but the most natural user phrases for this task ('404', 'dead links', 'link check') are missing, and 'metadata/structured data/indexability' read as boilerplate only loosely tied to broken links. This fits 'some relevant keywords but missing common variations or synonyms' rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'internal broken links' is a distinct niche, but the leading trigger 'auditing metadata, crawlability, structured data, or indexability' is generic boilerplate shared across a family of SEO rules, creating real overlap risk with sibling metadata/crawlability skills. This is 'somewhat specific but could still overlap' (anchor 3), not anchor 4's 'minor overlap risk only'.

3 / 5

Total

13

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/broken-links/SKILL.md

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.