CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

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

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 well structured with genuinely actionable audit and fix steps, and it correctly delegates implementation details to a real one-level reference file. Its weaknesses are redundancy — PageRank explained twice and a Quick Reference section that repeats other sections — and the absence of a post-fix verification step for what is a batch linking operation.

Suggestions

Remove the 'Explain' section (or fold one sentence of it into the intro): PageRank mechanics are already stated in the opening paragraph and are background knowledge Claude already has, so the section duplicates the intro and adds token cost without new instruction.

Trim the Quick Reference bullets or merge them into Check/Fix — bullets like "Internal links distribute PageRank; pages receiving few internal links rank lower" repeat the intro sentence almost verbatim.

Add a post-fix validation step to the Fix workflow, e.g., 'Re-crawl after changes and re-measure in-degree for each target page to confirm improvement,' satisfying the feedback-loop expectation for batch link additions.

DimensionReasoningScore

Conciseness

Mostly efficient — the Check, Fix, and Code Review sections are tight and instruction-focused — but PageRank is explained twice (intro: "Internal links are how PageRank flows through your site"; Explain: "PageRank, Google's foundational ranking algorithm, flows from page to page through internal links"), a concept Claude already knows, and the Quick Reference bullets partially duplicate the intro and Check content. This fits anchor 3 (mostly efficient with some unnecessary explanation) rather than 2, since the padding is confined to two short sections while the actionable core is lean.

3 / 5

Actionability

Provides concrete, specific guidance with real thresholds and examples: "Count the number of unique internal pages linking to it", "Identify pages with 0–2 incoming internal links", "List your top 10–20 most important pages", "Compute in-degree… Flag pages with in-degree < 2", and a concrete anchor-text example ('instead of "click here", use "our guide to CSS Grid"'). It is not 5 because there is no executable code or command in the body and obtaining the crawl data is left unspecified; it is above 3 because the guidance is far more complete than pseudocode-level hints.

4 / 5

Workflow Clarity

A clear Check-then-Fix sequence exists (four numbered audit steps, then seven numbered fix steps), but there is no post-fix validation checkpoint — nothing like re-crawling to confirm in-degree improved. Since adding links across many pages is a batch operation, the rubric's feedback-loop cap applies: missing validation caps this at anchor 3 (sequence present, checkpoints missing), preventing a 4.

3 / 5

Progressive Disclosure

The ~40-line body is well organized into Quick Reference / Check / Fix / Explain / Code Review sections and ends with a clearly signaled, purpose-stated, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which exists and delivers exactly what is promised (HTML code examples, audit steps, verification). This matches the anchor for a clear overview with well-signaled one-level-deep references and appropriate content split.

5 / 5

Total

15

/

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.

A strong description: it names four concrete capabilities, states them in third-person gerund form, and pairs them with an explicit, multi-scenario 'Use when…' trigger clause. The only gap is missing common synonyms (anchor text, orphan pages) that would make trigger matching even more robust.

DimensionReasoningScore

Specificity

Lists four specific concrete actions — "auditing a site's internal link structure", "identifying pages that need more incoming links", "generating contextual linking opportunities between related content", "reviewing a CMS template's internal linking patterns" — giving comprehensive coverage of the domain's capabilities. This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is above the anchor of 4, which allows minor gaps in coverage.

5 / 5

Completeness

Explicitly opens with "Use when auditing…, identifying…, generating…, or reviewing…", clearly answering both what the skill does (the four named actions) and when to use it (four concrete trigger scenarios). The 'when' is more explicit and specific than anchor 4's example (where the 'when' could be more explicit), so it fits anchor 5: both what and when clearly and explicitly stated with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "internal link structure", "incoming links", "contextual linking", "internal linking patterns" — but misses common synonyms such as "anchor text", "orphan pages", or "PageRank". Good keyword coverage with a few natural terms missing fits anchor 4; it is not 5 because synonym-level comprehensiveness is absent, and not 3 because multiple natural trigger phrases are present.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — internal linking — with distinct, natural triggers ("internal link structure", "contextual linking opportunities") that would not commonly fire for unrelated skills. Minor theoretical overlap with adjacent SEO topics (e.g., orphan pages) is not enough to drop to anchor 4, since every trigger phrase is specific to internal linking.

5 / 5

Total

19

/

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