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

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/canonical-url/SKILL.md

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 uses good progressive disclosure — a lean overview pointing to a real references/rule.md — but the body itself leans on concept restatement and abstract instructions rather than concrete, executable steps with explicit validation checkpoints.

Suggestions

Remove or compress the opening concept sentence and the redundant Quick Reference bullets that restate what canonical URLs do, keeping only the actionable rules (absolute HTTPS URL, self-referencing).

Add at least one concrete inline example in the Fix section (e.g. <link rel="canonical" href="https://example.com/page" />) so the body is actionable without forcing a jump to the reference.

Tighten the Check/Code Review sections into an explicit verify-then-fix sequence with a clear validation checkpoint (e.g. confirm the tag is absolute, HTTPS, and self-referencing before reporting pass).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the opening sentence and several Quick Reference bullets ('Canonical URLs tell search engines which version of a page to index', 'Prevents duplicate content penalties') restate concepts Claude already knows and could be trimmed.	2 / 3
Actionability	Guidance like 'Verify that this page has a canonical URL tag' and 'Add or correct the canonical URL tag in the head section' is directionally useful but abstract; the executable specifics (actual tag markup, verification commands) are deferred entirely to references/rule.md.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections give a loose sequence with an implied verify step, but there are no explicit validation checkpoints and the 'Explain' section breaks the procedural flow.	2 / 3
Progressive Disclosure	The SKILL.md is a concise overview that clearly signals a one-level-deep reference ('see references/rule.md') for full details and code examples; the referenced file exists and the split is appropriate.	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.

The description is concise, uses an explicit 'Use when' trigger, and covers natural SEO terms well. Its main weakness is that the broad audit-category qualifiers create overlap risk with sibling SEO skills and it lists audit scopes rather than a comprehensive set of concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the SEO domain and a concrete action ('Verify the rendered HTML and HTTP response rather than relying only on source files'), but the rest ('auditing metadata, crawlability, structured data, or indexability') lists audit scopes rather than a comprehensive set of specific actions.	2 / 3
Completeness	It explicitly answers both what (verify rendered HTML/HTTP response for canonical URLs) and when via an explicit 'Use when auditing ...' trigger clause, satisfying the completeness bar.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'canonical URLs', 'metadata', 'crawlability', 'structured data', and 'indexability' are all phrases a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	It is tied to a specific rule ('Set canonical URLs for all pages'), but the broad audit qualifiers 'metadata, crawlability, structured data, or indexability' could overlap with other SEO checklist skills and trigger the wrong one.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/canonical-url/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.