CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, actionable instruction skill with a clear fix workflow, a verification checkpoint, and clean one-level progressive disclosure to a real reference file. The main weakness is redundant instruction between the Check and Code Review sections plus some concept re-explanation in Explain.

Suggestions

Merge the "Check" and "Code Review" sections — both describe parsing <main>/<article>, counting same-domain <a href>, and excluding shared nav/header/footer — to remove duplication and save tokens.

Trim the "Explain" section: it re-teaches that internal links are graph edges and how crawlers navigate, which Claude already knows; keep only any non-obvious consequence.

Consider adding one small executable snippet (e.g., a one-liner to count in-body same-domain links) to lift actionability from strong-instructional to copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the "Explain" section restates concepts Claude already knows ("Internal links are the edges of your site's graph") and the "Check" and "Code Review" sections duplicate the same parse-main/article, count-a-href, exclude-nav/header/footer instructions, so it could be tightened.

2 / 3

Actionability

Guidance is concrete and actionable — specific selectors ("<main> or <article>"), a clear threshold ("fewer than 2" links), and a worked example (CSS Grid → Flexbox/responsive design); per the scoring notes, an instruction-only skill is not penalized for lacking executable code when guidance is this specific.

3 / 3

Workflow Clarity

The "Fix" section is a clear numbered sequence (identify dead ends → find related pages → add inline links → fallback section → re-crawl) culminating in an explicit validation checkpoint ("Re-crawl after changes to verify the links appear in the rendered DOM").

3 / 3

Progressive Disclosure

The SKILL.md body is an organized overview with well-signaled one-level-deep navigation to a real file ("see `references/rule.md`", which exists), matching the clear-overview-with-one-level-references anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong, third-person description with concrete actions, explicit "Use when" triggers, and natural SEO terminology that clearly scopes a distinct niche. It does not pad or over-claim.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "auditing a site's internal link graph", "suggesting related-content links to add to thin or standalone pages", and "reviewing CMS templates that produce link-free content pages" — matching the top anchor for several specific concrete actions.

3 / 3

Completeness

It states both what the skill does (audit/suggest/review) and an explicit "Use when..." trigger clause, satisfying the anchor that requires clearly answering both what AND when.

3 / 3

Trigger Term Quality

Covers natural terms an SEO auditor would actually say — "dead-end pages", "internal link graph", "related-content links", "CMS templates", "link-free content pages" — giving good coverage rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

The dead-end-page / internal-link-graph niche is specific with distinct triggers unlikely to overlap with unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.