CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

65%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 concise, well-sectioned overview with actionable check/fix guidance and exemplary progressive disclosure to a single real reference file. Its weaknesses are internal redundancy (duplicated audit procedure and thrice-repeated rationale) and a missing post-fix verification step for what is a batch audit-and-remediation workflow.

Suggestions

Merge the near-duplicate 'Check' and 'Code Review' sections into a single audit procedure to remove redundancy.

Add an explicit verification step after 'Fix' (e.g., re-fetch the sitemap and confirm no listed URL still carries a noindex directive, and confirm sitemap entries return 200) to satisfy the validation requirement for batch operations.

State the contradictory-signals/crawl-budget rationale once (e.g., in 'Explain') instead of repeating it across the intro, Quick Reference, and Explain sections.

DimensionReasoningScore

Conciseness

The body is short, but the same content repeats: the contradictory-signals/crawl-budget rationale appears in the intro, Quick Reference, and Explain sections, and 'Check' and 'Code Review' give near-identical audit procedures ('Fetch the XML sitemap(s) and check each listed URL ... check for <meta name=\'robots\' content=\'noindex\'> ... or an X-Robots-Tag: noindex HTTP header'). This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' — more than the minor trimmable instances of score 4, but not the heavily padded profile of score 2.

3 / 5

Actionability

The guidance names the exact signals to inspect ("<meta name='robots' content='noindex'> in the <head> or an X-Robots-Tag: noindex HTTP header"), the exact success criterion ("sitemap entries returning non-200 status codes"), and a complete decision procedure for fixes ("If yes — remove the noindex directive. If no — remove the URL from the sitemap"). As an instruction-only skill this is mostly executable guidance; it falls short of score 5 because no commands or code for fetching/parsing the sitemap are provided in the body.

4 / 5

Workflow Clarity

The Check → Fix sequence is present with an explicit per-URL decision rule ('decide whether the page should be indexed ... Never leave both in place'), but there is no validation or verification step after the fix, and the workflow is a batch operation over every sitemap URL. The rubric caps workflow clarity at 3 for batch operations without validation, which takes precedence over the otherwise clear single-purpose flow.

3 / 5

Progressive Disclosure

The body is a compact overview (~30 lines) with well-organized sections and a single clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which is a real bundle file containing the deeper implementation material (code examples, decision tree, verification steps). This matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation.'

5 / 5

Total

15

/

20

Passed

Description

70%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 well-scoped, appropriately concise description with an explicit 'Use when' clause and precise domain terminology. Its main weakness is that it describes the situation the skill applies to rather than the concrete actions the skill performs, and its trigger coverage misses several natural SEO synonyms.

Suggestions

State the skill's concrete capabilities explicitly, e.g., 'Checks sitemap URLs for noindex meta tags and X-Robots-Tag headers, reports conflicting URLs, and guides their removal from the sitemap or removal of the noindex directive.'

Add natural trigger synonyms users are likely to say, such as 'SEO audit', 'crawl budget', 'deindexed pages', or 'robots meta', to improve trigger-term coverage.

Narrow the broad trigger 'diagnosing indexing issues' toward the sitemap/noindex conflict specifically to reduce overlap with adjacent indexing-related skills.

DimensionReasoningScore

Specificity

The description names a precise domain ("XML sitemap", "noindex meta tags", "X-Robots-Tag headers") but the only actions offered are the generic verbs "auditing" and "diagnosing" — it never states what the skill actually does (check sitemap URLs for noindex, report conflicts, remove them). This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is above score 2 because the domain and scope are concrete, but below score 4 because no specific capabilities are listed.

3 / 5

Completeness

The 'when' is explicit and specific ("Use when auditing an XML sitemap or diagnosing indexing issues"), and the 'what' is conveyed by the scope sentence ("noindex meta tags or X-Robots-Tag headers ... applied to URLs also listed in the sitemap"), so both are present — matching anchor 4. It falls short of score 5 because the skill's concrete capabilities are never explicitly stated as actions, and above score 3 because the 'when' clause is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present: "auditing an XML sitemap", "diagnosing indexing issues", "noindex", "X-Robots-Tag", "URLs". Common variations a user might mention are missing (e.g., "SEO", "crawl budget", "deindexed", "robots meta", "sitemap.xml"), so it fits 'Good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

The noindex-in-sitemap niche is clear with distinct triggers ("noindex meta tags", "X-Robots-Tag headers", "URLs also listed in the sitemap"), but the broad trigger "diagnosing indexing issues" overlaps with closely related SEO skills (e.g., robots-meta or indexability-conflicts rules referenced in the bundle), matching 'Mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict score 5.

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/noindex-in-sitemap/SKILL.md

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.