CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

redirect-chain

Use when auditing site redirects after URL migrations, domain changes, or CMS upgrades. Applies to any site that has had multiple rounds of structural changes over time.

Quality

72%

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/redirect-chain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured overview that correctly pushes implementation detail to a real, one-level-deep reference file, with a clear check-fix-verify workflow and explicit validation criteria. Its main weakness is redundancy: the Explain section re-teaches known concepts and the Check and Code Review sections duplicate each other, which could be merged to tighten the skill.

Suggestions

Cut or collapse the Explain section — its only non-duplicated fact (the ~5-hop Googlebot limit) already appears in Quick Reference, and the rest re-teaches what redirect chains are, which Claude already knows.

Merge the Check and Code Review sections, which describe the same audit procedure (follow hops, record chain, flag 2+ hops, verify final 200) with slightly different wording — this redundancy creates ambiguity about which procedure to follow.

Add a single inline command for following redirects (e.g., a one-line curl -I example) so the body is executable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is compact overall, but the Explain section re-teaches a concept Claude already knows ("A redirect chain occurs when page A redirects to page B, which also redirects to page C") and duplicates facts already stated in the intro and Quick Reference (the 5-hop Googlebot limit appears twice, PageRank loss three times); the Check and Code Review sections also repeat the same audit procedure. Not a 2 because the body is short and not padded like a tutorial; not a 4 because the duplication is more than a minor trim.

3 / 5

Actionability

Concrete, specific guidance throughout: a worked fix example ("if A→B→C, update A's redirect to point directly to C"), explicit report fields ("source URL, intermediate URLs, number of hops, final URL, and HTTP status at each step"), and a concrete verification criterion ("confirming a single 301 or 302 followed by a 200"). As an instruction-only skill the absence of inline code is acceptable, but the execution mechanics (commands to follow redirects, where redirect rules live) are entirely deferred to references/rule.md rather than present in the body.

4 / 5

Workflow Clarity

A clear Check → Fix → Verify sequence with explicit validation checkpoints ("Verify the chain is gone by following the URL and confirming a single 301 or 302 followed by a 200"; "Verify that the final destination returns 200"), plus loop detection ("Check for redirect loops (A→B→A)"). Not a 5 because there is no error-recovery feedback loop (what to do if verification fails) and the overlapping Check/Code Review sections blur which procedure to follow; the batch-operation cap does not apply since verification steps are present.

4 / 5

Progressive Disclosure

A ~35-line overview body with well-organized sections and a clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — the file exists (151 lines with curl examples and framework guidance) and contains no further nested references.

5 / 5

Total

16

/

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 strong, explicit trigger clause with several natural search terms, but it is entirely when-oriented: the capability side (what the skill actually does — detect and flatten redirect chains) is only weakly implied by the embedded gerund. Adding a standalone what-statement with the term "redirect chain" would make it fully complete.

Suggestions

Prepend a standalone what-statement before the Use-when clause, e.g., "Detects and flattens multi-hop redirect chains, reporting hop count and HTTP status at each step. Use when auditing site redirects..." — this would raise completeness and specificity.

Include the term "redirect chain" (and "301 redirects") in the description — these are the most natural phrases a user would say for this exact task and are currently missing.

Name the concrete outputs of the audit (full chain A→B→C, hop count, HTTP status per step) so the skill's capabilities are explicit rather than implied by "auditing".

DimensionReasoningScore

Specificity

"auditing site redirects" is the one concrete action explicitly stated, which names the domain clearly but is not comprehensive — chain detection, hop counting, and chain flattening are never mentioned. Not a 2 because the action is concrete rather than generic, not a 4 because only a single action verb is present instead of several specific actions.

3 / 5

Completeness

The "when" is explicit and specific ("Use when auditing site redirects after URL migrations, domain changes, or CMS upgrades"), but the "what" exists only as the gerund embedded in the when-clause — there is no standalone statement of what the skill does (e.g., identify chains, report hops, flatten redirects). Not a 2 because a discernible what ("auditing site redirects") accompanies the explicit when; not a 4 because the what is not independently and clearly stated.

3 / 5

Trigger Term Quality

Natural trigger terms are present: "site redirects", "URL migrations", "domain changes", "CMS upgrades" — phrases users would plausibly say. Not a 5 because the most natural terms for this exact task — "redirect chain", "301 redirects", "redirect loops" — are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — post-migration redirect auditing — with distinct triggers (URL migrations, domain changes, CMS upgrades). Not a 5 because "site redirects" and "CMS upgrades" could overlap with broader site-migration or general SEO-audit skills.

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/redirect-chain/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.