CtrlK
BlogDocsLog inGet started
Tessl Logo

orphan-pages

Use when auditing site architecture or investigating why specific pages have low organic traffic despite good content. Applies to any site with more than ~20 pages.

49

Quality

53%

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/orphan-pages/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is well-organized with good progressive disclosure to a single real reference file, but it carries some redundant concept explanation and lacks both in-body executable examples and an explicit verification checkpoint for the batch fix operation.

Suggestions

Remove or merge the 'Explain' section, since it restates PageRank and recrawl concepts from the intro that Claude already knows.

Add an explicit verification step after Fix (e.g. re-crawl to confirm each orphan now has an inbound link, or surface the reference's Verification section), since adding links across many pages is a batch operation.

Inline a minimal executable snippet — such as the contextual <a href> anchor link HTML — in the body so the core action is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

The body is mostly lean and well-sectioned, but the 'Explain' section repeats PageRank/recrawl concepts already stated in the intro and largely known to Claude, so it could be tightened.

2 / 3

Actionability

Guidance is concrete (identify 2-5 pages, add contextual anchor links matching the target keyword) but the body itself contains no executable code, deferring all examples to the reference file.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is present, but there is no explicit validation/re-crawl checkpoint for what is a batch link-editing operation, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

The body is a concise overview with clearly signaled, one-level-deep navigation to references/rule.md (a real file), and detailed content is appropriately split into that reference.

3 / 3

Total

9

/

12

Passed

Description

50%

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 a clear, explicit use-trigger and a reasonably specific niche, but it omits the skill's core action and leans on a single scenario rather than a list of concrete capabilities. It reads as a 'when' statement with a weak 'what'.

Suggestions

State the concrete action the skill performs, e.g. 'Identify orphan pages and add internal links to them', so the description answers 'what' as clearly as it answers 'when'.

Add natural trigger terms users would actually say, such as 'orphan pages', 'pages with no internal links', 'pages not ranking', or 'no inbound links'.

Consider listing 2-3 specific actions (detect orphans, find candidate linking pages, insert contextual anchor links) to lift specificity and distinctiveness.

DimensionReasoningScore

Specificity

The description names a domain and two activities ('auditing site architecture', 'investigating why specific pages have low organic traffic') but does not list the skill's concrete remediation actions such as adding internal links, so it is not comprehensive.

2 / 3

Completeness

The 'when' is explicit via the 'Use when...' clause, but the 'what' is weak — the description never states the skill's actual action (add internal links to orphan pages), describing only the triggering scenario.

2 / 3

Trigger Term Quality

Natural phrases like 'low organic traffic' and 'auditing site architecture' are present, but common variations a user might say such as 'orphan pages', 'no internal links', or 'pages not ranking' are missing.

2 / 3

Distinctiveness Conflict Risk

The trigger is fairly niche but could still overlap with general SEO or internal-linking skills, and the 'more than ~20 pages' scope helps only marginally.

2 / 3

Total

8

/

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.