agentleFS
Sign inStart free
marketingskillsmarketingskills/seo/skills/schema-fix-writer/SKILL.md

schema-fix-writer

Skill7 starsChanged 5 months agoMITView on GitHub

Propose schema markup changes from page type and SERP context. Use when Codex needs to write or fix structured data for better SERP display and rich results eligibility.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the page's current schema markup for errors or missing fields.

    line 21
  2. Distinctive:

    Add missing schema type for the page type

    line 24
  3. Distinctive:

    Add relevant properties (review, FAQ, how-to steps, etc.)

    line 26
  4. Distinctive:

    Remove deceptive or irrelevant markup

    line 27
  5. Distinctive:

    Write the JSON-LD or microdata snippet.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Schema Fix Writer

Overview

Given a page URL and its content, analyze what schema types would be appropriate and propose specific JSON-LD or microdata changes. Uses the page type (article, product, FAQ, how-to, local business, etc.) and current SERP features to determine the best schema strategy.

Inputs

  • Page URL and optionally its rendered content
  • Current schema (if any) — paste from source or tool output
  • Page type or topic

Workflow

  1. Determine the page type from content analysis.
  2. Check the page's current schema markup for errors or missing fields.
  3. Research the target SERP for rich result types present.
  4. Propose schema changes:
    • Add missing schema type for the page type
    • Fix validation errors in existing schema
    • Add relevant properties (review, FAQ, how-to steps, etc.)
    • Remove deceptive or irrelevant markup
  5. Write the JSON-LD or microdata snippet.
  6. Include testing instructions (Schema.org validator, Rich Results Test).

Output

Schema recommendation with proposed markup, validation notes, and SERP eligibility impact.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free