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.

53

Quality

60%

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

72%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, appropriately concise overview that delegates details to references/rule.md, and the Check/Fix guidance is genuinely actionable with exact status codes and remediation policies. The main gap is the absence of a post-fix validation step for what is a batch operation, which caps workflow clarity.

Suggestions

Add an explicit post-fix validation step, e.g. 'After regenerating the sitemap, re-fetch all URLs to confirm every entry returns 200 before resubmitting in Search Console.'

Provide a concrete example command or snippet for fetching sitemap URLs and recording status codes (e.g., a curl loop or a small script) in the Check section or point to it in references/rule.md.

Remove the redundancy between the intro paragraph and the Quick Reference bullets so each point earns its tokens.

DimensionReasoningScore

Conciseness

The body is lean with no padded concept explanations, but the intro sentence and the Quick Reference bullet "4XX URLs in a sitemap waste crawl budget and cause Search Console errors" state the same information twice. This matches anchor 4 (efficient with minor trimmable redundancy) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, specific guidance throughout: exact status codes ("404 Not Found, 410 Gone, 403 Forbidden"), an exact remediation policy ("set up a 301 redirect to the new URL and add the new URL to the sitemap... return 410 Gone and remove the URL"), and a named verification tool ("Google Search Console → Coverage"). Minor gaps — no example command for fetching sitemap URLs — keep it at anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is present, but the workflow ends with "Regenerate and resubmit the sitemap" and includes no post-fix re-validation (e.g., re-fetching URLs to confirm 200s). Since fetching all sitemap URLs and editing the sitemap is a batch operation, the batch-operations cap limits this to anchor 3 ('sequence present but checkpoints missing or implicit').

3 / 5

Progressive Disclosure

A ~45-line overview with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single clearly signaled, one-level-deep pointer to references/rule.md (verified to exist) that keeps implementation details out of the main file. This matches anchor 5.

5 / 5

Total

16

/

20

Passed

Description

47%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 useful trigger contexts but is fundamentally incomplete: it never states what the skill does, and the opening "Use when applies to any site with..." is grammatically broken. It also misses the most natural trigger phrasing around 404s and broken sitemap URLs.

Suggestions

Add a 'what' clause stating the concrete capability, e.g. 'Audits XML sitemaps for URLs returning 4XX status codes and recommends redirects or removal.'

Fix the broken opening phrase 'Use when applies to any site with...' — use a third-person statement of capability followed by 'Use when...'.

Include natural trigger keywords users would actually say, such as '404 pages in the sitemap', 'broken sitemap URLs', or 'sitemap errors in Search Console'.

DimensionReasoningScore

Specificity

The description names the domain ("dynamically generated or manually maintained XML sitemap") but contains no concrete skill actions — there is no verb describing what the skill does, only trigger contexts. It matches anchor 2 ('names the domain but actions are minimal or generic') and falls short of anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Only the 'when' is present ("Use when investigating crawl errors or after a site migration"); the 'what' — what the skill actually does (e.g., audit sitemap URLs for 4XX status) — is entirely absent. This exactly matches anchor 2 ('only when is present without what').

2 / 5

Trigger Term Quality

Phrases like "XML sitemap", "investigating crawl errors", and "after a site migration that removed pages" are natural things a user would say. Coverage is good but misses common variations such as '404s in the sitemap' or 'broken URLs', so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The sitemap/SEO-crawl niche is mostly distinct with clear triggers, but "investigating crawl errors" is broad enough to overlap with general SEO crawl-audit or migration skills. Minor overlap risk matches anchor 4; it does not reach anchor 5's minimal-conflict bar.

4 / 5

Total

12

/

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