What it does
Takes a schema validation error or warning (pasted from a testing tool's output) and translates it into plain language, then patches the specific JSON-LD property causing it, whether that's a missing required field, a wrong data type, or a value that doesn't match what's visible on the page.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/rich-results-troubleshooter/ (or ~/.claude/skills/rich-results-troubleshooter/ for all projects)
GitHub Copilot (VS Code)
.github/skills/rich-results-troubleshooter/
OpenAI Codex
.codex/skills/rich-results-troubleshooter/
Cursor
.cursor/skills/rich-results-troubleshooter/ (or ~/.cursor/skills/rich-results-troubleshooter/ globally)
Compatibility
Any WordPress site with existing JSON-LD schema. The user needs to supply the validator output (from a structured data testing tool) since this skill doesn't run one directly.
The complete SKILL.md for this skill:
---
name: rich-results-troubleshooter
description: Use when a user has a schema validation error or warning and wants it explained and fixed in their WordPress page's structured data. Triggers on "schema error", "structured data warning", "rich results test failed", or "invalid JSON-LD".
---
# Rich Results Troubleshooter
## When to use
The user has run a structured data test on a page, gotten errors or warnings, and wants them explained in plain language and fixed in the actual JSON-LD.
## Procedure
1. Get the validator's error/warning output and the current JSON-LD block it refers to.
2. Translate each error into plain language: what property is missing, wrong type, or mismatched, and why that specific rule exists.
3. Check whether the missing value actually exists on the page (and just wasn't mapped into the schema) versus genuinely absent from the content.
4. Patch the JSON-LD with the fix, using real page content for anything that exists, and flagging anything that would need new content added to the page first.
5. Recommend the user re-run the validator after the fix to confirm it's clear, rather than assuming the fix is complete.
## Guardrails
- Never fill a missing required property with a placeholder value just to clear the error, an invented rating or price is worse than no schema at all.
- Distinguish errors (block rich results entirely) from warnings (rich results may still show) so the user prioritizes correctly.