CtrlK
BlogDocsLog inGet started
Tessl Logo

sitemap-4xx

Use when applies to any site with a dynamically generated or manually maintained XML sitemap. Use when investigating crawl errors or after a site migration that removed pages.

55

Quality

62%

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/sitemap-4xx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, actionable overview with a real one-level reference file and clear verification guidance. Its main weaknesses are duplicated rationale across sections and a missing explicit fetch/verify command plus a re-verification feedback loop.

Suggestions

Collapse the intro, 'Why It Matters', and 'Why 4XX URLs Are Harmful' into a single concise rationale section to remove redundancy.

Add an executable check command (e.g., a curl/grep or small script that fetches sitemap URLs and reports non-200 status codes) so the 'Check' step is copy-paste ready.

Convert the reference pointer to a markdown link (e.g., 'see [references/rule.md](references/rule.md)') and add a brief 'verify the fix' step after resubmitting the sitemap.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-sectioned, but repeats the 'why it matters' rationale (the intro, 'Why It Matters', and 'Why 4XX URLs Are Harmful' cover the same crawl-budget/trust/Search-Console points) and explains background a competent Claude already knows, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 4 because the duplication is non-trivial.

3 / 5

Actionability

Provides concrete, runnable guidance — a status-code action table, a redirect/removal fix sequence, and an executable db query example — with only minor gaps (no exact command to fetch/test sitemap URLs); fits 'Mostly executable guidance; concrete code or commands with minor gaps' rather than 5 because the core 'check' step lacks a copy-paste fetch+status command.

4 / 5

Workflow Clarity

The migration steps are clearly sequenced and the Verification section supplies both automated and manual checkpoints; this is not a destructive/batch operation requiring a validate-fix-retry loop, so the cap does not apply, fitting 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because there is no explicit re-verify-after-fix feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with a clearly signaled one-level-deep pointer ('see references/rule.md') and the referenced file exists, matching 'Good structure; most content is appropriately placed; references mostly clear'; not 5 because the pointer is plain text rather than a markdown link and the body duplicates a chunk of the reference's explanatory content.

4 / 5

Total

15

/

20

Passed

Description

57%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 provides strong, explicit trigger guidance ('Use when...') tied to concrete SEO scenarios, but it states scope rather than concrete capabilities and omits common keyword synonyms like '404' and 'Search Console'. It is distinctive within the SEO skill family with minor overlap risk.

Suggestions

Lead with a concrete action verb (e.g., 'Identifies and reports 4XX URLs in a sitemap') instead of only stating which sites the skill applies to.

Add common user synonyms and extensions such as '404', '410', 'broken URLs', and 'Google Search Console' to improve trigger-term coverage.

Make the 'what' explicit alongside the 'when' so both halves of the trigger are stated, e.g. 'Identifies 4XX URLs in a sitemap and flags them for removal or redirect.'

DimensionReasoningScore

Specificity

Names the domain (sitemap with 4XX URLs) but lists no concrete actions Claude should take — 'applies to any site with a dynamically generated or manually maintained XML sitemap' describes scope, not capabilities, matching the 'Names the domain but actions are minimal or generic' anchor; below 3 because there are zero concrete actions.

2 / 5

Completeness

The 'when' is explicit and concrete ('Use when investigating crawl errors or after a site migration that removed pages'), and the implied 'what' is identifying 4XX URLs in sitemaps, though the 'what' leans on domain phrasing rather than a stated action; fits 'Has both what and when; when could be more explicit or specific' but the what is implicit, so it does not reach 5.

4 / 5

Trigger Term Quality

Includes natural phrases like 'crawl errors', 'site migration', 'sitemap', and '4XX' that users would say, but lacks common synonyms/extensions (e.g. '404', 'Search Console', 'broken URLs'), fitting the 'Some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The trigger is fairly niche (4XX pages in XML sitemaps after migration/crawl-error investigation), with only minor overlap risk against other SEO/sitemap skills; fits 'Mostly distinct; minor overlap risk with closely related skills' rather than 5 because it could overlap with a broader sitemap-coverage skill.

4 / 5

Total

13

/

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.

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.