agentsclimarketplace

Schema org sprint

Skill sujanbhuiyan/Skills/skills/schema-org-sprint

A curated, installable marketplace of production-grade Agent Skills for Claude — research, SEO/GEO, finance, deliverables & engineering, indexed by topic, lifecycle & domain.

Install
npx -y skills add sujanbhuiyan/Skills --skill schema-org-sprint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audits a page or site and emits ready-to-paste Schema.org JSON-LD structured data plus a node-coverage checklist. Use when a page lacks structured data, when adding rich-result eligibility (Organization, LocalBusiness, Article, FAQ, Product, Breadcrumb), or when auditing which schema node types a site should have and whether each is present.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.2 KB, as published. Nobody here has run it

Schema.org Sprint

What this does

Turns page content into valid, ready-to-paste Schema.org JSON-LD. It identifies the page type, picks the correct node types, fills them from the actual page content, wires nodes together by @id, and emits <script type="application/ld+json"> blocks. It also produces a site-wide coverage checklist showing which node types the site should carry and whether each is present — the deliverable that turns a one-page fix into a structured-data sprint.

When to use it

  • A page has no structured data and you want rich-result / AI-citation eligibility.
  • Adding Organization, WebSite, LocalBusiness, Person, Service, Article, FAQPage, BreadcrumbList, or Product markup to a site.
  • Auditing a multi-page site for missing or malformed schema coverage.

How to use it

  1. Identify the page type (home, about, service, blog post, product, local business, contact). This drives which node types apply.
  2. Choose node types using references/node-guide.md — when to use each, required vs recommended properties, and how nodes link.
  3. Copy the matching skeleton(s) from assets/ and fill placeholders from the real page content (visible text, contact details, prices, authors, dates). Available templates: organization.json, website.json, localbusiness.json, person.json, service.json, article.json, faqpage.json, breadcrumblist.json, product.json.
  4. Wire nodes by @id (e.g. an Article.publisher references the Organization @id; a Service.provider references it too). See the "Linking nodes via @id" section of the node guide.
  5. Replace every placeholder. Never ship a value like https://example.com or PLACEHOLDER — Google and AI engines treat fabricated data as spam.
  6. Emit each block wrapped in <script type="application/ld+json"> … </script>, ready to paste into the page <head>. Multiple nodes can share one @graph.
  7. Produce a coverage checklist: list the node types the site should have site-wide and per template, mark each Present / Missing / Malformed, and note the fix. This is the audit artifact.
  8. Validate mentally against the required-properties table in the node guide; recommend the user run Google Rich Results Test + Schema Markup Validator before publishing.

Inputs

  • The page URL or its content (visible copy, headings, contact info, prices, author + publish date for articles, FAQ Q&A pairs).
  • The canonical site domain (for stable @id URIs and url fields).
  • Optional: the full page list, if producing a site-wide coverage checklist.

Output

  • One or more <script type="application/ld+json"> blocks with real values, nodes linked by @id, ready to paste into the page head.
  • A site-wide schema coverage checklist (node type × page, Present/Missing/Fix).

Notes & constraints

  • JSON-LD only (Google's preferred format) — do not emit Microdata or RDFa.
  • Only mark up content that is visible on the page; invisible/contradictory markup is a guidelines violation.
  • Use stable absolute @id URIs (e.g. https://site.com/#organization) so nodes can be referenced across pages.
  • Dates use ISO 8601 (2026-05-24); prices need both price and priceCurrency; images should be absolute URLs.
  • This skill builds markup; it does not deploy it. Validate with the Google Rich Results Test and the Schema.org validator before publishing.
  • Use forward-slash paths.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.