CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

schema-noindex-conflict

Use when applies to any site that uses structured data for rich results. Use when investigating why valid schema markup does not produce rich results in Google Search.

Quality

70%

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/schema-noindex-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 strong, well-structured skill document: concrete detection checks, specific fix directives with a decision branch, and clean separation between the SKILL.md overview and the detailed reference file. Weaknesses are minor — some repetition of the core noindex fact and verification steps that are mentioned but not integrated into an explicit post-fix validation loop.

DimensionReasoningScore

Conciseness

The body is lean (~45 lines) and assumes Claude's competence — no explanation of what structured data or robots.txt are — but the core fact that Google ignores schema on noindexed pages is restated three times (intro, Quick Reference bullet 1, and the Explain section), a minor redundancy that could be trimmed. This matches the 'efficient with minor over-explanation' anchor rather than the 'every token earns its place' anchor.

4 / 5

Actionability

Check gives three concrete, executable tests (robots.txt block, `<meta name='robots'>` containing `noindex`, canonical pointing elsewhere) against a specific selector (`<script type='application/ld+json'>` rich-result types), and Fix gives specific directives including the conditional branch for pages that must stay noindexed. As an instruction-only skill the absence of code is not penalized, but there is no concrete method for enumerating pages that carry schema markup — a minor gap that keeps it at 4 rather than fully executable.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with an explicit decision branch ("If the page must remain noindexed, remove the schema markup"), and the Code Review section does call for verifying final page output. It is not a 5 because post-fix verification is described as something to explain rather than integrated as an explicit re-validation step in the workflow, and the batch audit ("Audit all pages with schema markup") has no feedback loop for confirming fixes took effect.

4 / 5

Progressive Disclosure

The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that keeps the summary level and pushes implementation details, code examples, and framework guidance to a clearly signaled, one-level-deep reference (`references/rule.md`), which exists and contains that detail (verified: 120-line rule file with code examples). This matches the anchor for a clear overview with well-signaled one-level references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

48%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 good domain keywords and a clear trigger scenario for diagnosing missing rich results, but it is missing an explicit 'what' statement (what the skill does — audit, detect, fix schema/noindex conflicts), which leaves completeness weak. The overly broad first trigger clause also raises conflict risk with general schema/SEO skills.

Suggestions

Add a leading capability statement in third person before the triggers, e.g. "Detects and resolves conflicts where valid rich-result schema (Product, Review, FAQ) is nullified by noindex directives, robots.txt blocks, or mismatched canonicals. Use when ..." so both 'what' and 'when' are explicit.

Include the core conflict keywords users would naturally say — "noindex", "indexability", "rich results not showing" — since a user with this problem is likely to mention noindex or blocked pages.

Drop or narrow the first trigger clause "applies to any site that uses structured data for rich results", which fires on any schema-related task and conflicts with general structured-data validation skills.

DimensionReasoningScore

Specificity

Names the domain ("structured data for rich results", "schema markup") and one concrete action ("investigating why valid schema markup does not produce rich results in Google Search"), but lists no audit or fix capabilities — matching the anchor for domain plus 1-2 concrete actions rather than the several specific actions required for a 4.

3 / 5

Completeness

The description is structurally two 'Use when...' clauses with no explicit 'what' statement of capabilities — matching the anchor example 'Use when working with documents'. It is not a 3 because that anchor requires a clear 'what' to be present, and here the 'what' is only implied by the trigger phrasing.

2 / 5

Trigger Term Quality

Good natural keyword coverage ("structured data", "rich results", "schema markup", "Google Search") including synonyms users would say, but missing the core conflict terms like "noindex", "indexability", or "rich snippets not showing" that a user with this exact problem would mention, so it falls short of the comprehensive coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The second trigger clause is distinct to the schema+noindex conflict, but the first clause "Use when applies to any site that uses structured data for rich results" would fire on virtually any schema or SEO task, creating real overlap risk with general structured-data validation skills — somewhat specific but still overlapping, rather than mostly distinct.

3 / 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/schema-noindex-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.