ai-design-vault: Skill for Claude Code

.claude/skills/schema-markup/SKILL.md

schema-markup is a skill for Claude Code from textura-agency/ai-design-vault. It costs 81 tokens per session (727 once invoked), scanned A, original, Unlicense.

A workflow for adding JSON-LD structured data to web pages. JSON-LD is machine-readable information that describes things such as an organisation, article, product, or breadcrumb trail for search engines.

In plain words
What is it for?
Use it to build and render one shared entity graph, add page-appropriate types, connect related entities, source values from site and page data, and check required fields and URLs.
Why use it?
Scattered or conflicting structured-data blocks can describe the same site inconsistently, or claim information that the page does not show. A shared builder keeps the descriptions together and easier to validate.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is textura-agency/ai-design-vault's own configuration. It tells Claude Code how to work on ai-design-vault itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-design-vault configures →

Reuse

Borrowing it

Nothing to install: this file belongs to textura-agency/ai-design-vault. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/textura-agency/ai-design-vault/main/.claude/skills/schema-markup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/textura-agency/ai-design-vault

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for schema-markup

README.md
[![agentmods](https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/schema-markup/github.svg)](https://agentmods.dev/skills/textura-agency/ai-design-vault/schema-markup)
Your own site
<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/schema-markup"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/schema-markup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for schema-markup

Your own site · 80×15
<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/schema-markup"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/schema-markup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 727 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.00727
Opus 5.5 $0.00032 $0.00291
Sonnet 5.5 $0.00016 $0.00145
Haiku 4.5 $0.00008 $0.00073

Measured 23d ago against content hash ed675dcc8831, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

schema-markup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 23d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/schema-markup/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Structured data (JSON-LD)

Keep structured data in one typed builder module (e.g. <paths.source>/utils/seo/structured-data.*) that composes an entity graph, and render it once per page. Do not scatter inline <script type="application/ld+json"> tags through components — that is how a site ends up with three conflicting Organizations.

If no builder exists yet, create it; it is the first thing this skill installs.

Rules

  1. JSON-LD only — never microdata or RDFa (hard rule 10).
  2. Only describe what is on the page. Schema claiming content the page does not contain is spam, and search engines treat it that way.
  3. Reference, don't duplicate. Build the graph with @id references between entities so the Organization is defined once and linked from everywhere.
  4. Values come from the site config module and the page's own props — never hardcoded a second time.
  5. Validate: the JSON parses, required properties are present, URLs are absolute (they need the site URL variable set — see seo-audit).

Types worth adding, by page kind

Page Type Required-ish properties
Home Organization, WebSite name, url, logo, sameAs
Local business LocalBusiness address, geo, openingHours, telephone
Blog post Article / BlogPosting headline, image, datePublished, dateModified, author
Service page Service serviceType, provider, areaServed
Product Product + Offer name, image, description, price, availability
FAQ block FAQPage mainEntity[] of Question/acceptedAnswer
Any nested page BreadcrumbList itemListElement with position
Team page Person per member name, jobTitle, image, worksFor

FAQPage earns its place twice over: it is the format both featured snippets and AI answer engines extract most reliably. If the page has a real FAQ section, mark it up — but the questions must be visible on the page, not schema-only.

Pattern

Read the full file on GitHub · 59 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 23d ago First seen · 59 lines · 81 tokens per session scan A ed675dcc8831

Subscribe to this mod's changes

schema-markup is a skill published in the GitHub repository textura-agency/ai-design-vault (25 stars, last pushed 2mo ago), licensed Unlicense. It adds 81 tokens to every session and 727 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.

Related

schema-markup compared with skills from other repositories

schema-markup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
schema-markuptextura-agency/ai-design-vaultSkill252mo agoUnlicenseA81Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code