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 both 'what' and 'when' clauses plus a helpful cross-reference to a related skill. The main weakness is that the capability description could be more specific about concrete actions beyond 'add, fix, or optimize.' Overall, it would perform well in a multi-skill selection scenario.

Suggestions

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

Dimension	Reasoning	Score
Specificity	The description names the domain (schema markup/structured data) and mentions actions like 'add, fix, or optimize,' but doesn't list multiple specific concrete actions such as 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 'Use when' clause with trigger terms). Also includes a helpful cross-reference to the seo-audit skill for disambiguation.	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.	3 / 3
Distinctiveness Conflict Risk	Very distinct niche focused specifically on schema markup and structured data, with explicit disambiguation from the broader seo-audit skill. The specific trigger terms like 'JSON-LD,' 'schema.org,' and various schema types make it unlikely to conflict with other 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 is well-organized with good progressive disclosure and useful reference tables, but it leans too heavily on descriptive guidance rather than concrete, executable examples. The core principles section states things Claude already knows, and the implementation section is too vague to be immediately actionable. The validation workflow exists but isn't tightly integrated into the implementation steps.

Suggestions

Include at least one complete, copy-paste-ready JSON-LD example inline (e.g., a full Article or FAQPage schema) rather than deferring all examples to the reference file.

Remove or drastically condense the 'Core Principles' section—Claude already knows to be accurate, follow guidelines, and validate; these waste tokens.

Integrate validation as an explicit checkpoint within the implementation workflow (e.g., 'After adding JSON-LD: 1. Validate with Rich Results Test 2. If errors, fix and re-validate 3. Only then deploy').

Replace the vague implementation guidance for dynamic sites with a concrete code snippet (e.g., a Next.js component rendering JSON-LD via next/head).

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 one concrete code example (@graph pattern) and useful reference tables, but most guidance is descriptive rather than executable. The implementation section for dynamic sites and CMS is vague ('Component that renders schema,' 'Plugins (Yoast, Rank Math)'). Full JSON-LD examples are deferred to a reference file rather than providing at least one complete, copy-paste-ready example inline.	2 / 3
Workflow Clarity	There's a reasonable sequence implied (assess → implement → validate → deploy) and a testing checklist, but the workflow lacks explicit validation checkpoints integrated into the implementation steps. The validation section is separate from implementation rather than being woven in as a mandatory step before deployment.	2 / 3
Progressive Disclosure	The skill provides a clear overview with well-organized sections and appropriately defers complete JSON-LD examples to a reference file (references/schema-examples.md). Related skills are clearly signaled at the bottom. The structure is easy to navigate with tables and headers.	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: 05d40bb

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