CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nofollow-internal

Use when auditing internal link structure or reviewing link attributes. Applies to any site using rel=nofollow on links pointing to pages within the same domain.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/nofollow-internal/SKILL.md
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 a lean, well-structured overview with genuinely actionable check/fix guidance and exemplary use of a one-level reference file. Its weaknesses are triple-stating the same PageRank rationale (which Claude already knows) and omitting any post-fix verification step for what is a batch link modification.

Suggestions

Collapse the redundant PageRank explanation — the intro sentence, the Quick Reference bullet, and the Explain section all restate the same fact; keep one and cut the rest.

Add an explicit verification step after Fix (e.g. "re-run the scan and confirm zero internal nofollow links remain"), which would lift workflow clarity past the batch-operation cap of 3.

Surface the reference file's Verification section in the body, or link to it, so the validation loop isn't only discoverable in references/rule.md.

DimensionReasoningScore

Conciseness

The core fact (internal nofollow blocks PageRank; sculpting is obsolete) is stated three times — in the intro sentence ("prevents PageRank from flowing... providing no benefit"), the Quick Reference bullet ("once used for 'PageRank sculpting' but is no longer effective"), and the Explain section ("blocks PageRank from flowing... PageRank sculpting via nofollow does not work"). Mostly efficient but the redundant Explain section could be trimmed; not 4 given this triple repetition of a concept Claude already knows.

3 / 5

Actionability

Concrete directive guidance throughout: exact detection criteria ("rel='nofollow' or rel containing 'nofollow'", "same domain"), a specified output format ("source page, anchor text, and target URL"), and specific fixes ("<meta name='robots' content='noindex'>", "robots.txt Disallow"). Minor gap: no executable audit command/snippet in the body itself (those live in the reference file), so not 5.

4 / 5

Workflow Clarity

Check → Fix → Code Review sections give a recognizable sequence, but there is no validation checkpoint after the fix, and removing nofollow across a site's links is a batch edit — the rubric's batch-operation cap holds this at 3 (the reference file's Verification section is not surfaced in the body). Not 4: no re-scan/confirm step exists.

3 / 5

Progressive Disclosure

The 45-line body is a well-organized overview with clear sections, and it points to a single one-level-deep reference that exists and delivers exactly what is promised ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). Clearly signaled, easy navigation, nothing inlined that belongs elsewhere.

5 / 5

Total

15

/

20

Passed

Description

61%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 has a clear, explicit trigger clause and good natural keywords for the internal-link/nofollow niche, but it never states what the skill actually does — both sentences describe when it applies rather than the concrete action performed. Adding a leading capability statement would lift completeness and specificity.

Suggestions

Lead with a concrete action statement, e.g. "Flags internal links carrying rel=nofollow and recommends removal or noindex/robots.txt alternatives" — this fixes the missing 'what' that caps completeness at 3.

Add natural trigger synonyms users would say, such as "link audit" or "PageRank flow", to broaden trigger-term coverage.

Clarify the distinction from adjacent link-attribute topics (e.g. external/sponsored nofollow) to reduce overlap risk with sibling SEO skills.

DimensionReasoningScore

Specificity

Names the domain and two actions ("auditing internal link structure", "reviewing link attributes") but the actions are generic — it never states that the skill flags or reports internal nofollow links. Anchor 3 fits: 1-2 concrete actions, not comprehensive; not 4 because no list of specific actions is given.

3 / 5

Completeness

The 'when' is explicit ("Use when auditing internal link structure or reviewing link attributes") but the 'what' is only implied — "Applies to any site using rel=nofollow..." is an applicability condition, not a description of what the skill does. Falls between anchor 3 (clear what, weak when) and anchor 4 (both present); the unstated action keeps it at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "auditing internal link structure", "link attributes", "rel=nofollow", "links pointing to pages within the same domain". Missing a few natural variations a user might say ("link audit", "PageRank", "link sculpting"), so not 5; coverage is clearly better than the 'some relevant keywords' of 3.

4 / 5

Distinctiveness Conflict Risk

"rel=nofollow on links pointing to pages within the same domain" carves a clear niche in SEO link auditing with distinct triggers. Minor overlap risk with adjacent skills (external link audits, robots/noindex rules), so not 5.

4 / 5

Total

14

/

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