Agent skill

Schema Markup

by OpenClaudia in OpenClaudia/openclaudia-skills

Generate Schema.org structured data (JSON-LD) for any page type.

Install Schema Markup

skills CLI

$ npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install OpenClaudia/openclaudia-skills schema-markup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/schema-markup .claude/skills/schema-markup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "schema-markup" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup into .claude/skills/schema-markup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-markup", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OpenClaudia/openclaudia-skills schema-markup --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/schema-markup .agents/skills/schema-markup && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "schema-markup" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup into .agents/skills/schema-markup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-markup", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OpenClaudia/openclaudia-skills schema-markup --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/schema-markup .cursor/skills/schema-markup && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "schema-markup" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup into .cursor/skills/schema-markup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-markup", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/OpenClaudia/openclaudia-skills.git --path skills/schema-markup

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OpenClaudia/openclaudia-skills schema-markup --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/schema-markup .gemini/skills/schema-markup && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "schema-markup" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup into .gemini/skills/schema-markup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-markup", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install OpenClaudia/openclaudia-skills schema-markup

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/schema-markup .github/skills/schema-markup && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "schema-markup" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup into .github/skills/schema-markup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-markup", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OpenClaudia/openclaudia-skills schema-markup --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/schema-markup .opencode/skills/schema-markup && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "schema-markup" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/schema-markup into .opencode/skills/schema-markup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema-markup", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: schema-markup
GitHub stars: 713
Token cost: ~4k tokens
SKILL.md length: 681 words
Files: 1
Skills in repo: 74
Repo updated: Sep 18, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate Schema.org structured data (JSON-LD) for any page type.

Works in 8 steps: Article / BlogPosting / NewsArticle → Product → FAQPage → …
The user says schema markup
SKILL.md covers Supported Schema Types, Multi-Schema Pages, Generation Process and Implementation Instructions, plus 2 more sections
Reaches schema.org and twitter.com

What it does

Schema Markup is an agent skill from OpenClaudia/openclaudia-skills. Generate Schema.org structured data (JSON-LD) for any page type. Use when the user says "schema markup", "structured data", "JSON-LD", "rich snippets", "rich results", "FAQ schema", "product schema", "article schema", "breadcrumb schema", "organization schema", "how-to schema", "review schema", or asks about structured data for SEO.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Schema markup. The repository describes itself as: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.

When your agent uses it

The user says schema markup
Structured data
Breadcrumb schema
Organization schema

Example prompts

“schema markup”
“structured data”
“JSON-LD”
“/schema-markup”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Article / BlogPosting / NewsArticle
Product
FAQPage
HowTo
Organization
LocalBusiness
BreadcrumbList
Review / AggregateRating

What it can do on your machine

Read from SKILL.md and the folder at commit 28bf209. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json, typescript and html).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- schema.org
- twitter.com
- linkedin.com
- facebook.com
- github.com
- maps.google.com
Also links to:
- search.google.com
- validator.schema.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Schema Markup loads about 4k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 681 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~87
When it runs · the whole SKILL.md, loaded when a task matches: ~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OpenClaudia/openclaudia-skills at commit 28bf209, republished under its MIT licence (© OpenClaudia). 681 words, ~4,045 tokens.

Download SKILL.mdSave it as .claude/skills/schema-markup/SKILL.md (or your agent's skills folder).

name: schema-markup
description: Generate Schema.org structured data (JSON-LD) for any page type. Use when the user says "schema markup", "structured data", "JSON-LD", "rich snippets", "rich results", "FAQ schema", "product schema", "article schema", "breadcrumb schema", "organization schema", "how-to schema", "review schema", or asks about structured data for SEO.

Schema Markup Generator Skill

You are an expert in Schema.org structured data and Google's rich results requirements. Generate valid, complete JSON-LD markup that maximizes eligibility for Google rich results.

Supported Schema Types

This skill supports the following schema types. When the user asks for schema, determine which type(s) are appropriate based on the page content.

1. Article / BlogPosting / NewsArticle

Use for: Blog posts, news articles, editorial content Rich result: Article carousel, headline in search

json

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title (max 110 characters)",
  "description": "Brief description of the article (max 160 characters)",
  "image": [
    "https://example.com/image-16x9.jpg",
    "https://example.com/image-4x3.jpg",
    "https://example.com/image-1x1.jpg"
  ],
  "datePublished": "2025-01-15T08:00:00+00:00",
  "dateModified": "2025-01-20T10:30:00+00:00",
  "author": [{
    "@type": "Person",
    "name": "Author Name",
    "url": "https://example.com/author/name",
    "jobTitle": "Senior Editor",
    "sameAs": [
      "https://twitter.com/authorhandle",
      "https://linkedin.com/in/authorname"
    ]
  }],
  "publisher": {
    "@type": "Organization",
    "name": "Publisher Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png",
      "width": 600,
      "height": 60
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/article-url"
  },
  "wordCount": 2500,
  "articleSection": "Technology",
  "keywords": ["keyword1", "keyword2", "keyword3"],
  "isAccessibleForFree": true
}

Google requirements:

headline is required (max 110 characters)
image is required (provide 3 aspect ratios: 16:9, 4:3, 1:1; each > 696px wide)
datePublished is required (ISO 8601 format)
author.name is required
For NewsArticle, also add dateline if applicable
For BlogPosting, @type changes to "BlogPosting"

2. Product

Use for: Product pages, e-commerce listings Rich result: Product snippet with price, availability, reviews

json

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Product description",
  "image": [
    "https://example.com/product-1.jpg",
    "https://example.com/product-2.jpg"
  ],
  "sku": "SKU-12345",
  "mpn": "MPN-67890",
  "gtin13": "0123456789012",
  "brand": {
    "@type": "Brand",
    "name": "Brand Name"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/product",
    "priceCurrency": "USD",
    "price": "99.99",
    "priceValidUntil": "2025-12-31",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "seller": {
      "@type": "Organization",
      "name": "Seller Name"
    },
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": {
        "@type": "MonetaryAmount",
        "value": "0",
        "currency": "USD"
      },
      "deliveryTime": {
        "@type": "ShippingDeliveryTime",
        "handlingTime": {
          "@type": "QuantitativeValue",
          "minValue": 0,
          "maxValue": 1,
          "unitCode": "DAY"
        },
        "transitTime": {
          "@type": "QuantitativeValue",
          "minValue": 1,
          "maxValue": 5,
          "unitCode": "DAY"
        }
      },
      "shippingDestination": {
        "@type": "DefinedRegion",
        "addressCountry": "US"
      }
    },
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    }
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "bestRating": "5",
    "ratingCount": "142"
  },
  "review": [{
    "@type": "Review",
    "author": {
      "@type": "Person",
      "name": "Reviewer Name"
    },
    "datePublished": "2025-01-10",
    "reviewBody": "Review text here",
    "reviewRating": {
      "@type": "Rating",
      "ratingValue": "5",
      "bestRating": "5"
    }
  }]
}

Google requirements:

name is required
offers, review, or aggregateRating - at least one required
offers.price and offers.priceCurrency required if offers present
offers.availability must use Schema.org enum values
As of 2024, shippingDetails and hasMerchantReturnPolicy are recommended for merchant listings

3. FAQPage

Use for: FAQ sections, Q&A pages Rich result: Expandable FAQ in search results

json

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the first question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>The answer with <strong>HTML formatting</strong> allowed. You can include <a href=\"https://example.com\">links</a>.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "What is the second question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Plain text answers also work."
      }
    }
  ]
}

Google requirements:

Each Question must have exactly one acceptedAnswer
Answer text can include HTML: <h2> through <h6>, <br>, <ol>, <ul>, <li>, <a>, <p>, <b>, <strong>, <i>, <em>
Must be visible on the page (not hidden behind tabs/accordions without proper implementation)
Google may show up to 3 FAQ rich results per page
Do not use for advertising purposes

4. HowTo

Use for: Tutorial pages, step-by-step guides, DIY instructions Rich result: Step-by-step display in search results

json

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Do Something",
  "description": "Brief description of the task",
  "image": {
    "@type": "ImageObject",
    "url": "https://example.com/howto-main.jpg",
    "height": "406",
    "width": "305"
  },
  "totalTime": "PT30M",
  "estimatedCost": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": "20"
  },
  "supply": [
    {
      "@type": "HowToSupply",
      "name": "Supply item 1"
    },
    {
      "@type": "HowToSupply",
      "name": "Supply item 2"
    }
  ],
  "tool": [
    {
      "@type": "HowToTool",
      "name": "Tool 1"
    }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "name": "Step 1 Title",
      "text": "Detailed instructions for step 1.",
      "url": "https://example.com/howto#step1",
      "image": "https://example.com/step1.jpg"
    },
    {
      "@type": "HowToStep",
      "name": "Step 2 Title",
      "text": "Detailed instructions for step 2.",
      "url": "https://example.com/howto#step2",
      "image": "https://example.com/step2.jpg"
    }
  ]
}

Google requirements:

name is required
step array is required with at least one step
Each step needs either text or itemListElement with HowToDirection/HowToTip
totalTime uses ISO 8601 duration format (PT1H30M = 1 hour 30 minutes)
Do not use HowTo for recipes (use Recipe schema instead)

5. Organization

Use for: Homepage, about page, company information Rich result: Knowledge panel, logo in search

json

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Company Name",
  "alternateName": "Company Abbreviation",
  "url": "https://example.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/logo.png",
    "width": 512,
    "height": 512
  },
  "description": "Company description",
  "foundingDate": "2020-01-01",
  "founder": {
    "@type": "Person",
    "name": "Founder Name"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94102",
    "addressCountry": "US"
  },
  "contactPoint": [{
    "@type": "ContactPoint",
    "telephone": "+1-555-555-5555",
    "contactType": "customer service",
    "areaServed": "US",
    "availableLanguage": "English"
  }],
  "sameAs": [
    "https://twitter.com/company",
    "https://linkedin.com/company/company",
    "https://facebook.com/company",
    "https://github.com/company"
  ],
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "minValue": 10,
    "maxValue": 50
  }
}

6. LocalBusiness

Use for: Local business pages, Google Business Profile support Rich result: Local business panel, map results

json

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "https://example.com/#business",
  "name": "Business Name",
  "description": "Business description",
  "url": "https://example.com",
  "telephone": "+1-555-555-5555",
  "email": "info@example.com",
  "image": "https://example.com/storefront.jpg",
  "logo": "https://example.com/logo.png",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94102",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": "37.7749",
    "longitude": "-122.4194"
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "17:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "10:00",
      "closes": "14:00"
    }
  ],
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "bestRating": "5",
    "ratingCount": "312"
  },
  "areaServed": {
    "@type": "City",
    "name": "San Francisco"
  },
  "hasMap": "https://maps.google.com/?cid=123456789"
}

Google requirements:

name, address are required
Use specific subtypes when possible: Restaurant, Dentist, LegalService, RealEstateAgent, etc.
geo coordinates should be accurate to the business location
openingHoursSpecification must reflect actual business hours

7. BreadcrumbList

Use for: Any page with breadcrumb navigation Rich result: Breadcrumb trail in search results

json

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Category",
      "item": "https://example.com/category"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Current Page Title"
    }
  ]
}

Google requirements:

position must be sequential starting at 1
Last item should not have item (it's the current page)
Must match the visible breadcrumb on the page

Show full SKILL.md (270 more words)Show less

8. Review / AggregateRating

Use for: Review pages, product reviews, service reviews Rich result: Star rating in search results

json

{
  "@context": "https://schema.org",
  "@type": "Review",
  "name": "Review Title",
  "reviewBody": "Full review text...",
  "datePublished": "2025-01-15",
  "author": {
    "@type": "Person",
    "name": "Reviewer Name"
  },
  "itemReviewed": {
    "@type": "Product",
    "name": "Product Being Reviewed",
    "image": "https://example.com/product.jpg"
  },
  "reviewRating": {
    "@type": "Rating",
    "ratingValue": "4",
    "bestRating": "5",
    "worstRating": "1"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Review Site Name"
  }
}

Google requirements:

author is required (must be a valid Person or Organization)
itemReviewed is required
reviewRating is recommended
Self-serving reviews (reviewing your own product) are against guidelines

Multi-Schema Pages

Most pages need multiple schema types. Combine them using @graph:

json

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Company Name",
      "url": "https://example.com",
      "logo": "https://example.com/logo.png"
    },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "https://example.com",
      "name": "Site Name",
      "publisher": { "@id": "https://example.com/#organization" }
    },
    {
      "@type": "WebPage",
      "@id": "https://example.com/page/#webpage",
      "url": "https://example.com/page/",
      "name": "Page Title",
      "isPartOf": { "@id": "https://example.com/#website" }
    },
    {
      "@type": "Article",
      "mainEntityOfPage": { "@id": "https://example.com/page/#webpage" },
      "headline": "Article Title",
      "author": { "@type": "Person", "name": "Author" },
      "publisher": { "@id": "https://example.com/#organization" },
      "datePublished": "2025-01-15"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com" },
        { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog" },
        { "@type": "ListItem", "position": 3, "name": "Article Title" }
      ]
    }
  ]
}

Generation Process

When the user asks for schema markup:

Determine page type - Ask what kind of page this is for (or infer from context)
Gather information - Ask for or collect the required fields. If the user provides a URL, fetch it to extract data.
Select schema types - Choose all applicable schemas (most pages need 2-4 types)
Generate JSON-LD - Create complete, valid markup
Validate - Check against Google's requirements for each type
Provide implementation instructions - Tell the user exactly where to place it

Implementation Instructions

For Next.js App Router:

tsx

// In your page component or layout
export default function Page() {
  const jsonLd = {/* generated schema */};

  return (
    <>
      <script
        type="application/ld+json"
        dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
      />
      {/* page content */}
    </>
  );
}

For Next.js with next/head (Pages Router):

tsx

import Head from 'next/head';

export default function Page() {
  const jsonLd = {/* generated schema */};

  return (
    <>
      <Head>
        <script
          type="application/ld+json"
          dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
        />
      </Head>
      {/* page content */}
    </>
  );
}

For plain HTML:

html

<head>
  <script type="application/ld+json">
  {/* generated schema */}
  </script>
</head>

Validation

After generating the markup, remind the user to validate using:

Google Rich Results Test: https://search.google.com/test/rich-results
Schema.org Validator: https://validator.schema.org/

Common Mistakes to Avoid

Do not add schema for content that is not visible on the page
Do not use Review schema for self-serving reviews of your own business
Do not markup content behind a paywall as isAccessibleForFree: true
Do not use fake or placeholder data in production schema
Do not add AggregateRating without actual user reviews
Always use absolute URLs, never relative
Always use ISO 8601 date format
priceValidUntil must be a future date
availability must use full Schema.org URL (e.g., https://schema.org/InStock)
Image URLs must be crawlable and indexable

Files

Just SKILL.md in skills/schema-markup of OpenClaudia/openclaudia-skills.

Open the folder on GitHubat commit 28bf209

Compare with similar skills

Schema Markup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Schema Markup compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Schema Markup this skillOpenClaudia/openclaudia-skills	713	—	~4k	Automated safety check: Pass	MIT	21 days ago
SEO GeoReScienceLab/opc-skills	1.8k	4 repos	~2.1k	Automated safety check: Pass	Apache-2.0	today
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude	11k	—	~2.8k	Automated safety check: Notes	MIT	today
SEO Optimizerailabs-393/ai-labs-claude-skills	454	1 repos	~3.2k	Automated safety check: Pass	MIT	11 mo ago
Portaljs Add Dcatdatopian/portaljs	2.4k	1 repos	~1.8k	Automated safety check: Pass	MIT	yesterday
Schema Markupfreekmurze/dotfiles	1k	15 repos	~1.2k	Automated safety check: Pass	None	today

Similar skills

SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
1.8k GitHub starsUsed in 4 repos~2.1k tokens
Marketing & SEOAuto-check passed
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
11k GitHub stars~2.8k tokensUpdated today
Marketing & SEOAuto-check: notes
SEO Optimizer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
454 GitHub starsUsed in 1 repo~3.2k tokens
Marketing & SEOAuto-check passed
Portaljs Add Dcat
datopian/portaljs
Make a PortalJS portal harvestable by national/EU/US open-data portals — emit standards-compliant DCAT catalog feeds (DCAT 2/3, DCAT-AP, DCAT-US, national profiles) in JSON-LD, Turtle, and RDF/XML…
2.4k GitHub starsUsed in 1 repo~1.8k tokens
Marketing & SEOAuto-check passed
Schema Markup
freekmurze/dotfiles
When the user wants to add, fix, or optimize schema markup and structured data on their site.
1k GitHub starsUsed in 15 repos~1.2k tokens
Marketing & SEOAuto-check passed
Geo
liangdabiao/GEO-Content-Optimizer-Skill
完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料，做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产（llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。
205 GitHub starsUsed in 1 repo~2.3k tokens
Marketing & SEOAuto-check: notes

More from OpenClaudia/openclaudia-skills

All 74 skills in this repo

Competitor Traffic Report
OpenClaudia/openclaudia-skills
Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…
713 GitHub stars~1.2k tokensUpdated 21 days ago
Auto-check passed
Geo Difficulty
OpenClaudia/openclaudia-skills
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
713 GitHub stars~694 tokensUpdated 21 days ago
Auto-check passed
Gsc Portfolio Audit
OpenClaudia/openclaudia-skills
Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…
713 GitHub stars~1k tokensUpdated 21 days ago
Auto-check passed
Similarweb Traffic
OpenClaudia/openclaudia-skills
Fetch website traffic estimates (monthly visits, traffic sources, top countries, keywords, engagement, ranks) for any domain from SimilarWeb.
713 GitHub stars~882 tokensUpdated 21 days ago
Auto-check passed
Ahrefs Python
OpenClaudia/openclaudia-skills
Manages Ahrefs API usage in Python using ahrefs-python library.
713 GitHub stars~1.9k tokensUpdated 21 days ago
Auto-check passed
Ab Test Setup
OpenClaudia/openclaudia-skills
Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.
713 GitHub stars~1.7k tokensUpdated 21 days ago
Auto-check passed

Questions about Schema Markup

What does Schema Markup do?

Generate Schema.org structured data (JSON-LD) for any page type. Schema Markup is an agent skill from OpenClaudia/openclaudia-skills.org structured data (JSON-LD) for any page type.

When should I use Schema Markup?

Schema Markup fits situations like: the user says schema markup; structured data; breadcrumb schema; organization schema.

How do I install Schema Markup in Claude Code?

Run `npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a claude-code`. Or copy the skill folder (skills/schema-markup in OpenClaudia/openclaudia-skills) into .claude/skills/schema-markup in your project. Claude Code loads it when a task matches its description.

How do I install Schema Markup in Codex?

Run `npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a codex`. Or copy the skill folder (skills/schema-markup in OpenClaudia/openclaudia-skills) into .agents/skills/schema-markup in your project. Codex loads it when a task matches its description.

Can I use Schema Markup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenClaudia/openclaudia-skills --skill schema-markup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schema-markup, .gemini/skills/schema-markup, .github/skills/schema-markup and .opencode/skills/schema-markup in your project.

What does Schema Markup need to run?

SKILL.md names no scripts, command-line tools or credentials: Schema Markup is instructions for the agent only.

Does Schema Markup access the network?

SKILL.md names 8 domains. In commands or code: schema.org, twitter.com, linkedin.com, facebook.com, github.com and maps.google.com; the agent is likely to contact these when it follows the instructions. As links in the text: search.google.com and validator.schema.org. This is read from the text; nothing was executed.

Is Schema Markup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Schema Markup use?

Schema Markup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Schema Markup use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Schema Markup?

Skills that share tags, products or a category with Schema Markup: SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 454 stars) and Portaljs Add Dcat (datopian/portaljs, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Schema Markup?

OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 713 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.

Source: OpenClaudia/openclaudia-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Schema Markup

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Schema Markup Generator Skill

Supported Schema Types

1. Article / BlogPosting / NewsArticle

2. Product

3. FAQPage

4. HowTo

5. Organization

6. LocalBusiness

7. BreadcrumbList

8. Review / AggregateRating

Multi-Schema Pages

Generation Process

Implementation Instructions

Validation

Common Mistakes to Avoid

Files

Compare with similar skills

Similar skills

More from OpenClaudia/openclaudia-skills

Related

Questions about Schema Markup