CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

robots-meta-conflict

Use when applies to sites that use both robots.txt disallow rules and meta robots noindex tags. Use when investigating why deindexed pages still appear in search results.

Quality

69%

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/robots-meta-conflict/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a tight, well-structured overview: an executable check, conditional fix guidance, and a clean pointer to a real one-level-deep reference file. The only weaknesses are minor redundancy between the intro/Quick Reference and the Check/Fix sections, and the absence of an explicit verification checkpoint in the fix workflow.

Suggestions

Deduplicate the Quick Reference bullets that restate the intro and the Check/Fix content — the 'blocked in robots.txt → noindex never read' fact appears three times.

Add an explicit verification checkpoint at the end of Fix, e.g. 'After removing the Disallow rule, verify in Google Search Console's URL Inspection that the page is now crawlable and will be treated as noindex.'

Include one inline example pair (a robots.txt Disallow line next to the flagged page's meta tag) so the Check step can be executed without opening the reference file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no tutorial padding about what robots.txt is. Minor redundancy: the core fact (a page blocked by robots.txt can never have its noindex read) is restated across the intro, Quick Reference bullets 1-2, and the Check/Fix logic, and bullets 3-4 prestate Fix content. This fits 'efficient; minor instances... that could be trimmed', not level 5 where every token earns its place.

4 / 5

Actionability

The Check section is concretely executable ('Cross-reference the site's robots.txt disallow paths against pages carrying <meta name="robots" content="noindex">. Flag any page where the URL matches a Disallow rule AND has a noindex tag') and Fix gives specific conditional remediation. It falls short of level 5 because Code Review is somewhat generic ('Review metadata generation, rendered HTML, structured data, and response headers') and no inline example pair (robots.txt snippet + flagged page) or tool usage is shown.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure forms a clear sequence, and verification is directed ('describe how to verify the final page output'), so the batch-operation cap at 3 does not apply. However, verification lives in a separate descriptive section rather than an explicit checkpoint with a feedback loop (e.g., re-verify the page is crawlable after removing the Disallow rule), which keeps it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is under 50 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 file containing those details without nested references. This matches the clear-overview anchor with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

47%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 has a specific, well-differentiated domain and natural trigger phrasing, but it is missing the capability statement entirely — it tells Claude when to activate without saying what it does. The malformed opening clause ('Use when applies to sites') further degrades clarity.

Suggestions

Add an explicit capability statement before the trigger clauses, e.g. 'Detects and resolves conflicts where robots.txt Disallow rules block crawlers from reading noindex meta tags.'

Fix the malformed opening clause 'Use when applies to sites that use both...' — it needs a verb, e.g. 'Use when auditing sites that use both robots.txt Disallow rules and meta robots noindex tags.'

Add missing natural trigger terms users would say: 'Google', 'still indexed', 'remove page from Google', 'meta robots tag'.

DimensionReasoningScore

Specificity

The description names the domain precisely ('robots.txt disallow rules and meta robots noindex tags') but never states a concrete action the skill performs — 'applies to sites' and 'investigating' are not capabilities. It matches 'Names the domain but actions are minimal or generic', not level 3, which requires 1-2 concrete actions like detects, audits, or fixes.

2 / 5

Completeness

Both sentences are 'Use when...' trigger clauses; only 'when' is present without any 'what' — no capability statement exists. This is exactly anchor 2 ('only when is present without what'), not 1 (the domain is specific, not extremely vague) and not 3 (the 'what' is absent entirely, not just weakly implied). The opening clause is also grammatically malformed ('Use when applies to sites'), weakening the trigger guidance.

2 / 5

Trigger Term Quality

Good natural keyword coverage: 'robots.txt', 'Disallow', 'noindex', 'deindexed pages still appear in search results' — phrasings users would actually say. It falls short of level 5 because common synonyms are missing: 'Google', 'still indexed', 'remove from Google', 'SERP', 'meta robots tag'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (robots.txt/noindex conflict) with distinct triggers that would rarely fire the wrong skill. Minor overlap risk remains with closely related SEO skills such as a general indexability-conflicts or deindexing skill.

4 / 5

Total

12

/

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/robots-meta-conflict/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.