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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-schema/SKILL.md

Quality

Content

63%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 well-structured and actionable with usable JSON-LD templates, but it is hurt by broken/incorrect reference paths, an unlinked and duplicated reference file, and verbose inline time-sensitive listings. Fixing the references and offloading the deprecated-types detail would raise both conciseness and progressive_disclosure.

Suggestions

Fix or remove the broken reference paths: replace '../seo/references/schema-types.md' and 'schema/templates.json' with a link to the actual file references/deprecated-types-2024-2026.md, or add the cited files to the bundle.

Move the inline deprecated-types date listings into references/deprecated-types-2024-2026.md and keep only a one-line pointer in the body to reduce duplication and improve conciseness.

Add an executable validation step (e.g., a Rich Results Test URL or a CLI command) to the Validation section so the guidance is concrete rather than abstract.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but carries extensive inline time-sensitive date listings for deprecated types that duplicate the existing references/deprecated-types-2024-2026.md file, plus some over-explanation (the JS rendering note), so it could be tightened toward anchor 4.	3 / 5
Actionability	It provides copy-paste-ready JSON-LD templates (Organization, LocalBusiness, Article) and a concrete error-handling table, but validation guidance is described abstractly ("Validate against Google's supported rich result types") without an executable command, leaving a minor gap at anchor 4.	4 / 5
Workflow Clarity	Detection and Generation are laid out as numbered sequences with a 'Validate output before presenting' checkpoint, giving a clear sequence with most checkpoints present; there is no explicit validate-fix-retry feedback loop, but the skill is not destructive, so anchor 4 fits better than 3.	4 / 5
Progressive Disclosure	Structure exists via clear sections, but the body cites paths that do not exist in the bundle (../seo/references/schema-types.md, schema/templates.json) while the actual reference file references/deprecated-types-2024-2026.md is not linked and its content is duplicated inline, matching anchor 3 (references present but not clearly signaled, content that should be separate is inline).	3 / 5
	Total	14 / 20 Passed

Description

87%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 is strong: it states concrete actions, an explicit format preference, and a clear 'Use when' clause with multiple natural trigger terms. Minor gaps in action specificity and a few missing synonyms keep two dimensions at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	"Detect, validate, and generate" names three concrete actions on a defined domain (Schema.org structured data), but coverage of the domain is somewhat high-level with minor gaps, matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	It explicitly answers both what ("Detect, validate, and generate Schema.org structured data. JSON-LD format preferred.") and when ("Use when user says ...") with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	It lists five natural trigger terms ("schema", "structured data", "rich results", "JSON-LD", "markup") giving good keyword coverage, but a few common synonyms such as "rich snippets" or "SERP" are missing, so it sits at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The Schema.org structured-data niche with its specific trigger terms is clearly distinct from other skills and carries minimal conflict risk, matching anchor 5.	5 / 5
	Total	18 / 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
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: 9279553

Reviewed: 16 hours 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.