seo-schema

Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".

Quality

82%

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

Quality

Content

65%

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

The body is actionable and well-organized with strong templates and error handling, but loses points for verbose inline dated content, a missing validate→fix→retry checkpoint, and references to bundle files that do not exist.

Suggestions

Add an explicit validate-then-retry checkpoint to the Generation workflow (e.g. generate → run Rich Results Test → fix issues → re-test → present), modeled on the validation table.

Fix or remove the dangling references to '../seo/references/schema-types.md' and 'schema/templates.json', and link the existing references/deprecated-types-2024-2026.md from the DEPRECATED section so the bundled reference is actually used.

Move the full JSON-LD templates into the references file and keep only a compact Quick-start example inline to improve token efficiency and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete checklists and templates, but full inline JSON-LD templates and many inline dated deprecation entries (e.g. 'May 7, 2026', '2026-01-06') add tokens that could be trimmed or pushed to the reference file; not the lean 3-anchor.	2 / 3
Actionability	Provides complete, copy-paste-ready JSON-LD templates for Organization, LocalBusiness, and Article, plus a concrete validation checklist and a scenario→action error table — fully executable guidance.	3 / 3
Workflow Clarity	Generation steps are listed but lack an explicit validation checkpoint or feedback loop for the detect→validate→generate flow; the 'Validate output before presenting' step is present but not framed as a verify-and-retry gate, capping it at 2 per the rubric.	2 / 3
Progressive Disclosure	The body signals external references — '../seo/references/schema-types.md' and 'schema/templates.json' — but neither path exists in the bundle (only references/deprecated-types-2024-2026.md is present and is not referenced), so navigation is broken and full templates live inline rather than in a separate file.	2 / 3
	Total	9 / 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.

The description is concise, third-person, and explicit about both capability and triggers, hitting the highest anchor on all four dimensions. It is a strong model description with no padding.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — 'Detect, validate, and generate Schema.org structured data' — matching the 'lists multiple specific concrete actions' anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly states what it does (detect/validate/generate) and when to use it via the 'Use when user says...' clause, satisfying both halves of the highest anchor; not capped at 2 because the trigger guidance is explicit.	3 / 3
Trigger Term Quality	Quotes natural user phrasings — "schema", "structured data", "rich results", "JSON-LD", or "markup" — giving broad coverage of terms a user would actually say, not jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear SEO/structured-data niche with distinct, specific triggers, making overlap with unrelated skills unlikely; not merely 'works with document files' as at anchor 2.	3 / 3
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-seo
Path: skills/seo-schema/SKILL.md
Commit: 09d37c7

Reviewed: 4 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.