CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

68%

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

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.

A well-organized, token-efficient overview with excellent progressive disclosure to a single real reference file. The weaknesses are in the body's actionability (no inline executable code or commands) and workflow clarity (no post-fix validation checkpoint closing the loop).

Suggestions

Add one inline executable step to the Check section (e.g., 'curl -s https://example.com/sitemap.xml | head' or an XML validation command) so the body is not wholly dependent on the reference file for execution.

Close the workflow loop in Fix: instruct Claude to re-verify after generating or updating the sitemap (fetch it, confirm it parses as valid XML and includes the important pages).

Trim the duplicated 'why sitemaps matter' statement — keep it in either the intro or the Quick Reference bullet, not both.

DimensionReasoningScore

Conciseness

The body is mostly lean with clear sections, but the intro sentence 'Search engines may not discover all your pages through links alone—a sitemap ensures every important page gets indexed' and the Quick Reference bullet 'XML sitemaps help search engines discover all your pages' explain a concept Claude already knows and duplicate each other. Not 5 because these tokens do not earn their place; not 3 because only minor trimming is needed and there is no other padding.

4 / 5

Actionability

Concrete specifics are named ('/sitemap.xml', 'Google Search Console and Bing Webmaster Tools', 'Reference sitemap in robots.txt'), but the Fix step ('Generate or update the XML sitemap... with proper priority and changefreq values') is high-level direction — every executable code example and command is deferred to references/rule.md rather than included or sampled inline. Not 4 because the body itself contains no executable code or commands; not 2 because specific tools and paths are named.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent rough sequence, and Check ('Verify that this website has a valid XML sitemap accessible at /sitemap.xml') acts as an implicit pre-checkpoint, but there is no post-fix re-validation and 'describe how to verify the final page output' defers verification rather than specifying it. Matches anchor 3: sequence present but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

A lean ~30-line overview with a clearly signaled, one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md'. The referenced file exists, holds the executable details appropriately split from the overview, and nests no further references. Matches the anchor-5 example of a clear overview with well-signaled single-level references.

5 / 5

Total

15

/

20

Passed

Description

58%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 has an explicit and reasonably specific trigger clause plus a concrete verification methodology, but the capability statement ('what') is garbled by embedding the rule title inside the 'Use when' clause, and the trigger keywords are a broad SEO bucket that both misses common natural terms and invites overlap with sibling SEO skills.

Suggestions

State the core capability directly before the trigger clause (e.g., 'Creates, validates, and submits XML sitemaps for a website') so the 'what' is explicit rather than embedded in the 'Use when' clause.

Add natural trigger synonyms users actually say: 'SEO', 'Google Search Console', 'Bing Webmaster Tools', 'robots.txt', 'get my pages indexed'.

Drop or narrow 'structured data' in the trigger list — it describes schema.org/JSON-LD concerns rather than sitemaps and invites mis-triggers against sibling SEO skills.

DimensionReasoningScore

Specificity

Names the domain ("auditing metadata, crawlability, structured data, or indexability") and one concrete action ("Verify the rendered HTML and HTTP response rather than relying only on source files"), which matches the 'domain and 1-2 concrete actions, not comprehensive' anchor. Not 2 because a genuinely concrete verification action is explicitly stated; not 4 because there is no list of several specific actions.

3 / 5

Completeness

Both elements are explicitly present: a "Use when auditing metadata, crawlability, structured data, or indexability..." trigger clause and a what conveyed via "Create and submit an XML sitemap" plus "Verify the rendered HTML and HTTP response". Not 5 because the 'what' is awkwardly embedded in the when-clause rather than stated as a concrete capability; not 3 because the 'when' is explicit and specific, not merely implied.

4 / 5

Trigger Term Quality

Includes relevant keywords such as "XML sitemap", "crawlability", and "indexability", but misses common natural phrases a user would say for this need: "SEO", "Google Search Console", "Bing Webmaster Tools", "robots.txt", or "get my pages indexed". Falls between anchors 3 and 4, closer to 3 because several common variations and synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

The sitemap topic is fairly specific, but the broad trigger bucket "metadata, crawlability, structured data, or indexability" overlaps heavily with sibling SEO audit skills — "structured data" in particular describes a different SEO concern than sitemaps, creating real mis-trigger risk. Not 4 because the overlap risk is more than minor.

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

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