CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

canonical-url

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

Quality

74%

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-url/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, concise overview with excellent progressive disclosure — the heavy detail (code examples, framework guidance) correctly lives in references/rule.md. Its main weakness is actionability: the Check and Fix steps say what to do but not how, with no inline command or example to make the audit immediately executable.

Suggestions

Add one executable check to the Check section, e.g. `curl -s https://example.com/page | grep -i 'rel="canonical"'` or a note to inspect the DOM in devtools, so the audit step is immediately actionable rather than deferred to the reference.

Inline a minimal correct example in the Fix section (e.g. `<link rel="canonical" href="https://example.com/page" />`) so the fix target is concrete without leaving the body.

Cut the redundant concept bullets in Quick Reference (the first two duplicate the intro paragraph) and fold the useful specifics (absolute URLs, self-referencing canonicals) into Check/Fix where they guide action.

DimensionReasoningScore

Conciseness

The 45-line body is lean and directive, but the intro paragraph and the first two Quick Reference bullets ("Canonical URLs tell search engines which version of a page to index", "Prevents duplicate content penalties from URL variations") restate basics Claude already knows and duplicate each other — minor over-explanation that could be trimmed.

4 / 5

Actionability

The Check section gives a specific instruction ("Verify that this page has a canonical URL tag and that it points to the correct preferred version") but no executable method — no command for inspecting rendered HTML versus source, no example canonical tag, and no framework-level pointer inline; the concrete how is entirely deferred to references/rule.md. Anchor 3: some concrete guidance but missing key details.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, coherent sequence for a single-rule audit. Not 5 because there are minor validation gaps: no explicit post-fix verification step and no instruction for how to confirm the canonical in rendered output (the description's key behavior) inside the body's Check step.

4 / 5

Progressive Disclosure

The body is a clean overview with clearly labeled sections, and full implementation details, code examples, and framework-specific guidance are appropriately split into references/rule.md — a well-signaled, one-level-deep reference that exists in the bundle (verified), with no nested reference chains.

5 / 5

Total

16

/

20

Passed

Description

66%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 an explicit and useful "Use when..." trigger plus a genuinely distinctive behavior (verify rendered output, not just source files), but it is weakened by an awkwardly embedded rule title and trigger terms broad enough to collide with sibling SEO skills. Tightening the wording and adding canonical-specific synonyms would lift it.

Suggestions

Rewrite so the capability reads as actions rather than an embedded rule title, e.g. "Audit pages for correct canonical URL tags... Use when the user mentions canonical URLs, duplicate content, rel=canonical, or URL variants (www vs non-www, parameters, pagination)."

Narrow the trigger terms to canonical-specific phrases ("canonical URLs", "duplicate content", "rel=canonical", "canonical tag") and drop the generic "auditing metadata, structured data, indexability" list that overlaps other SEO skills.

State the 'what' as clean third-person capabilities first (e.g. "Checks rendered HTML and HTTP responses for canonical tags and flags incorrect or missing ones"), then give the 'Use when' clause.

DimensionReasoningScore

Specificity

One concrete action is stated ("Verify the rendered HTML and HTTP response rather than relying only on source files") and the domain (canonical URL auditing) is named, but the phrase "auditing metadata, crawlability, structured data, or indexability related to Set canonical URLs for all pages" inserts a rule title rather than listing several specific actions, so coverage is not comprehensive.

3 / 5

Completeness

Both are present: an explicit "Use when auditing metadata, crawlability, structured data, or indexability..." trigger and a what ("Verify the rendered HTML and HTTP response rather than relying only on source files"). Not a 5 because the 'what' is awkwardly phrased — the capability is buried in a sentence that embeds the rule title "Set canonical URLs for all pages" rather than stating clean capabilities.

4 / 5

Trigger Term Quality

Good natural keyword coverage — "auditing", "crawlability", "structured data", "indexability", "canonical URLs" — but common variations users would say such as "duplicate content", "rel=canonical", "canonical tag", or "SEO" are missing.

4 / 5

Distinctiveness Conflict Risk

"Canonical URLs" carves a recognizable SEO niche, but the trigger terms "auditing metadata", "structured data", and "indexability" are broad audit categories that would equally match other SEO skills (meta descriptions, schema/JSON-LD, robots.txt, sitemaps), creating real overlap risk.

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