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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/schema-noindex-conflict/SKILL.md

Quality

Content

72%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 content is a well-structured, concise overview with excellent progressive disclosure to a single reference file. Its main weakness is the lack of an explicit verification/feedback loop for the batch audit, which caps workflow clarity.

Suggestions

Add a verification checkpoint to the body (e.g., after Fix, re-run the Check or confirm via Google Rich Results Test / Search Console) to establish a validate-fix-retry loop.

Remove the small overlap between the Quick Reference bullets and the Check section to tighten conciseness.

Surface a one-line note that the audit is batch-oriented (crawl all schema pages) so the per-page check reads as part of a larger sweep.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with tight Check and Fix sections and no padding about concepts Claude already knows; minor redundancy between Quick Reference and Check, and a slightly duplicative intro, keep it just below a 5.	4 / 5
Actionability	Check gives three concrete per-page tests (robots.txt block, meta robots noindex, canonical) and Fix gives specific remediation steps; as an instruction-only audit skill the guidance is actionable with only minor gaps, deferring code examples appropriately to the reference.	4 / 5
Workflow Clarity	A clear Check-then-Fix sequence exists, but the body omits any validation/verification checkpoint for what is a batch site-wide audit, so the destructive/batch cap of 3 applies even though the single-page steps are well ordered.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with clearly signaled, one-level-deep navigation to references/rule.md (verified present), and content is appropriately split between overview and detail file.	5 / 5
	Total	16 / 20 Passed

Description

65%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 strong, explicit trigger guidance and a clear niche, but is light on concrete capability verbs. Tightening the 'what' from generic investigating to specific detection actions would raise it.

Suggestions

Replace the generic 'investigating' with concrete actions, e.g. 'Detects pages where rich-result schema markup is negated by noindex, robots.txt blocks, or non-self canonicals.'

Add natural synonyms users say ('JSON-LD', 'rich snippets', 'structured data not showing') to broaden trigger coverage.

Consolidate the two 'Use when' clauses so the what and when read as one crisp sentence.

Dimension	Reasoning	Score
Specificity	The description names the domain clearly ('structured data for rich results', 'schema markup') but the only action stated is generic 'investigating', with no concrete detection or remediation verbs, matching the anchor where actions are minimal.	2 / 5
Completeness	Two explicit 'Use when' clauses give a clear trigger, and 'investigating why valid schema markup does not produce rich results' supplies a what, but the what could be more action-specific (e.g., 'detects schema+noindex conflicts') to reach a 5.	4 / 5
Trigger Term Quality	Natural SEO terms ('structured data', 'rich results', 'schema markup', 'Google Search') cover the domain well and are phrases users would actually say, though synonyms like 'JSON-LD' or 'rich snippets' are missing.	4 / 5
Distinctiveness Conflict Risk	The schema/noindex/rich-results niche is distinct with specific triggers and low conflict risk, though it could overlap slightly with broader SEO indexability skills, keeping it just below a 5.	4 / 5
	Total	14 / 20 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/schema-noindex-conflict/SKILL.md
Commit: 30756a7

Reviewed: 13 days 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.