agentleFS
akii-technologies-ltdakii-technologies-ltd/akii-seo-ai-search-optimizer/skills/schema-markup/SKILL.md

schema-markup

Skill78 starsChanged 5 months agoMITView on GitHub

Fast-path schema generator — produce, audit, and validate JSON-LD structured data for a single page or file in one turn. This is the default for any schema question. Use when the user asks to "generate schema", "add JSON-LD", "structured data", "schema markup", "rich snippets", "add schema.org", "LocalBusiness schema", "FAQ schema", "Product schema", "Article schema", "HowTo schema", "Organization schema", "BreadcrumbList schema", "audit schema", "fix schema errors", "Recipe schema". **Do not invoke the `schema-generator` agent unless** the user explicitly says "bulk schema", "across my site", "all pages", "every page", or names a path containing 3+ pages to fix. The agent is the autonomous multi-file path that writes into source; this skill is the one-page fast path that proposes JSON-LD inline.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat schema as serving two real purposes:

    line 13
  2. Distinctive:

    Never tell the user schema is *required* for AI visibility — Google's own guidance says it isn't.

    line 17
  3. Very specific:

    No placeholders (example.com, TODO, lorem)

    line 60
  4. Distinctive:

    Never mark up content not actually on the page (structured-data spam violation).

    line 90
  5. Distinctive:

    Write only on explicit user approval.

    line 91

“Common” is measured: kept by at least 6 in 10 of the 54 edited versions of this file we could read. “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 Schema.org JSON-LD specialist powered by Akii. Produce markup that maximizes both rich-snippet eligibility AND answer-engine extractability.

Scoping — what schema actually does

Google's AI Optimization Guide is explicit: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add. However, it's a good idea to continue using it as part of your overall SEO strategy, as it helps with being eligible for rich results."

Treat schema as serving two real purposes:

  1. Rich-snippet eligibility on Google Search (review stars, FAQ accordions, recipe cards, breadcrumbs) — measurable SERP value.
  2. Cleaner extraction by non-Google AI engines (ChatGPT, Claude, Perplexity, Copilot) that DO consume structured data more directly than Google AI surfaces.

Never tell the user schema is required for AI visibility — Google's own guidance says it isn't. Recommend schema where rich results or non-Google extraction is the actual win.

Supported types

  • Article / NewsArticle / BlogPosting
  • Product + Offer + AggregateRating + Review
  • FAQPage
  • HowTo
  • Organization (with sameAs linking Wikipedia, LinkedIn, X, GitHub, Crunchbase)
  • LocalBusiness + granular subtypes: FinancialService, MedicalBusiness, EntertainmentBusiness, Restaurant, Store, LegalService, ProfessionalService
  • BreadcrumbList
  • WebSite + SearchAction
  • VideoObject
  • Event
  • Course
  • SoftwareApplication
  • Recipe

Best-practice properties (always include where applicable)

  • sameAs array (Wikipedia, social, directory profiles) — anchors the entity to the wider web for AI engine cross-corroboration
  • mainEntityOfPage + canonical URL
  • image (≥1200px, absolute URL)
  • datePublished + dateModified (ISO 8601)
  • author + publisher with their own @id

LocalBusiness specifics (Gemini local weight = 38%)

  • name, full address (PostalAddress)
  • telephone (E.164)
  • geo (lat + long)
  • openingHoursSpecification
  • currenciesAccepted, priceRange
  • actionableFeedbackPolicy
  • paymentAccepted
  • areaServed
  • hasMap

Steps

  1. Resolve target (URL → WebFetch; file → Read).
  2. Extract: title, primary entity, body, key facts, dates, authors, images, FAQs.
  3. Build JSON-LD per requested type.
  4. Validate:
    • JSON syntax
    • Required + recommended Schema.org fields
    • HTTPS absolute URLs
    • No placeholders (example.com, TODO, lorem)
  5. Present the block.
  6. Offer (don't auto-do) to write into the source:
    • HTML → <script type="application/ld+json"> in <head>
    • MDX/MD → block at file head

Output

## <Type> schema for <target>

```json
{
  "@context": "https://schema.org",
  ...
}
```

### Why these fields
- `sameAs`: cross-corroboration for Claude + Gemini
- `actionableFeedbackPolicy`: Google E-E-A-T trust signal
- ...

### Validation
- ✅ All required + recommended present
- ⚠️ `aggregateRating` placeholder — fill once reviews exist

Rules

  • Never fabricate ratings, addresses, prices, dates.
  • Never mark up content not actually on the page (structured-data spam violation).
  • Write only on explicit user approval.

Schema markup powered by Akii. Explore Akii Technologies and the products we build: https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=schema-markup&utm_campaign=akii_plugin_v1

Download now (ZIP)

  • Other versions55 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 55

    1. TheCraigHewitt/seomachine★ 7.5ksame name
    2. LeoYeAI/openclaw-marketing-skills★ 1ksame name
    3. OpenClaudia/openclaudia-skills★ 724same name
    4. mysticaltech/marketingskills★ 352same name
    5. boraoztunc/skills★ 337same name
    6. textura-agency/next16-claude-starter★ 141same name
    7. b1rdmania/ghostclaw★ 91same name
    8. robertbstillwell/marketing-skills★ 26same name
    9. ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same name
    10. wpgaurav/WordPress-skills★ 19same name

    45 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use internal-link-audit, product-marketing-context and 8 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • semrushSkill

      internal-link-audit

      Audit internal linking to find orphan pages, broken internal links, crawl-depth problems, and weak anchor distribution, then plan the hub-and-spoke structure that fixes them. Use when the user asks about internal links, orphan pages, site architecture, crawl depth, or how to pass authority to priority pages.

      Also in 3 projects that use this

    • xfstudioSkill

      product-marketing-context

      When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

      Also in 17 projects that use this

    • ukunal91appSkill

      revops

      When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

      Also in 13 projects that use this

    • alaraakcasizSkill

      technical-seo-audit

      Technical and on-page SEO audit of any website — a client site, your own site, a competitor, or a staging build before a CMS migration. Use this skill whenever the user asks for an SEO audit, technical SEO audit, on-page audit, site health check, crawl analysis, or the SEO section of a broader digital marketing audit. Also trigger for migration/replatform work ("are we losing pages", "build a redirect map", "compare old site vs new site", Webflow to Framer, WordPress to Shopify, any CMS to any CMS), and whenever the user uploads Screaming Frog exports (internal_all.csv, image_details.csv, All Inlinks), a GSC Pages export, or a sitemap and wants them analysed. Covers indexability, canonicals, crawl directives, headings, titles and metas, alt text, schema markup, page speed, robots.txt, llms.txt, internal linking, page-inventory diffing and redirect mapping.

      Also in 3 projects that use this

    • VercelSkill

      site-architecture

      Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.

      Also in 15 projects that use this

    • ukunal91appSkill

      churn-prevention

      When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

      Also in 13 projects that use this

    • +3 more from ukunal91app
  • In this repository11 other files it gives its agents.

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.