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.

56

Quality

63%

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

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

The body is well-structured and points cleanly to a real reference file for implementation detail, but it is held back by section duplication, conceptual padding in Explain, and the absence of any validation checkpoint for a batch URL-auditing workflow.

Suggestions

Merge the "Check" and "Code Review" sections, which repeat the same fetch-and-detect instructions, to remove redundancy.

Add an explicit validation step in the workflow (e.g. re-fetch to confirm the noindex directive before removing a URL from the sitemap, and confirm the sitemap parses as valid XML).

Trim the "Explain" section, which restates the intro and explains what a sitemap/noindex is; lean on Claude's existing knowledge of these concepts.

DimensionReasoningScore

Conciseness

The body is short and mostly tight, but the "Check" and "Code Review" sections repeat nearly identical instructions, and the "Explain" section restates the intro and explains sitemap/noindex concepts Claude already knows.

3 / 5

Actionability

Gives concrete detection signals (the exact meta tag string and X-Robots-Tag header) and a clear fix decision branch, but provides no executable commands/code in the body and omits key execution details like how to fetch or parse the sitemap XML.

3 / 5

Workflow Clarity

A rough Check-then-Fix sequence is present, but this is a batch operation over every sitemap URL with no explicit validation checkpoint (e.g. confirm the noindex directive before removing the URL), which caps the score at 3.

3 / 5

Progressive Disclosure

Clear sectioned overview with a well-signaled one-level-deep pointer to the real references/rule.md for code examples; minor gap is the duplicated Check/Code Review content that could be consolidated.

4 / 5

Total

13

/

20

Passed

Description

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

The description is well-targeted to a specific SEO niche with a clear Use-when trigger and good natural keywords. Its main weakness is that the 'what' stays at the level of auditing/diagnosing rather than naming the concrete detection and remediation actions.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions ("auditing an XML sitemap", "diagnosing indexing issues") but does not enumerate the specific operations (fetch, detect noindex, remove) that the skill performs, so coverage is not comprehensive.

3 / 5

Completeness

An explicit "Use when..." clause gives the trigger, and "auditing"/"diagnosing" convey the what, but the what could be more specific about the actual detection/removal actions.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ("XML sitemap", "indexing issues", "noindex meta tags", "X-Robots-Tag"), but misses common synonyms like sitemap.xml, crawl budget, or Google indexing.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (noindex directives conflicting with sitemap listings) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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.

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.