CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

68%

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

Quality

Content

86%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 audit-and-fix guide: concise, concrete, and correctly offloading implementation detail to a single clearly signaled reference file. Its only shortcoming is that post-fix verification guidance stays implicit rather than specifying how to confirm the rendered output (e.g., fetch the page as Googlebot or check live headers).

DimensionReasoningScore

Conciseness

Every section is lean and load-bearing: the Quick Reference conveys the one non-obvious domain fact ("crawlers never fetch it and therefore never read its `noindex` meta tag") in a single bullet, and there is no padding or explanation of concepts Claude already knows. Matches the 'Lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The Check section gives a concrete, executable audit procedure ("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 exact per-case remediation. Minor gaps: no specific verification commands (e.g., fetching the live robots.txt or inspecting rendered headers), leaving it just below fully-executable level 5.

4 / 5

Workflow Clarity

The Check → Fix → verify sequence is coherent and includes an explicit checkpoint ("Audit pages that need to be deindexed by confirming they are crawlable but carry `noindex`"). Verification of the final output is only gestured at ("describe how to verify the final page output"), so it matches 'Clear sequence with most checkpoints present; minor validation gaps' rather than level 5.

4 / 5

Progressive Disclosure

The body is a clear, sectioned overview with a well-signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists and points only to external URLs, not to further nested skill files. Matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

51%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 excellent trigger-term coverage and occupies a distinctive niche, but it answers only 'when should Claude use it' — it never states what the skill does — and its opening clause is grammatically broken ("Use when applies to sites"). Adding a concrete action statement and fixing the grammar would lift it substantially.

Suggestions

Lead with a 'what' statement describing the skill's actions, e.g., 'Detects and resolves conflicts between robots.txt Disallow rules and meta robots noindex tags by auditing which URLs are both blocked and marked noindex,' keeping the existing 'Use when' clauses as triggers.

Fix the grammatically broken opening 'Use when applies to sites that use both...' to 'Use when the site uses both robots.txt Disallow rules and meta robots noindex tags.'

Add common user phrasings as trigger synonyms, such as 'remove a page from Google', 'page still indexed despite noindex', or 'robots.txt blocked URL showing in results', to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names a concrete domain ("robots.txt disallow rules and meta robots noindex tags") but lists no actions the skill performs — both sentences are trigger clauses. This matches the anchor 'Names the domain but actions are minimal or generic' rather than level 3, which requires 1-2 concrete actions; it is well above level 1's pure abstraction.

2 / 5

Completeness

Both sentences are "Use when..." clauses, so only the 'when' is present and the 'what' is entirely missing — the anchor at level 2 explicitly covers 'only when is present without what'. It does not reach level 3 because there is no statement of what the skill does, even a weak one.

2 / 5

Trigger Term Quality

Phrases like "robots.txt disallow rules", "meta robots noindex tags", and "deindexed pages still appear in search results" are natural terms a user with this problem would say. A few common variations are missing (e.g., "remove page from Google", "robots.txt blocked", "site still indexed"), so it fits 'Good keyword coverage; a few natural terms missing' rather than the comprehensive level 5.

4 / 5

Distinctiveness Conflict Risk

The robots.txt/noindex conflict is a clear niche with distinct trigger conditions; virtually no other skill would fire on these phrases. This matches anchor 5 ('Clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

13

/

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