CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

canonical-header

Use when auditing metadata, crawlability, structured data, or indexability related to Sync HTML canonical tags and Link headers. 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-header/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 lean, well-structured skill body with excellent progressive disclosure — a short overview that defers implementation detail to a real references/rule.md file. Its main weakness is actionability: the Check/Fix guidance states what to compare and update but gives no executable way to inspect rendered HTML or response headers, and the workflow lacks a post-fix re-verification step.

Suggestions

Add one concrete verification snippet to the Check section, e.g. `curl -sI https://example.com/page | grep -i '^link:'` alongside checking the rendered `<link rel="canonical">` in the served HTML, so Claude knows exactly how to inspect both signals.

Add a brief re-verify step after Fix (confirm tag and header now match and no other canonical signals conflict) to close the workflow's feedback loop.

Merge or clearly delimit the 'Explain' section, which currently restates the intro's risk sentence, to remove redundancy and tighten conciseness.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) and assumes Claude's competence, with no padding explaining what canonical tags are. Minor redundancy keeps it from a 5: the intro ("Conflicting canonical-url signals can lead search engines to ignore both declarations") restates the same risk as the 'Explain' section, and the Quick Reference bullets overlap the Check/Fix sections. It is well above the 3 anchor ('some unnecessary explanation') but not perfectly trimmed.

4 / 5

Actionability

Guidance is concrete at the intent level — "Compare the HTML canonical tag with the HTTP Link header to ensure they point to the exact same URL" and "Update either the HTML tag or the HTTP header" — but there are no executable commands or examples for verifying the rendered page and headers (e.g., a curl -I invocation to inspect the Link header, or how to check the rendered DOM vs source). This matches the 3 anchor ('some concrete guidance but incomplete; missing key details') rather than the 4 anchor ('concrete code or commands with minor gaps').

3 / 5

Workflow Clarity

For a simple single-purpose skill, the Check → Fix → Explain sequence is unambiguous and 'Check' itself serves as the verification step. It falls short of 5 because there is no re-check/confirmation step after 'Fix', and the 'Code Review' section is a second, differently-shaped workflow (review-mode guidance) mixed into the same flow without signaling when each applies. Well above the 3 anchor (steps listed, checkpoints missing).

4 / 5

Progressive Disclosure

The body is well under 50 lines, appropriately split, and points to a real one-level-deep reference with clear navigation: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" (the file exists in the bundle). This matches the 5 anchor: clear overview with a well-signaled, one-level-deep reference and easy navigation.

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 and a clear verification action, backed by good domain keywords. It is held back by listing only one concrete capability and by trigger terms broad enough to overlap with sibling SEO skills. The phrase 'related to Sync HTML canonical tags and Link headers' is also awkward and partially redundant with the trigger clause.

Suggestions

List the core capabilities as concrete verbs, e.g. 'Compare the rel="canonical" HTML tag with the HTTP Link canonical header, flag mismatches, and verify the rendered page and response headers' — this lifts specificity toward comprehensive coverage.

Add natural synonyms users would say, such as 'canonical URL', 'rel=canonical', and 'duplicate content', to improve trigger term coverage.

Trim the broad trigger list ('metadata, crawlability, structured data, indexability') to terms specific to canonical/URL signals to reduce overlap with other SEO skills.

DimensionReasoningScore

Specificity

The description names the domain ("auditing metadata, crawlability, structured data, or indexability") and gives one concrete action ("Verify the rendered HTML and HTTP response rather than relying only on source files"), but does not list multiple specific actions like comparing the tag and header or flagging mismatches. It matches the 'names domain and 1-2 concrete actions' anchor, not the 4 anchor ('lists several specific actions') and clearly above the 2 anchor ('actions are minimal or generic').

3 / 5

Completeness

Both parts are present: 'what' is "Verify the rendered HTML and HTTP response rather than relying only on source files" and 'when' is the explicit "Use when auditing metadata, crawlability, structured data, or indexability" clause. The 'what' is a single action rather than a fuller capability statement, and the phrasing "related to Sync HTML canonical tags and Link headers" is awkward, so it fits the 4 anchor ('both present, when could be more explicit/specific') better than the fully concrete 5 anchor.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "canonical tags", "Link headers", "rendered HTML", "HTTP response", "crawlability", "indexability", "structured data" — terms an SEO reviewer would actually say. A few common variations are missing ("canonical URL", "rel=canonical", "duplicate content"), so it falls just short of the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Sync HTML canonical tags and Link headers" is a clear niche, but the broad trigger terms "metadata", "crawlability", "structured data", and "indexability" overlap with other SEO skills (e.g., canonical URL selection, structured data rules), creating minor overlap risk — matching the 4 anchor 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict 5 anchor.

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