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.
78
Quality
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/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 disambiguation from related skills. The main weakness is that the 'what' portion could be more specific about concrete capabilities (e.g., 'generate JSON-LD code, validate existing schemas, implement FAQ/Product/Review markup'). The explicit cross-reference to seo-audit is a best practice for avoiding skill conflicts.
Suggestions
Expand the capabilities section with more specific actions like 'generate JSON-LD code, validate existing schemas, debug rich snippet errors' to improve specificity score
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (schema markup/structured data) and some actions ('add, fix, or optimize'), but doesn't list comprehensive concrete actions like specific schema types it can create or validation capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('add, fix, or optimize schema markup and structured data') and when ('when the user wants to...' plus explicit 'Also use when' clause with trigger terms). Also includes helpful disambiguation with seo-audit reference. | 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' - these are exactly what users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on schema markup/structured data with distinct triggers. The explicit reference to 'For broader SEO issues, see seo-audit' actively prevents conflicts 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 solid reference material for schema markup with good organization and appropriate progressive disclosure. However, it leans toward being a reference document rather than actionable guidance—it tells Claude what schema types exist but doesn't provide enough executable examples or clear implementation workflows with validation checkpoints.
Suggestions
Add 2-3 complete, copy-paste ready JSON-LD examples inline for the most common schema types (Article, Product, FAQPage) rather than deferring all examples to a reference file
Create an explicit implementation workflow: 1) Audit existing schema → 2) Generate new schema → 3) Validate with Rich Results Test → 4) Fix errors → 5) Deploy only when valid
Remove the 'You are an expert...' framing and 'Core Principles' section—Claude knows these concepts; replace with specific gotchas or edge cases
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('You are an expert...') and explanatory text that Claude doesn't need. The tables and quick references are well-structured, but some sections like 'Core Principles' explain concepts Claude already understands. | 2 / 3 |
Actionability | Provides useful reference tables and a JSON-LD example for @graph, but lacks complete executable examples for most schema types. References external file for examples rather than providing copy-paste ready code inline for common cases. | 2 / 3 |
Workflow Clarity | Has a testing checklist and mentions validation tools, but lacks explicit validation-first workflow with feedback loops. The 'Initial Assessment' section provides good discovery questions, but implementation steps aren't clearly sequenced with checkpoints. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for quick reference, and properly signaled one-level-deep reference to schema-examples.md for detailed examples. Related skills are clearly linked at the end. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
355d067
- 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.