redirect-chains

Use when auditing internal link structure after a URL migration, domain change, or site rebuild. Applies to any site that has had redirects in place for more than a month.

Quality

63%

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/redirect-chains/SKILL.md

Quality

Content

53%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 and points cleanly to a single reference file, but it suffers from duplicated Check/Code Review sections, no executable tooling, and no validation step for what is a batch crawl operation. Tightening redundancy and adding a verify step would raise the score.

Suggestions

Merge the near-duplicate 'Check' and 'Code Review' sections into one to remove redundancy and tighten token use.

Add a verification step after 'Fix' (e.g. re-crawl updated internal links and confirm they resolve directly to 200) to satisfy the batch-operation validation requirement.

Include a concrete executable command or short script for crawling links and reporting redirect chains, rather than only describing the procedure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with clear sections, but the 'Check' and 'Code Review' sections are near-duplicates and the 'Explain' section restates PageRank/crawl-budget concepts Claude already knows, so it could be tightened; not severely padded so it stays above 2.	3 / 5
Actionability	Gives concrete procedural guidance (follow each <a href>, check HTTP code, report source/linked/final URLs) but provides no executable tooling, commands, or code, leaving key implementation details missing; as an instruction-only skill this is actionable but incomplete.	3 / 5
Workflow Clarity	A rough Check -> Fix sequence is present, but this is a site-wide batch crawl with no validation/verification checkpoint (e.g. re-crawl to confirm updated links resolve to 200), which caps workflow clarity at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	The body is a well-organized overview with clearly signaled one-level-deep reference to references/rule.md (verified to exist); minor organizational redundancy between 'Check' and 'Code Review' keeps it just below the clean level 5.	4 / 5
	Total	13 / 20 Passed

Description

73%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 is well-targeted with explicit 'Use when' triggers and a distinct SEO niche, though the 'what' side is a touch thin on enumerated concrete actions. Trigger-term coverage is strong but a few natural synonyms are absent.

Dimension	Reasoning	Score
Specificity	Names the domain ('auditing internal link structure' after migrations) and one concrete action (auditing), but does not enumerate multiple specific actions, fitting the 'names domain and 1-2 concrete actions' anchor rather than the multi-action level 4.	3 / 5
Completeness	Both 'what' (auditing internal link structure) and 'when' (after URL migration, domain change, or site rebuild with redirects > 1 month) are present, with explicit trigger phrases; the 'what' is somewhat thin so it does not reach the fully concrete level 5.	4 / 5
Trigger Term Quality	Includes several natural SEO terms a user would say ('URL migration', 'domain change', 'site rebuild', 'redirects'), giving good keyword coverage; a few common synonyms (e.g. 'redirect chains', '301s') are missing so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (post-migration internal-link/redirect auditing) with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	16 / 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/redirect-chains/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.