schema-markup

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/schema-markup/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and clear completeness, including an explicit 'when to use' clause and a helpful cross-reference to a related skill. The main weakness is that the specificity of capabilities could be improved by listing more concrete actions beyond 'add, fix, or optimize.' The description also correctly uses third person voice throughout.

Suggestions

Expand the capability list with more specific actions, e.g., 'Generates JSON-LD snippets, validates existing schema markup, implements FAQ/product/review/breadcrumb schemas, and troubleshoots rich snippet issues.'

Dimension	Reasoning	Score
Specificity	The description names the domain (schema markup and structured data) and mentions some actions ('add, fix, or optimize'), but doesn't list specific concrete capabilities like generating JSON-LD snippets, validating existing markup, or implementing specific schema types.	2 / 3
Completeness	Clearly answers both 'what' (add, fix, or optimize schema markup and structured data) and 'when' (explicit trigger terms listed, plus a cross-reference to seo-audit for broader SEO issues). The 'Use when' clause is explicit and comprehensive.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'schema markup,' 'structured data,' 'JSON-LD,' 'rich snippets,' 'schema.org,' 'FAQ schema,' 'product schema,' 'review schema,' and 'breadcrumb schema.' These are all terms users would naturally use when requesting this type of work.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche focused specifically on schema markup/structured data. The cross-reference to 'seo-audit' for broader SEO issues explicitly delineates boundaries, reducing conflict risk with related skills.	3 / 3
	Total	11 / 12 Passed

Implementation

57%

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

This skill provides a reasonable overview of schema markup implementation with good structure and progressive disclosure, but falls short on actionability by not including complete executable JSON-LD examples for the most common schema types. The core principles section is largely unnecessary padding that Claude already knows, and the workflow could benefit from explicit sequencing with validation gates.

Suggestions

Add at least 2-3 complete, copy-paste ready JSON-LD examples inline for the most common types (e.g., Article, Product, FAQPage) rather than deferring all examples to a reference file.

Remove or drastically condense the 'Core Principles' section—Claude already knows to be accurate, follow guidelines, and validate; replace with specific gotchas or non-obvious constraints.

Add an explicit numbered workflow: 1. Audit existing schema → 2. Draft JSON-LD → 3. Validate with Rich Results Test → 4. If errors, fix and re-validate → 5. Only deploy when passing.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like 'Core Principles' that are general best practices Claude already knows (e.g., 'accuracy first,' 'validate everything'). The 'Task-Specific Questions' section at the end is also somewhat redundant given the 'Initial Assessment' section. However, the tables and quick references are reasonably efficient.	2 / 3
Actionability	The skill provides a table of schema types and required properties, plus one code example for @graph, but lacks complete executable JSON-LD examples for the most common types (Organization, Article, Product, FAQ). It references 'references/schema-examples.md' for complete examples, but the main skill itself mostly describes rather than provides copy-paste ready markup.	2 / 3
Workflow Clarity	There's a general flow implied (assess → implement → validate → deploy) and a testing checklist, but the workflow lacks explicit sequencing with validation checkpoints. For schema implementation which can break rich results, there should be a clearer step-by-step process with a validate-before-deploy feedback loop explicitly sequenced.	2 / 3
Progressive Disclosure	The skill is well-structured with clear sections, a table for quick scanning, and appropriately references 'references/schema-examples.md' for detailed examples rather than inlining them. Related skills are clearly signaled at the bottom. Navigation is straightforward and one level deep.	3 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: freekmurze/dotfiles
Commit: 2c6f6e8

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