CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-sitemap

Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, information-dense skill body that provides executable commands, concrete thresholds, and ready-to-use XML templates. Its main gaps are the absence of an explicit validation step after sitemap generation and reliance on out-of-bundle script/template paths that cannot be verified from this skill alone.

Suggestions

Add an explicit validation step to Mode 2's process (e.g., run the generated XML through a parser or the discovery script and re-check per-file URL/size limits before delivering output), creating a feedback loop for the batch generation workflow.

Move the extension sitemap (image/video/news) tag-by-tag rules and the safe/penalty programmatic-page lists into a reference file (e.g., references/extension-sitemaps.md) to keep SKILL.md a lean overview with well-signaled one-level-deep references.

Clarify out-of-bundle paths: either bundle the industry templates referenced by ../seo-plan/assets/ and the sitemap_discovery.py script within this skill, or state clearly that they belong to the parent claude-seo plugin so the dependency is discoverable.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics — thresholds ("≤50,000 URLs AND ≤50MB"), a severity/fix table, and deprecated-tag details — with no padding explaining what sitemaps are. The Mode 1 prose describing the discovery helper's behavior could be tightened, matching anchor 4 (efficient, minor over-explanation) rather than anchor 5 (every token earns its place).

4 / 5

Actionability

Includes an executable discovery command, complete XML templates for both standard and index sitemaps, and per-subtype tag requirements with exact caps. Anchor 5 is missed because Mode 2's generation process remains high-level ("Ask for business type", "Load industry template from ../seo-plan/assets/") with no executable commands and a template path that is not part of this skill's bundle.

4 / 5

Workflow Clarity

Both modes are clearly sequenced, Mode 2 includes explicit quality-gate checkpoints (⚠️ at 30+ location pages, 🛑 HARD STOP at 50+), and the Error Handling section gives recovery guidance for unreachable URLs and rate limiting. It falls short of anchor 5 because Mode 2 lacks an explicit validate-the-generated-XML feedback loop (step 5 says "Generate valid XML output" but no verification step follows).

4 / 5

Progressive Disclosure

The single file is well-sectioned (Modes, checks, templates, error handling) with clearly named paths. It sits at anchor 4 rather than 5 because ~140 lines of inline content (extension sitemap subtype rules, safe/penalty page lists) could be split into reference files, and the referenced paths (scripts/claude-seo, ../seo-plan/assets/) do not exist within this skill's bundle.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description: it pairs concrete third-person capabilities with an explicit, well-quoted trigger clause. The only improvements are adding a few missing natural trigger variants and slightly more specific action coverage.

DimensionReasoningScore

Specificity

The description lists several concrete third-person actions ("Analyze existing XML sitemaps or generate new ones with industry templates", "Validates format, URLs, and structure") with minor coverage gaps — e.g., it omits outputs like validation reports or split sitemap indexes. It sits between anchor 4 (several specific actions, minor gaps) and anchor 5 (comprehensive), closer to 4 because the actions remain slightly high-level.

4 / 5

Completeness

It explicitly answers both what ("Analyze existing XML sitemaps or generate new ones... Validates format, URLs, and structure") and when ("Use when user says 'sitemap', 'generate sitemap', 'sitemap issues', or 'XML sitemap'") with concrete trigger phrases. This matches anchor 5; anchor 4's example has a less explicit 'when' clause, which this description exceeds.

5 / 5

Trigger Term Quality

Quoted triggers "sitemap", "generate sitemap", "sitemap issues", "XML sitemap" are natural phrases a user would say and cover the core domain. A few natural terms are missing ("submit sitemap", "robots.txt", ".xml" file extension), matching anchor 4 rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"XML sitemap" is a clear niche with distinct, domain-specific trigger phrases; risk of firing for the wrong skill is minimal. It matches anchor 5; anchor 4 would imply overlap with closely related skills, which is not the case here.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-seo
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.