plugins/pm-growth/skills/schema-markup/SKILL.md
Generate structured-data (Schema.org / JSON-LD) markup to win rich results in search. Use when asked about schema markup, structured data, rich snippets, JSON-LD, or making a page eligible for stars/FAQ/breadcrumb results. Produces valid JSON-LD for the right schema type, the rich-result it targets, required vs. recommended fields, and validation/guideline notes.
npx skillsauth add mohitagw15856/pm-claude-skills schema-markupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured data tells search engines exactly what a page is — a product, a recipe, an FAQ, an event — making it eligible for rich results (star ratings, FAQ drop-downs, breadcrumbs) that win clicks. This skill produces valid JSON-LD for the right Schema.org type, with the fields Google actually requires, and flags the guideline traps that get markup ignored or penalised.
Ask for these only if they aren't already provided:
Target rich result — which Google rich result this enables, and the eligibility note (e.g. review snippets need real, visible reviews).
Schema type — the correct Schema.org type (and any nesting, e.g. Product → AggregateRating + Offer).
JSON-LD — ready to paste in a <script type="application/ld+json"> block:
{
"@context": "https://schema.org",
"@type": "...",
"...": "..."
}
Use the real provided values; mark any placeholders clearly.
Required vs. recommended fields — what Google requires for the rich result vs. nice-to-have, so nothing essential is missing.
Validation & guidelines — test in Google's Rich Results Test + Schema validator; the key rules: markup must reflect visible page content, no fake/marked-up-but-hidden data, no review spam (no self-serving aggregate ratings without real reviews). Note anything that would disqualify it.
Schema.org structured data + Google's structured-data guidelines for rich results (JSON-LD, required fields, content-match rules).
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.