CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

indexability-conflicts

Use when auditing a site for indexability issues, investigating why pages appear in Google's index that should be excluded (or vice versa), or reviewing robots.txt and meta robots configurations for consistency.

Quality

77%

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/indexability-conflicts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, actionable skill body with a clear check/fix/verify workflow and exemplary progressive disclosure to a single, real reference file. Its main weakness is redundancy: the robots.txt-vs-noindex conflict mechanic is explained three times across the intro, Quick Reference, and Explain sections, which inflates tokens without adding guidance.

Suggestions

Consolidate the triplicated robots.txt-vs-noindex explanation: keep it once (either the intro or the Explain section) and cut the rest — the Quick Reference bullet restating "robots.txt blocks crawling; noindex blocks indexing" is redundant with both.

Add an error-recovery loop to Fix step 4: what to re-check and re-apply if Google Search Console URL Inspection still shows conflicting signals after the fix.

Either include a short runnable snippet for the Code Review audit (fetch robots.txt, match Disallow, check meta/X-Robots-Tag) inline, or make the reference pointer accurately describe what references/rule.md contains (config examples, not programmatic audit code).

DimensionReasoningScore

Conciseness

The core mechanic — robots.txt blocks crawling so noindex is never read — is explained three separate times (intro paragraph, Quick Reference bullets, and the Explain section), and the Explain section largely restates knowledge Claude already has about robots.txt vs noindex pipelines. The Check/Fix sections are efficient, so it is mostly efficient but could be tightened by consolidating the redundant explanations; it is not severely padded enough to fall to 2.

3 / 5

Actionability

The Check section names the exact four signals to collect (specific meta tag `<meta name='robots' content='noindex'>`, `X-Robots-Tag` header, canonical link, robots.txt path match) and Fix gives concrete if/else decision branches per conflict type — directly executable guidance. Not 5 because the body contains no runnable code or commands (deferred to references/rule.md, which holds config examples rather than the programmatic audit code the Code Review section describes), leaving minor gaps.

4 / 5

Workflow Clarity

There is a clear Check → Fix → Verify sequence, and step 4 of Fix is an explicit validation checkpoint ("Verify after fixing using Google Search Console URL Inspection for each affected page"), so it exceeds the implicit-checkpoint level of 3. Not 5 because there is no error-recovery feedback loop — no instruction for what to do if the URL still shows conflicting signals after the fix.

4 / 5

Progressive Disclosure

The ~40-line body is a clean, well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) with a single clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and holds the examples and detail the body defers. Content is appropriately split with easy navigation, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

75%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 solid description with explicit, concrete "Use when..." triggers naming the exact domain and artifacts (robots.txt, meta robots, Google's index). Its main weaknesses are a "what" that is folded into the trigger clauses rather than stated independently, and missing natural synonyms (noindex, canonical, X-Robots-Tag) that users would commonly say.

Suggestions

Lead with an independent capability statement (e.g., "Detects and resolves conflicting indexability signals — robots.txt blocks combined with noindex, canonicals pointing to noindex pages — and fixes them") before the "Use when..." clause, so "what" and "when" are each explicit.

Add the natural synonyms users say for this problem — "noindex", "canonical tag", "X-Robots-Tag", "deindexed" — to the trigger terms to round out keyword coverage.

Mention the fix/resolution side of the skill (not just auditing) so the description covers the full capability set the body provides.

DimensionReasoningScore

Specificity

The description lists three concrete actions — "auditing a site for indexability issues", "investigating why pages appear in Google's index that should be excluded (or vice versa)", and "reviewing robots.txt and meta robots configurations for consistency" — which matches the anchor for several specific actions with minor gaps. Not 5 because it omits the fix/resolution workflow and the canonical/X-Robots-Tag signals the skill body actually covers.

4 / 5

Completeness

Both "what" and "when" are present: the explicit "Use when auditing... investigating... or reviewing..." clause provides concrete trigger phrases, and the gerund actions state what the skill does. Not 5 because the "what" is embedded inside the when-clauses rather than stated as an independent capability statement (e.g., what output the audit produces), so it is less explicitly separated than the 5-anchor pattern.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "indexability issues", "Google's index", "robots.txt", "meta robots" are phrases a user with this problem would say. Not 5 because common synonyms and variations are missing — notably "noindex", "canonical", "X-Robots-Tag", and "deindexed".

4 / 5

Distinctiveness Conflict Risk

The niche (indexability conflicts between robots.txt, meta robots, and Google's index) is distinct with domain-specific triggers, so conflict risk is low. Not 5 because "reviewing robots.txt and meta robots configurations for consistency" could also plausibly fire for a generic robots.txt-authoring or broad SEO-audit skill.

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

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/indexability-conflicts/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.