CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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/redirect-chains/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 good progressive disclosure pointing to a real reference file, but the body is held back by a duplicated Check/Code Review section, an explanatory section that restates known SEO concepts, and a missing verification step in a batch link-updating workflow.

Suggestions

Collapse the near-duplicate 'Check' and 'Code Review' sections into a single step, or differentiate them clearly (e.g., one for detection, one for code-review framing), to remove redundancy.

Trim the 'Explain' section's restatement of PageRank/crawl-budget basics, or move the rationale into references/rule.md, keeping the body focused on action.

Add an explicit verification step to the workflow (e.g., 'Re-crawl to confirm no internal links still resolve to a 301/302') so the batch update has a validation checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but the 'Check' and 'Code Review' sections are near-duplicates of each other, and the 'Explain' section restates SEO concepts (PageRank dilution, crawl budget) Claude largely already knows — clear tightening opportunities that keep it below a 3.

2 / 3

Actionability

Guidance is concrete and specific ('follow the URL and check the HTTP response code', 'flag 301 or 302', 'update the href attribute to the final destination URL'), but the body contains no executable commands or tooling (curl/Screaming Frog steps live only in the reference), so it is incomplete for direct execution.

2 / 3

Workflow Clarity

A clear Check → Fix sequence is present, but this is a batch operation (crawling and updating all internal links) with no verification checkpoint such as a re-crawl to confirm no links still point to redirects; the rubric caps such batch workflows at 2.

2 / 3

Progressive Disclosure

The body is a well-organized overview split into clear sections and ends with a clearly signaled, one-level-deep pointer ('see references/rule.md'); the referenced file exists and holds the detailed content, matching the anchor for appropriate splitting and easy 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 strong: it has an explicit 'Use when' trigger, natural keywords, and a distinct niche. Its only weakness is that it names a single action (auditing) rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

It names the domain ('auditing internal link structure') and one concrete action (auditing), but lists only a single action rather than multiple specific concrete actions, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It opens with an explicit 'Use when ...' trigger clause and states the action ('auditing internal link structure'), clearly answering both what it does and when to use it.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered: 'URL migration', 'domain change', 'site rebuild', 'redirects', and 'internal link structure' are phrases a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The trigger is a narrow SEO niche (post-migration redirect-chain auditing on sites with redirects >1 month), making it unlikely to fire for unrelated skills.

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.