dead-end-pages

Use when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce link-free content pages.

Quality

78%

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/dead-end-pages/SKILL.md

Quality

Content

67%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 a clear fix workflow and a properly signaled one-level reference, but it spends tokens restating crawler/link concepts Claude already knows and duplicates some content found in references/rule.md.

Suggestions

Remove or shrink the 'Explain' section and the introductory crawler paragraph — Claude already knows how crawlers and internal links work; keep only the dead-end-specific guidance.

De-duplicate the body's 'Code Review' section against references/rule.md 'What to Check' so the detection criteria live in one place and the body stays a lean overview.

Tighten 'Quick Reference' so it does not repeat the Check/Fix steps verbatim; reference those sections instead.

Dimension	Reasoning	Score
Conciseness	The intro and 'Explain' section restate concepts Claude already knows ('Googlebot follows links to discover and re-crawl pages', 'Internal links are the edges of your site's graph', 'Crawlers navigate by following links'), and Quick Reference overlaps Check/Fix, so it is mostly efficient but padded.	3 / 5
Actionability	Concrete criteria are given ('count `<a href>` links pointing to other pages on the same domain', 'exclude navigation/header/footer', 'Flag any page with zero or fewer than two unique internal links in `<main>` or `<article>`') plus a 6-step Fix; no executable code in the body, but the instruction guidance is actionable with only minor gaps.	4 / 5
Workflow Clarity	The Fix section is a clear 6-step sequence with a validation checkpoint ('Re-crawl after changes to verify the links appear in the rendered DOM'), matching 'clear sequence with most checkpoints present' rather than the full feedback-loop anchor.	4 / 5
Progressive Disclosure	The body is an organized overview pointing one level deep to the verified `references/rule.md` for full details, but the body's 'Explain' and 'Code Review' sections partly duplicate the reference's 'Why It Matters' and 'What to Check', a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

88%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 strong: third-person voice, explicit 'Use when' trigger, and three concrete, domain-specific actions. It loses only on a few missing synonyms and minor overlap with related SEO internal-link skills.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('auditing a site's internal link graph for dead-end pages', 'suggesting related-content links to add to thin or standalone pages', 'reviewing CMS templates that produce link-free content pages') with comprehensive coverage of the niche, matching the 'multiple specific concrete actions' anchor.	5 / 5
Completeness	An explicit 'Use when' clause supplies concrete triggers and the three verbs clearly state what the skill does, satisfying both 'what' and 'when' with concrete phrases.	5 / 5
Trigger Term Quality	Natural terms like 'dead-end pages', 'thin or standalone pages', 'CMS templates', and 'link-free content pages' are present, but common synonyms a user might say ('orphan pages', 'internal linking', 'no outgoing links') are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	'dead-end pages' carves a clear SEO niche with distinct triggers, but there is minor overlap risk with sibling internal-link SEO rules, keeping it just below the minimal-conflict anchor.	4 / 5
	Total	18 / 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/dead-end-pages/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.