mverab/egeoagents

schema-generator

Generate JSON-LD schema markup for pages and content types with an implementation checklist. Use when users ask for schema, structured data, rich snippets, or markup.

First seen Feb 8, 2026

Installation

$ npx skills add mverab/egeoagents --skill schema-generator

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mverab/egeoagents.

npx skills add mverab/egeoagents

Browse all from mverab/egeoagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 175
License LICENSE
Default branch main
Open issues 4
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,763 B
  • docs SUMMARY.md 190 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 60 installs

SKILL.md

Schema Generator Skill

When generating schema markup:

Schema Type Selection

Content Type Primary Schema Additional Types
SaaS Product SoftwareApplication Offer, AggregateRating
Physical Product Product Offer, Brand, Review
Service Service Provider, AreaServed
Article Article Author, Organization
How-To HowTo Step, Tool
FAQ FAQPage Question, Answer
About Page Organization ContactPoint, Address
Person/Team Person Organization
Event Event Location, Offer
Course Course Organization

Output Format

┌─────────────────────────────────────────────────────────────┐
│  🏗️ SCHEMA MARKUP GENERATED                                 │
├─────────────────────────────────────────────────────────────┤
│  Type: [Schema Type]                                        │
│  Validation: ✓ Valid JSON-LD                                │
└─────────────────────────────────────────────────────────────┘

## JSON-LD (copy to <head>)

<script type="application/ld+json"> { "@context": "https://schema.org";, "@type": "SoftwareApplication", "name": "Product Name", "description": "GEO-optimized description", "applicationCategory": "BusinessApplication", "operatingSystem": "Web", "offers": { "@type": "Offer", "price": "99", "priceCurrency": "USD" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "[FILL: rating]", "reviewCount": "[FILL: review count]" } } </script>


## Implementation Checklist

- [ ] Add JSON-LD to page `<head>` section
- [ ] Fill in `[FILL: ...]` placeholders with real data
- [ ] Test with Google Rich Results Test
- [ ] Verify in Google Search Console

Common Templates

SaaS/Software

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "",
  "description": "",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web",
  "offers": {
    "@type": "Offer",
    "price": "",
    "priceCurrency": "USD",
    "priceValidUntil": ""
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "",
    "reviewCount": ""
  },
  "author": {
    "@type": "Organization",
    "name": ""
  }
}

B2B Service

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "",
  "description": "",
  "serviceType": "",
  "provider": {
    "@type": "Organization",
    "name": "",
    "url": ""
  },
  "areaServed": {
    "@type": "Country",
    "name": ""
  },
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Services",
    "itemListElement": []
  }
}

FAQ Page

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Question text?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Answer text."
      }
    }
  ]
}

Rules

  • Always output valid JSON-LD
  • Mark fields needing human input as [FILL: description]
  • Include implementation instructions
  • Suggest additional schema types when relevant