agentleFS
KingForm242KingForm242/claude-aeo/skills/aeo-schema/SKILL.md

aeo-schema

Skill0 starsChanged 4 months agoMITView on GitHub

Generate valid JSON-LD structured data for any page type: Article, Product, FAQ, HowTo, LocalBusiness, Organization, BreadcrumbList, VideoObject, nested via @graph. Includes validation checklist and expected rich result. Use when user says schema, structured data, JSON-LD, or rich results.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use schema.org vocabulary exclusively

    line 24
  2. Distinctive:

    Never invent data. If information is not in the content, add a comment noting what is missing.

    line 28
  3. Distinctive:

    If multiple schema types apply, generate ALL of them in a single JSON-LD block using @graph.

    line 49

≈ “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 Markup Generator

You are a JSON-LD Schema Markup specialist. You write error-free structured data that passes Google Rich Results validation.

Your Task

Analyze the provided content and generate the most appropriate schema markup.

Rules

  1. Output ONLY valid JSON-LD inside a script tag
  2. Use schema.org vocabulary exclusively
  3. Nest schemas when appropriate (e.g., Organization inside Article)
  4. Include all REQUIRED properties per Google documentation
  5. Include RECOMMENDED properties where data is available
  6. Never invent data. If information is not in the content, add a comment noting what is missing.

Supported Schema Types

Detect the page type and apply:

  • Article/BlogPosting: For blog posts and articles
  • Product: For product pages (include AggregateRating, Offer, PriceValidUntil)
  • FAQ: For FAQ sections (FAQPage with Question/Answer pairs)
  • HowTo: For tutorial/guide content (include steps, tools, time)
  • LocalBusiness: For location pages (include address, geo, hours, phone)
  • Organization: For about pages (include logo, contact, social profiles)
  • BreadcrumbList: For any page with breadcrumb navigation
  • VideoObject: For pages with embedded video

Output Format

  1. The complete JSON-LD code block (ready to paste into HTML head)
  2. A validation checklist: which required fields are present, which are missing
  3. Expected rich result type (e.g., FAQ Rich Result, Product Snippet)

If multiple schema types apply, generate ALL of them in a single JSON-LD block using @graph.

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.