CtrlK
BlogDocsLog inGet started
Tessl Logo

canonical-chain

Use when auditing metadata, crawlability, structured data, or indexability related to Avoid redirect chains on canonical URLs. Verify the rendered HTML and HTTP response rather than relying only on source files.

60

Quality

70%

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

A compact, well-structured skill that practices good progressive disclosure by keeping an overview in SKILL.md and detail in references/rule.md. The body loses points for an unnecessary concept-explanation opener, a lack of executable verification commands, and an implicit (rather than explicit) re-check after the fix.

Suggestions

Add an explicit post-fix verification step (e.g., re-crawl or curl the canonical URL to confirm a 200 OK with no redirect) to turn the Check -> Fix sequence into a validate -> fix -> re-validate feedback loop.

Include one concrete verification command (e.g., a curl -I example showing the 200 status) so the guidance is copy-paste ready rather than deferred entirely to the reference.

Trim or remove the opening explanatory sentence about canonical chains confusing search engines, since Claude already knows this concept.

DimensionReasoningScore

Conciseness

The body is largely lean with short sections, but the opening sentence ('Canonical chains confuse search engines and can result in the wrong version of a page being indexed...') explains a concept Claude already knows, and the Quick Reference bullets overlap the Check section, so it could be tightened past the score-3 'every token earns its place' bar.

2 / 3

Actionability

It gives concrete directives ('Ensure the URL returns a 200 OK status', 'Update the <link rel=canonical> tag to point directly to the final, non-redirecting URL') but no executable command for how to verify (e.g., a curl/DevTools check), leaving key verification details in the reference file rather than the score-3 'copy-paste ready' anchor.

2 / 3

Workflow Clarity

The Check -> Fix -> Explain -> Code Review structure gives a clear sequence, but there is no explicit re-verification checkpoint after the fix (e.g., 're-crawl to confirm 200 OK and no redirect'), so validation remains implicit rather than the score-3 'explicit validation steps; feedback loops' anchor.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview organized into clear sections, and it points to a real one-level-deep references/rule.md (verified present, containing the code example, exceptions, and verification steps) with a clearly signaled pointer, matching the score-3 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

9

/

12

Passed

Description

82%

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 well-formed description with an explicit 'Use when' trigger, strong natural SEO keywords, and clear what/when coverage. Its main weakness is a broad, likely-templated audit prefix that risks overlap with sibling SEO skills and actions framed as audit scope rather than concrete verbs.

Suggestions

Lead with concrete verbs (e.g., 'Audit and fix redirect chains on canonical URLs') instead of framing actions as audit-scope nouns to lift specificity toward the score-3 anchor.

Narrow or differentiate the shared 'auditing metadata, crawlability, structured data, or indexability' prefix so this skill is distinguishable from sibling SEO rules that reuse the same trigger wording.

DimensionReasoningScore

Specificity

It names the SEO domain and two actions ('auditing metadata, crawlability, structured data, or indexability' and 'Verify the rendered HTML and HTTP response'), but these read as audit-scope nouns plus a single verify directive rather than a list of multiple concrete actions, so it falls short of the score-3 'lists multiple specific concrete actions' anchor.

2 / 3

Completeness

It opens with an explicit 'Use when auditing...' trigger (the when) and follows with 'Verify the rendered HTML and HTTP response rather than relying only on source files' (the what), clearly answering both with an explicit trigger clause.

3 / 3

Trigger Term Quality

Terms like 'canonical URLs', 'redirect chains', 'crawlability', 'structured data', 'indexability', 'rendered HTML', and 'HTTP response' are natural language an SEO practitioner would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The 'canonical URLs' / 'redirect chains' niche is distinctive, but the templated prefix 'Use when auditing metadata, crawlability, structured data, or indexability related to...' would be shared verbatim by sibling SEO skills, creating overlap among similar skills.

2 / 3

Total

10

/

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.