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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplar of a lean, actionable SEO diagnostic skill: concise sections, specific remediation directives, a clear check-fix sequence with verification, and a well-signaled single reference for deeper detail.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned body with no padding and no re-explanation of concepts Claude already knows; every line carries framing or actionable value.	3 / 3
Actionability	Gives specific, executable directives — the exact `<meta name="robots" content="noindex">` tag and concrete robots.txt Disallow add/remove actions — with two clear remediation paths.	3 / 3
Workflow Clarity	Clear Check → Fix → Explain → Code Review sequence with a verification checkpoint ('confirming they are crawlable but carry noindex') for the diagnostic flow.	3 / 3
Progressive Disclosure	The body is a concise overview and clearly signals a single one-level-deep reference (`references/rule.md`, which exists) for full implementation details and examples.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 strong, natural trigger terms and a clear niche, but its 'what does this do' is only weakly implied and the opening trigger clause is grammatically broken, capping completeness and specificity at the mid level.

Suggestions

State the 'what' explicitly with concrete verbs, e.g. 'Detects pages blocked by robots.txt that also carry noindex tags, and guides remediation.'

Fix the broken trigger phrasing 'Use when applies to sites' to 'Use when a site uses both robots.txt Disallow rules and meta robots noindex tags.'

List the concrete actions the skill performs (audit, flag conflicts, recommend remediation) rather than naming only 'investigating.'

Dimension	Reasoning	Score
Specificity	Names the domain ('robots.txt disallow rules', 'meta robots noindex tags') and one action ('investigating'), but does not list multiple concrete actions such as auditing, flagging, or remediating — only investigation is named.	2 / 3
Completeness	The 'when' is explicit via two 'Use when' clauses, but the 'what' is only weakly implied through 'investigating', and the first clause is grammatically broken ('Use when applies to sites').	2 / 3
Trigger Term Quality	Includes natural SEO terms a user would actually say — 'robots.txt disallow rules', 'noindex', 'deindexed pages', and 'search results' — with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow, specific SEO scenario (robots.txt Disallow conflicting with noindex) with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/robots-meta-conflict/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.