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," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
81
73%
Does it follow best practices?
Impact
93%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/schema-markup/SKILL.mdQuality
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 boundaries distinguishing it from related skills. The explicit 'Use when' clause with comprehensive trigger terms and cross-references to related skills are particularly effective. The main weakness is that the capability description could be more specific about concrete actions beyond 'add, fix, or optimize.'
Suggestions
Expand the capability description to list specific concrete actions like 'generate JSON-LD code, validate existing schema, implement FAQ/Product/Review markup, debug rich results errors.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (schema markup/structured data) and mentions actions like 'add, fix, or optimize,' but doesn't list multiple specific concrete actions like 'generate JSON-LD code, validate schema, implement FAQ markup.' | 2 / 3 |
Completeness | Clearly answers both what ('add, fix, or optimize schema markup and structured data') and when ('Use when the user mentions...' with explicit trigger list, plus 'whenever someone wants their pages to show enhanced results in Google'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'schema markup,' 'structured data,' 'JSON-LD,' 'rich snippets,' 'schema.org,' 'FAQ schema,' 'product schema,' 'review schema,' 'breadcrumb schema,' 'Google rich results,' 'knowledge panel,' 'star ratings in search.' | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on schema markup/structured data with explicit boundaries distinguishing it from related skills ('For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo'). | 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 solid reference structure for schema markup implementation with good organization and appropriate progressive disclosure. However, it lacks executable code examples (relying on external file references), includes some unnecessary explanatory content Claude already knows, and could benefit from a clearer step-by-step implementation workflow with explicit validation checkpoints.
Suggestions
Add at least one complete, executable JSON-LD example inline (e.g., Organization or FAQPage) rather than only referencing external files
Remove the 'Core Principles' section or condense to a single line - Claude knows accuracy matters and to follow guidelines
Add an explicit numbered workflow: 1. Audit existing schema → 2. Generate JSON-LD → 3. Validate with Rich Results Test → 4. If errors, fix and re-validate → 5. Deploy
Replace the incomplete @graph example with a complete, copy-paste ready version
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., 'Your goal is to implement schema.org markup that helps search engines understand content'). The core principles section explains concepts Claude already knows. Could be tightened. | 2 / 3 |
Actionability | Provides useful reference tables and mentions JSON-LD format, but the actual code example is incomplete (shows structure with '...' placeholders). References external file for complete examples rather than providing executable code inline for common cases. | 2 / 3 |
Workflow Clarity | Has a testing checklist and validation tools listed, but lacks explicit step-by-step workflow with validation checkpoints. The implementation section describes approaches but doesn't sequence them with verification steps. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for quick reference, and properly signaled external reference to schema-examples.md. Related skills are clearly linked at the end. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- 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.