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

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nofollow-internal/SKILL.md

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 content is well-structured with a clean overview and a properly signaled one-level reference, and the Check/Fix guidance is concrete and actionable. It loses points for an educational 'Explain' section that pads tokens and for a workflow that omits validation/verification steps for a batch link edit.

Suggestions

Tighten the 'Explain' section: drop the origin story of rel=nofollow and PageRank-sculpting history that Claude already knows, keeping only the actionable 'why it matters' point.

Add an explicit validation step after 'Fix' (e.g. re-crawl the affected pages and confirm rel=nofollow is gone and noindex/robots directives are intact) so the batch edit has a checkpoint.

Consider inlining one short executable snippet (e.g. a query that finds internal <a> with rel containing 'nofollow') in the 'Check' section so the body is copy-paste ready rather than deferring all code to the reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with clear bulleted sections, but the 'Explain' section restates what rel=nofollow does and PageRank-sculpting history that Claude largely already knows, and there is some redundancy with the Quick Reference.	3 / 5
Actionability	Concrete, specific guidance is given (scan <a href> for rel='nofollow', remove it, substitute <meta name='robots' content='noindex'> or robots.txt Disallow), though executable code is deferred to the reference rather than inlined.	4 / 5
Workflow Clarity	A rough Check -> Fix -> Code Review sequence is present, but the body lacks any explicit validation or re-crawl checkpoint; because 'Fix' is a batch edit across a site, the missing validation caps this at 3.	3 / 5
Progressive Disclosure	The body is a clear overview with well-organized sections and a single, clearly signaled one-level-deep reference to references/rule.md (a real file) for implementation details and code.	5 / 5
	Total	15 / 20 Passed

Description

82%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 an explicit 'Use when' trigger, a clear niche, and good natural keyword coverage. Its main limitation is that the named actions ('auditing', 'reviewing') are somewhat generic rather than enumerating specific operations like flag, list, or fix.

Dimension	Reasoning	Score
Specificity	Names the domain (internal links, rel=nofollow, link attributes) plus two concrete actions ('auditing internal link structure', 'reviewing link attributes'), but the verbs are generic and coverage is not comprehensive.	3 / 5
Completeness	It explicitly answers both what (auditing/reviewing link attributes for internal nofollow) and when via a concrete 'Use when auditing internal link structure or reviewing link attributes' trigger clause.	5 / 5
Trigger Term Quality	Natural phrases a user would say are present ('auditing internal link structure', 'reviewing link attributes', 'rel=nofollow', 'internal links'), with only minor synonyms (e.g. PageRank, SEO) missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear SEO niche (rel=nofollow on same-domain links) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/nofollow-internal/SKILL.md
Commit: 30756a7

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.