CtrlK
BlogDocsLog inGet started
Tessl Logo

internal-links

Use when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or reviewing a CMS template's internal linking patterns.

64

Quality

76%

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/internal-links/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A concise, actionable overview that correctly delegates code examples and verification detail to a well-signaled one-level-deep reference file. The main gap is the absence of a validation/re-measurement step in the body's batch link-editing workflow, which the rubric caps at 3 for workflow clarity.

Suggestions

Add an explicit verification step to the Fix workflow, e.g., '8. Re-crawl and recompute in-degree after 1-2 crawl cycles to confirm the target pages gained links' - this both closes the validation gap and surfaces the loop that currently lives only in references/rule.md.

Name at least one concrete crawl mechanism or data source (e.g., a Screaming Frog export, a sitemap crawl script, or Google Search Console internal-links report) so the Check step is executable without guessing.

Trim the 'Explain' section's PageRank primer and fold Quick Reference bullets into Check to remove duplication and lift token efficiency to the anchor-5 level.

DimensionReasoningScore

Conciseness

The body is lean and instructional (numbered Check/Fix steps, concrete thresholds), but the 'Explain' section re-teaches PageRank basics ('Google's foundational ranking algorithm, flows from page to page') that Claude already knows, and Quick Reference partly restates the intro and Check sections. These are minor trimmable instances (anchor 4), not pervasive padding that would drop it to 3.

4 / 5

Actionability

Concrete, executable instruction throughout: a 4-step Check procedure, a 7-step Fix with specific quantities ('top 10-20 most important pages', '5-10 most important commercial pages', 'in-degree < 2') and a worked anchor-text example ('instead of "click here", use "our guide to CSS Grid"'), plus a concrete Code Review procedure. As an instruction-only skill, absent code is fine since full HTML examples live in references/rule.md; the gap keeping it from 5 is that no crawl tooling or command is named.

4 / 5

Workflow Clarity

The Check -> Fix -> Code Review sequence is clearly ordered, but there is no validation or verification checkpoint after the batch link-addition workflow (the 'measure in-degree again after 1-2 crawl cycles' loop exists only in references/rule.md, not the body). The rubric's cap for batch operations without validation applies, so it cannot exceed 3 despite the good sequencing.

3 / 5

Progressive Disclosure

A well-sectioned ~35-line overview with a single clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md' - a real file containing those code examples). Content is appropriately split: overview and procedure in SKILL.md, examples and verification detail in the reference, matching the anchor-5 structure.

5 / 5

Total

16

/

20

Passed

Description

80%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.

A strong description with explicit trigger guidance and multiple concrete, domain-specific actions in third person. The main improvement is separating the 'what' (capability statement) from the 'when' (trigger clause) and adding a few natural synonyms like 'orphan pages'.

Suggestions

Lead with a declarative capability statement (e.g., 'Audits internal link structure, flags under-linked and orphan pages, and generates contextual linking opportunities.') before the 'Use when...' clause so 'what' and 'when' are each explicit.

Add natural trigger synonyms users would actually say, such as 'orphan pages', 'PageRank flow', or 'interlinking', to broaden keyword coverage.

Sharpen distinctiveness from sibling SEO rules (orphan-pages, anchor-text) by scoping triggers to whole-site link-graph auditing rather than single-page link counts.

DimensionReasoningScore

Specificity

Lists four concrete, distinct actions ('auditing a site's internal link structure', 'identifying pages that need more incoming links', 'generating contextual linking opportunities', 'reviewing a CMS template's internal linking patterns') that comprehensively cover the skill's audit-to-implementation span. It fits the score-5 anchor rather than 4 because no meaningful capability of the skill is left unlisted.

5 / 5

Completeness

An explicit 'Use when...' clause with four concrete trigger scenarios is present, and the 'what' is conveyed through the gerund actions, but capability statements are fused into the when-clause rather than declared separately (the anchor-5 pattern states capabilities, then triggers). It is noticeably above anchor 4's midpoint but not a clean anchor-5 match.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('internal link structure', 'incoming links', 'contextual linking', 'internal linking patterns', 'CMS template'). Not 5 because common synonyms like 'orphan pages', 'PageRank', 'site architecture', or 'interlinking' are missing.

4 / 5

Distinctiveness Conflict Risk

A clear SEO/internal-linking niche with distinct triggers, but 'identifying pages that need more incoming links' overlaps with closely related sibling skills (orphan-pages detection, anchor-text optimization), matching the 'mostly distinct; minor overlap risk' anchor rather than 5.

4 / 5

Total

17

/

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
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.