sitemap

Use when auditing metadata, crawlability, structured data, or indexability related to Create and submit an XML sitemap. 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/sitemap/SKILL.md

Quality

Content

65%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 overview that practices clean progressive disclosure by offloading code and framework guidance to references/rule.md. It is held back by lacking executable detail and explicit validation checkpoints in the body itself.

Suggestions

Add at least one minimal executable snippet inline (e.g. a curl/HTTP check for /sitemap.xml or a tiny sitemap XML stub) so the body is actionable without opening the reference.

Make the validation loop explicit in the Check/Fix sections: verify format → if invalid, fix → re-verify, with a concrete validator command or URL.

Trim the opening 'why sitemaps matter' sentence, which restates knowledge Claude already has, to push conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is lean with short Quick Reference bullets and brief section directives; the only mild padding is the opening 'Search engines may not discover all your pages...' background Claude already knows, keeping it just below a 5.	4 / 5
Actionability	The body gives directional guidance and a concrete target ('/sitemap.xml', 'priority and changefreq values') but no executable code or commands in the body itself—the actual examples live in references/rule.md; this is some concrete guidance but incomplete, matching a 3 rather than a 4.	3 / 5
Workflow Clarity	The Check / Fix / Explain / Code Review sections provide a recognizable sequence, but validation is only implicit ('verify that this website has a valid XML sitemap') with no explicit validate-then-retry checkpoint; not a 4 because checkpoints are missing or unstated.	3 / 5
Progressive Disclosure	The SKILL.md body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md') for full implementation details, and that reference file exists and holds the detailed content—matching the well-signaled one-level-deep anchor.	5 / 5
	Total	15 / 20 Passed

Description

75%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 clearly answers both what the skill does and when to use it, with concrete audit domains and an explicit verification directive. It is grammatically awkward from embedding the rule title mid-sentence and omits some common SEO trigger synonyms.

Suggestions

Rewrite the description in smooth third-person prose instead of embedding the rule title 'Create and submit an XML sitemap' mid-clause.

Add natural trigger synonyms users would say, e.g. 'XML sitemap', 'SEO', 'Google Search Console', or 'sitemap.xml'.

List a couple more distinct verbs (e.g. 'generate', 'submit', 'validate') to lift specificity from domain-listing toward multi-action coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'auditing metadata, crawlability, structured data, or indexability' and 'Verify the rendered HTML and HTTP response rather than relying only on source files' list several concrete audit domains plus an explicit verification action; not a 5 because the verb set is narrow (mostly 'auditing'/'verify') rather than many distinct actions.	4 / 5
Completeness	An explicit 'Use when auditing...' clause provides the 'when' and the audit domains plus verification action provide the 'what'; not a 5 because the 'when' is tied to a single rule rather than broader trigger phrasing, and the embedded rule title reads awkwardly.	4 / 5
Trigger Term Quality	Phrases 'metadata, crawlability, structured data, or indexability' plus 'sitemap', 'rendered HTML', and 'HTTP response' are natural SEO-audit terms a user would say; not a 5 because common synonyms like 'XML sitemap', 'SEO', or 'Google Search Console' are absent.	4 / 5
Distinctiveness Conflict Risk	The sitemap-indexability niche with rendered-HTML/HTTP verification is mostly distinct; not a 5 because 'metadata', 'structured data', and 'crawlability' overlap with adjacent SEO skills (robots.txt, meta-tag auditing).	4 / 5
	Total	16 / 20 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/sitemap/SKILL.md
Commit: 30756a7

Reviewed: 9 days 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.