schema-markup
Skill4 starsChanged 11 days agoMITView on GitHub
Structured data and JSON-LD schema markup for search engines and AI answer surfaces, including validation and common markup mistakes.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
1
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
- Distinctive: line 13
Read CLAUDE.md before executing.
- Very specific: line 19
Do not edit this file directly.
“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.
Files
<!-- GENERATED by scripts/sync-agent-adapters from ai/AGENT_ROUTES.json. DO NOT EDIT. -->schema-markup skill adapter
Canonical skill: skills/schema-markup/SKILL.md. Read that file in full before acting, then follow it exactly.
This adapter exists so a runtime that discovers repository skills under .agents/skills/ or .claude/skills/ can reach a skill whose canonical copy lives in skills/. It owns no procedure. Do not restate, shorten, or improvise the canonical steps, and do not treat this summary as the skill.
Read CLAUDE.md before executing. It is the shared operating contract and it outranks this skill on precedence, voice, pricing policy, and what counts as a sanctioned write. The canonical skill wins on execution mechanics.
Vendored reference material, not this repository's doctrine. Provenance, licences, and the deliberate skip list live in skills/VENDORED.md. This repository's voice, pricing, and precedence rules override anything this file models, including the em-dash copy style several of these files demonstrate, which is banned in every artifact this repo produces. It carries no knowledge/ write licence and no send authority.
Maintenance
Do not edit this file directly. Change skills/schema-markup/SKILL.md for procedure or ai/AGENT_ROUTES.json for routing, then run scripts/sync-agent-adapters --write. scripts/repo-doctor blocks stale generated surfaces.
Other versions55 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 55
- TheCraigHewitt/seomachine★ 7.5ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- OpenClaudia/openclaudia-skills★ 724same name
- mysticaltech/marketingskills★ 352same name
- boraoztunc/skills★ 337same name
- textura-agency/next16-claude-starter★ 141same name
- b1rdmania/ghostclaw★ 91same name
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 78same name
- robertbstillwell/marketing-skills★ 26same name
- ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same 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 10 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.
semrushSkillinternal-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
xfstudioSkillproduct-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 18 projects that use this
ukunal91appSkillrevops
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 14 projects that use this
VercelSkillsite-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 16 projects that use this
ukunal91appSkillchurn-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 14 projects that use this
alaraakcasizSkilltechnical-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
- +3 more from ukunal91app
In this repository92 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- analytics-trackingSkill
- app-store-screenshotsSkill
- business-profile-creatorSkill
- call-debriefSkill
- copy-editingSkill
- copywritingSkill
- daily-logSkill
- decision-gauntletSkill
- deep-researchSkill
- hard-taskSkill
- harvestSkill
- invoice-creatorSkill
- landing-pageSkill
- make-interfaces-feel-betterSkill
- ogilvySkill
- onboardSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- proposal-creatorSkill
- prospect-briefSkill
- research-doctrineSkill
- run-coding-sessionSkill
- schema-markupSkill
- seo-auditSkill
- stop-slopSkill
- tailwind-v4Skill
- visual-style-presetsSkill
- web-design-guidelinesSkill
- analytics-trackingSkill
- app-store-screenshotsSkill
- business-profile-creatorSkill
- call-debriefSkill
- copy-editingSkill
- copywritingSkill
- daily-logSkill
- decision-gauntletSkill
- deep-researchSkill
- hard-taskSkill
- harvestSkill
- invoice-creatorSkill
- landing-pageSkill
- make-interfaces-feel-betterSkill
- ogilvySkill
- onboardSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- proposal-creatorSkill
- prospect-briefSkill
- research-doctrineSkill
- run-coding-sessionSkill
- seo-auditSkill
- stop-slopSkill
- tailwind-v4Skill
- The first 60 shown.
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
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.

