Schema markup

Skill bromso/metapowers/plugins/marketing/skills/schema-markup

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install

npx -y skills add bromso/metapowers --skill schema-markup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implement structured data markup for rich search results

SKILL.md

2.0 KB, 493 tokens by cl100k_base, as published. Nobody here has run it

Schema Markup

Plan and generate structured data (schema.org) for "$ARGUMENTS". Optimize for rich snippets, knowledge panels, and enhanced search results.

Prerequisites

Read .metapowers/marketing/$ARGUMENTS/00-strategy.md. If this file does not exist, tell the user:

Phase 0 (Strategy) has not been completed for "$ARGUMENTS". Run /marketing:customer-research $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/marketing/$ARGUMENTS/skip-log.md.

Process

Read context:
- Read .metapowers/marketing/$ARGUMENTS/00-strategy.md for product context
- Read .metapowers/marketing/$ARGUMENTS/01-reach.md if it exists (for SEO context)
Identify applicable schema types:
- Organization, Product, SoftwareApplication, WebSite
- Article, BlogPosting, HowTo, FAQ, Review
- BreadcrumbList, SearchAction, VideoObject
- Match schema types to page types
Audit current markup (if URL provided):
- Use WebFetch to check existing structured data
- Test with Google Rich Results Test patterns
- Identify missing or incorrect markup
Generate schema markup:
- Write JSON-LD for each identified page type
- Include all recommended properties (not just required)
- Ensure accuracy — schema must match visible page content
- Validate against schema.org specification
Write the artifact — append to .metapowers/marketing/$ARGUMENTS/02-act.md under a ## Schema Markup section:
- Schema Audit — current state (if applicable)
- Recommended Schema Types — per page type
- JSON-LD Templates — ready-to-implement code
- Implementation Guide — where and how to add each schema
- Testing Plan — how to validate after implementation

Output

Schema markup plan appended to .metapowers/marketing/$ARGUMENTS/02-act.md. Present the JSON-LD templates directly to the user for implementation.