CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

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

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.

A well-structured, concise audit skill body with an excellent progressive-disclosure split to references/rule.md. The main gap is actionability: verification is described at the directive level without any executable commands for checking redirects or HTTP status, and the Check section is redundant with the Quick Reference.

Suggestions

Add concrete verification commands to the Check section, e.g. `curl -sIL <canonical-url> | grep -E 'HTTP/|location'` or equivalent, so the redirect-chain check is executable rather than directive.

Merge the redundant "## Check" section with the Quick Reference bullets, or differentiate them (bullets = rule summary, Check = how to test).

Add a post-fix validation step ("After updating the tag, confirm the new canonical URL returns 200 OK with no redirects") and fix the HTML-escaped `&lt;link rel="canonical"&gt;` in the Fix section so it renders correctly.

DimensionReasoningScore

Conciseness

The body is lean at roughly 35 lines with well-scoped sections, but the "## Check" section ("Verify that the canonical URL of the page does not result in any redirects") duplicates the Quick Reference bullets, and the opening sentence re-explains SEO crawl basics Claude already knows. Efficient with minor trimmable instances — anchor 4, not 5.

4 / 5

Actionability

Concrete directives exist ("returns a 200 OK status", "Update the `<link rel="canonical">` tag to point directly to the final, non-redirecting URL"), but no executable commands show how to verify redirects or status codes (e.g. `curl -I <url>`), and the Check section states what to do without how. Some concrete guidance but missing key execution details — anchor 3, not 4, since the body contains no commands at all.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review headings form a coherent audit workflow for a simple single-purpose skill, and no destructive/batch cap applies. However, no post-fix re-verification step is stated (e.g. re-check that the canonical now returns 200 OK), leaving a minor validation gap — anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a concise overview that delegates implementation details via a clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and references/rule.md exists with the code example, rationale, exceptions, and verification steps. Clear overview, well-signaled reference, appropriate split — matches anchor 5.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid description with an explicit "Use when" trigger, a clear niche, and concrete verification guidance. Its weaknesses are the awkwardly embedded rule title in the trigger clause and missing natural synonyms ("SEO", "canonical tag", "rel=canonical") that would improve trigger matching and distinctiveness.

Suggestions

Rewrite the trigger clause to use natural user phrasing, e.g. "Use when auditing canonical tags, rel=canonical, redirect chains, or SEO indexability issues" instead of embedding the title-cased rule name "Avoid redirect chains on canonical URLs".

Add natural synonyms and domain terms users actually say — "SEO", "canonical tag", "rel=canonical", "redirects" — to broaden trigger term coverage.

Enumerate one or two more concrete actions (e.g. "check HTTP status codes" and "trace redirect hops") to raise specificity beyond the current two generic audit verbs.

DimensionReasoningScore

Specificity

Names the domain (canonical URLs / SEO metadata) and two concrete actions — "auditing metadata, crawlability, structured data, or indexability" and "Verify the rendered HTML and HTTP response" — but the action list is not comprehensive. It sits at anchor 3 rather than 4 because it does not enumerate several distinct specific actions, and above anchor 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Both "what" ("Verify the rendered HTML and HTTP response rather than relying only on source files") and "when" ("Use when auditing...") are explicitly present, so the missing-trigger cap at 3 does not apply. It falls short of anchor 5 because the trigger clause embeds the rule title "related to Avoid redirect chains on canonical URLs" rather than natural concrete trigger phrases a user would type.

4 / 5

Trigger Term Quality

Includes natural keywords users would say in this domain: "metadata", "crawlability", "structured data", "indexability", "canonical URLs", "redirect chains", "rendered HTML", "HTTP response". Missing a few common variations and synonyms such as "SEO", "canonical tag", "rel=canonical", or plain "redirects", which keeps it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The phrase "Avoid redirect chains on canonical URLs" pins a distinct niche with minimal conflict risk, but the shared boilerplate "Use when auditing metadata, crawlability, structured data, or indexability" is common across the SEO rule family, creating minor overlap risk with closely related SEO skills. Mostly distinct — anchor 4 rather than 5.

4 / 5

Total

15

/

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