CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

73%

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/nofollow-internal/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 skill is well-structured with a clear overview and a properly signaled, real one-level-deep reference, scoring well on progressive disclosure. It is held back by some redundant conceptual explanation, abstract (non-executable) detection steps, and a missing post-fix verification step for a batch operation.

Suggestions

Add an explicit verification checkpoint after the Fix step (e.g. re-scan internal links and confirm none still carry rel=nofollow before reporting done).

Replace the abstract "Scan all internal links" / "Query all <a href> elements" guidance with a concrete selector or runnable snippet (e.g. a Document.querySelectorAll('a[rel~="nofollow"]') query) so the audit step is copy-paste ready.

Tighten the Explain section to remove PageRank-sculpting background Claude already knows, or move it into references/rule.md to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the "Explain" section reiterates PageRank-sculpting concepts Claude largely already knows and overlaps with the Quick Reference, and "Code Review" partly restates "Check" — efficient but could be tightened.

2 / 3

Actionability

The fixes are concrete (add <meta name='robots' content='noindex'>, use robots.txt Disallow), but the detection steps are abstract ("Scan all internal links", "Query all <a href='...'> elements") with no executable selector or script, and runnable code is deferred to references rather than included.

2 / 3

Workflow Clarity

A Check → Fix sequence is present, but this batch audit-and-modify operation has no explicit verification checkpoint after remediation (e.g. re-scan to confirm nofollow removed), which caps the score per the destructive/batch guideline.

2 / 3

Progressive Disclosure

The body is a concise overview organized into labeled sections and signals a single one-level-deep reference ("see `references/rule.md`"), which exists and holds the detailed implementation — clean navigation.

3 / 3

Total

9

/

12

Passed

Description

90%

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 is well-constructed: it pairs an explicit Use-when trigger with a clearly scoped niche (internal rel=nofollow), giving strong completeness, trigger-term, and distinctiveness scores. Its only weakness is that the verbs (auditing, reviewing) are somewhat abstract rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

Phrases like "auditing internal link structure" and "reviewing link attributes" name the domain (internal links, rel=nofollow, same domain) but use high-level verbs rather than the multiple concrete, specific actions the top anchor calls for (e.g. "Extract... fill... merge").

2 / 3

Completeness

It has an explicit "Use when..." trigger (when) and states what it applies to ("auditing internal link structure or reviewing link attributes" for sites "using rel=nofollow on links pointing to pages within the same domain"), covering both what and when.

3 / 3

Trigger Term Quality

It surfaces natural terms a user would say — "internal link structure", "link attributes", "rel=nofollow", "links pointing to pages within the same domain" — giving good coverage of the relevant phrasings.

3 / 3

Distinctiveness Conflict Risk

The rel=nofollow-on-internal-links framing is a narrow SEO niche with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

11

/

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.