CtrlK
BlogDocsLog inGet started
Tessl Logo

sitemap-domain

Use when applies to sites that have recently migrated from HTTP to HTTPS, changed domain name, or have www/non-www redirect configurations. Use when sitemap submission reports low coverage.

52

Quality

58%

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

Quality

Content

87%

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 lean, well-structured overview that defers detail to a single verified reference, with concrete actionable Check/Fix guidance; its main gap is the absence of an explicit post-fix verification checkpoint.

Suggestions

Add an explicit verification step after Fix, e.g. re-parse the regenerated sitemap to confirm no <loc> hostname/protocol mismatches remain before resubmitting.

Include a one-line validation command or check that the resubmitted sitemap's coverage report reflects the corrected URLs.

DimensionReasoningScore

Conciseness

The body is lean and well-organized, states the rule without explaining basic SEO concepts, and defers full detail to the reference, so every token earns its place.

3 / 3

Actionability

The Check and Fix sections give concrete, copy-applicable guidance (parse all <loc> values, extract protocol and hostname, flag mismatches, require every URL to start with the canonical host, regenerate and resubmit), satisfying the instruction-only carve-out despite no inline code.

3 / 3

Workflow Clarity

The Check -> Fix -> Explain -> Code Review sequence is present, but the post-fix verification checkpoint (confirm resubmitted sitemap reports correct coverage) is only implicit in the body, so it sits at 'steps listed but validation gaps'.

2 / 3

Progressive Disclosure

The body is a concise overview with a single, clearly-signaled, one-level-deep reference to references/rule.md (verified to exist), giving easy navigation and an appropriate content split.

3 / 3

Total

11

/

12

Passed

Description

30%

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, distinctive trigger coverage and clear when-to-use guidance, but it completely omits what the skill actually does, leaving the 'what' unspecified.

Suggestions

Lead with a concrete capability statement naming the actions the skill performs, e.g. "Audit sitemap URLs for cross-domain or protocol/hostname mismatches and guide fixes."

Add natural user-facing phrasings like "fix my sitemap" or "sitemap not being crawled" alongside the technical triggers.

Keep the existing 'Use when' clauses but pair them with an explicit one-line 'what' so both what and when are stated.

DimensionReasoningScore

Specificity

The description states only trigger conditions ("migrated from HTTP to HTTPS, changed domain name... www/non-www redirect configurations") with no concrete action verbs describing what the skill does, so it never reaches the 'names domain and some actions' bar of a 2.

1 / 3

Completeness

It has explicit "Use when..." triggers for the 'when', but the 'what does this do' is entirely absent rather than merely implied, which matches the 'missing what OR when' anchor.

1 / 3

Trigger Term Quality

It includes relevant natural terms (HTTP to HTTPS migration, changed domain name, www/non-www, sitemap submission) but leans on technical phrasing like "reports low coverage" and misses plainer variations a user would say, so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The triggers are narrow and SEO-sitemap-specific (HTTPS migration, domain rename, www/non-www redirect, sitemap low coverage), forming a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

7

/

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.