CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

67%

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

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured with clean progressive disclosure to a real reference file, but the body restates known concepts and lacks executable examples or a validation loop for the sitemap-generation workflow.

Suggestions

Drop or shrink the opening explanatory sentence about why sitemaps matter; assume Claude already knows this.

Add a minimal copy-pasteable sitemap.xml skeleton and a concrete generation command (or a one-liner) to make the Fix section executable.

Turn Check/Fix into an explicit validate→fix→recheck loop so the sitemap update workflow has a feedback checkpoint.

DimensionReasoningScore

Conciseness

The body is short and sectioned, but the opening sentence ("Search engines may not discover all your pages through links alone—a sitemap ensures every important page gets indexed…") restates a concept Claude already knows and could be trimmed.

2 / 3

Actionability

Concrete targets are named ("valid XML sitemap accessible at /sitemap.xml", "priority and changefreq values", "Reference sitemap in robots.txt"), but there is no executable example — no sample sitemap XML or generation command — so guidance is incomplete.

2 / 3

Workflow Clarity

Check/Fix modes are present and loosely ordered, but generating or updating a sitemap is a batch operation with no explicit validate→fix→recheck feedback loop, capping clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

The body is a concise overview with a clearly signaled, one-level-deep pointer ("see references/rule.md") to a real bundle file, matching the well-organized one-level-deep anchor.

3 / 3

Total

9

/

12

Passed

Description

77%

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 Use-when trigger and names multiple concrete actions, making it fairly strong on specificity and completeness. It is held back by single-form technical trigger terms and some overlap with adjacent SEO skills.

Suggestions

Add natural user phrasings alongside the technical terms (e.g., "when the site isn't being indexed by Google" or "can't be crawled") to broaden trigger coverage.

Lead with the sitemap-specific trigger before the generic SEO audit terms to reduce overlap with sibling SEO skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — "auditing metadata, crawlability, structured data, or indexability" and "Verify the rendered HTML and HTTP response rather than relying only on source files" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicit "Use when auditing…" clause gives the trigger (when) and "Verify the rendered HTML and HTTP response…" gives a concrete action (what), satisfying both halves.

3 / 3

Trigger Term Quality

Relevant keywords (sitemap, crawlability, indexability, structured data, metadata) appear, but each in a single technical form, missing common user phrasings like "indexed by Google" or "can't be crawled".

2 / 3

Distinctiveness Conflict Risk

Scoped to XML sitemaps, but the broad SEO trigger terms (metadata, structured data, indexability) overlap sibling SEO-audit skills, so it could still trigger for the wrong one.

2 / 3

Total

10

/

12

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.