CtrlK
BlogDocsLog inGet started
Tessl Logo

noindex-in-sitemap

Use when auditing an XML sitemap or diagnosing indexing issues. Applies to any site where noindex meta tags or X-Robots-Tag headers may be applied to URLs also listed in the sitemap.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/noindex-in-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 content is well-structured with excellent progressive disclosure, deferring implementation detail to a clearly signaled reference. It loses points on conciseness (duplicated Check/Code Review sections and conceptual re-explanation) and on workflow clarity (no explicit re-verification step after sitemap edits).

Suggestions

Merge the redundant 'Check' and 'Code Review' sections into a single detection step to remove duplicated guidance and tighten the body.

Drop or trim the 'Explain' section's re-statement of what a sitemap and noindex directive are — Claude already knows this — and keep only the non-obvious crawl-budget consequence.

Add an explicit verification/re-crawl step after 'Fix' (e.g., re-fetch the sitemap and confirm no noindexed URLs remain) to close the validation loop for these batch sitemap edits.

DimensionReasoningScore

Conciseness

The body is mostly efficient with clear sections, but the 'Check' and 'Code Review' sections repeat nearly identical steps and the 'Explain' section re-describes what a sitemap/noindex directive is — concepts Claude already knows — so it fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean level 3.

2 / 3

Actionability

It gives specific, concrete checks (exact '<meta name=robots content=noindex>' tag, exact 'X-Robots-Tag: noindex' header) and a clear fix decision, but the executable code/tooling is deferred to the reference rather than present as copy-paste commands, matching 'some concrete guidance but incomplete' rather than the fully-executable level 3.

2 / 3

Workflow Clarity

The Check→Fix flow is sequenced, but after a batch/destructive sitemap edit there is no explicit re-verification checkpoint in the body, so per the rubric's destructive-operation guidance workflow clarity is capped at 'steps listed but validation gaps; checkpoints missing or implicit' rather than the validation-loop level 3.

2 / 3

Progressive Disclosure

The body is a concise overview that keeps heavy detail in a single, real, one-level-deep reference clearly signaled ('see references/rule.md'), with well-organized sections, matching the 'clear overview with well-signaled one-level-deep references' anchor; it is not the level 2 case where content that should be separate is inlined.

3 / 3

Total

9

/

12

Passed

Description

90%

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 well-constructed description with an explicit 'Use when' trigger, strong natural trigger terms, and a distinctive niche. Its only weakness is specificity: the named actions ('auditing', 'diagnosing') are abstract rather than a list of concrete operations.

DimensionReasoningScore

Specificity

It names the domain ('XML sitemap', 'noindex meta tags', 'X-Robots-Tag headers') and a couple of actions ('auditing', 'diagnosing indexing issues'), but the actions are generic and it does not list multiple specific concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.

2 / 3

Completeness

It answers both 'what' (auditing/diagnosing noindex-in-sitemap conflicts on URLs listed in the sitemap) and 'when' with an explicit 'Use when auditing an XML sitemap or diagnosing indexing issues' trigger, matching the 'clearly answers both what AND when with explicit triggers' anchor; it is not the level below where 'when' is only implied.

3 / 3

Trigger Term Quality

It surfaces natural terms a user troubleshooting indexing would actually say — 'XML sitemap', 'indexing issues', 'noindex meta tags', 'X-Robots-Tag headers' — giving good coverage of the phrases that would surface this skill, fitting the level 3 anchor over the 'some relevant keywords but missing variations' level 2.

3 / 3

Distinctiveness Conflict Risk

It carves out a clear niche (noindex directives applied to sitemap-listed URLs) with distinct, specific triggers unlikely to fire for unrelated SEO skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.

3 / 3

Total

11

/

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.