sitemap-coverage

Use when applies to content sites, e-commerce stores, and any site where timely indexing of new pages matters. Use when investigating why new pages take a long time to appear in search results.

Quality

72%

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-coverage/SKILL.md

Quality

Content

72%

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

The content is concise, well-structured, and uses progressive disclosure effectively with a real reference file, but the Fix guidance is abstract and the workflow lacks an explicit post-fix verification checkpoint.

Suggestions

Add a concrete, executable step in Fix, such as a sample sitemap.xml entry or a command/tool for generating the sitemap.

Add a verification checkpoint, e.g. re-run the Google Search Console Coverage report to confirm flagged pages now appear in the sitemap.

Include one short copy-paste example of a correct vs. excluded sitemap URL entry to make the rule immediately actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized into Quick Reference, Check, Fix, Explain, and Code Review sections with no padding or explanation of basic SEO concepts Claude already knows.	3 / 3
Actionability	The Check section gives precise criteria (HTTP 200, no noindex, self-referencing canonical, absent from sitemap) and names Google Search Console, but the Fix section stays abstract ("Automate sitemap generation") without executable commands or a concrete sitemap-generation method.	2 / 3
Workflow Clarity	Check, Fix, Explain, and Code Review imply a sequence, but there is no explicit verification step to confirm the sitemap gaps were resolved after fixing, so checkpoints are missing.	2 / 3
Progressive Disclosure	The body is a concise overview that signals one well-defined one-level-deep reference, references/rule.md, which exists in the bundle, with clear navigation to it.	3 / 3
	Total	10 / 12 Passed

Description

72%

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 strong trigger terms and a clear niche, but is grammatically awkward ("Use when applies to...") and omits any explicit statement of what the skill does, capping completeness and specificity.

Suggestions

Add a leading what-clause, e.g. "Audits sitemap coverage of indexable pages and flags gaps" before the Use when triggers.

Fix the broken syntax "Use when applies to content sites" to "Use for content sites" or "Use when working on content sites".

Name the concrete actions the skill performs (audit, compare URLs, flag missing pages) to lift specificity.

Dimension	Reasoning	Score
Specificity	It names domains ("content sites, e-commerce stores") and one action ("investigating why new pages take a long time to appear in search results"), but does not enumerate the concrete capabilities the skill performs, so it is not comprehensive.	2 / 3
Completeness	It includes two explicit "Use when..." trigger clauses, but never states what the skill does (the what is only implied by the skill name), so it answers when but not what.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered: "content sites", "e-commerce stores", "indexing of new pages", "search results", and "new pages take a long time to appear in search results" are phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly sitemap/indexing coverage for SEO, with triggers tied to indexing delays and search-result discovery, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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-coverage/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours 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.