CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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 actionable for an instruction-only SEO skill, with a clear workflow including a verification step and a properly signaled single reference file. Its main weaknesses are mild redundancy between the intro and Explain sections and the absence of executable code.

Suggestions

Consolidate the robots.txt-vs-noindex mechanism explanation into one section (e.g., Explain) and trim the intro to a single non-obvious insight to avoid restating the same concept twice.

Add a small executable snippet in the Code Review section (e.g., fetching robots.txt and matching a Disallow pattern) to lift actionability toward copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the intro paragraph and the 'Explain' section both restate the same robots.txt-vs-noindex mechanism, which could be tightened into one place.

2 / 3

Actionability

Provides concrete instructional guidance (numbered Fix steps with specific conditionals, a four-signal Check list, and a Code Review procedure), but contains no executable, copy-paste-ready code or commands, so it stops short of the fully-executable anchor.

2 / 3

Workflow Clarity

A clear Check → Fix → Verify sequence is present with an explicit validation checkpoint in step 4 ('Verify after fixing using Google Search Console URL Inspection'), satisfying the anchor for a clear sequence with explicit validation.

3 / 3

Progressive Disclosure

Well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) plus a clearly signaled, one-level-deep pointer to the existing 'references/rule.md' for implementation details, matching the anchor for a clear overview with well-signaled references.

3 / 3

Total

10

/

12

Passed

Description

100%

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 strong, well-scoped description that uses a clear 'Use when...' trigger, names concrete auditing actions, and employs natural SEO terminology with low conflict risk. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete auditing actions tied to a specific domain: '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', matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (auditing indexability conflicts) and when, opening with a clear 'Use when...' trigger covering multiple scenarios.

3 / 3

Trigger Term Quality

Uses natural terms an SEO practitioner would actually say — 'indexability issues', 'Google's index', 'robots.txt', and 'meta robots' — with good coverage rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

The niche is narrowly scoped to indexability/robots.txt conflicts with distinct SEO-auditing triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.