schema-org-sprint — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited schema-org-sprint (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact 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.
BreadcrumbList, or Product markup to a site.
business, contact). This drives which node types apply.
references/node-guide.md— when to use each, required vs recommended properties, and how nodes link.
assets/ and fill placeholders from thereal 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.
@id (e.g. an Article.publisher references theOrganization @id; a Service.provider references it too). See the "Linking nodes via @id" section of the node guide.
https://example.comor PLACEHOLDER — Google and AI engines treat fabricated data as spam.
<script type="application/ld+json"> … </script>,ready to paste into the page <head>. Multiple nodes can share one @graph.
site-wide and per template, mark each Present / Missing / Malformed, and note the fix. This is the audit artifact.
recommend the user run Google Rich Results Test + Schema Markup Validator before publishing.
author + publish date for articles, FAQ Q&A pairs).
@id URIs and url fields).<script type="application/ld+json"> blocks with real values,nodes linked by @id, ready to paste into the page head.
markup is a guidelines violation.
@id URIs (e.g. https://site.com/#organization) sonodes can be referenced across pages.
2026-05-24); prices need both price andpriceCurrency; images should be absolute URLs.
Results Test and the Schema.org validator before publishing.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.