SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
A skill your agent uses when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't…
Install Schema
$ npx skills add fcakyon/claude-codex-settings --skill schema -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fcakyon/claude-codex-settings schema --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/seo-skills/skills/schema .claude/skills/schema && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "schema" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schema into .claude/skills/schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schemaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fcakyon/claude-codex-settings --skill schema -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fcakyon/claude-codex-settings schema --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/seo-skills/skills/schema .agents/skills/schema && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "schema" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schema into .agents/skills/schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fcakyon/claude-codex-settings --skill schema -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fcakyon/claude-codex-settings schema --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/seo-skills/skills/schema .cursor/skills/schema && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "schema" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schema into .cursor/skills/schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fcakyon/claude-codex-settings.git --path plugins/seo-skills/skills/schema--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fcakyon/claude-codex-settings --skill schema -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fcakyon/claude-codex-settings schema --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/seo-skills/skills/schema .gemini/skills/schema && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "schema" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schema into .gemini/skills/schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fcakyon/claude-codex-settings schemaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fcakyon/claude-codex-settings --skill schema -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/seo-skills/skills/schema .github/skills/schema && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "schema" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schema into .github/skills/schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fcakyon/claude-codex-settings --skill schema -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fcakyon/claude-codex-settings schema --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/seo-skills/skills/schema .opencode/skills/schema && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "schema" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/seo-skills/skills/schema into .opencode/skills/schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "schema", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
schema- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 621 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't…
- Reviewing structured data: JSON-LD for articles
- SKILL.md covers Choosing the type, Reviewing existing markup, Handing it over and Sources
- Runs JavaScript scripts from its folder; calls node
- Local businesses
What it does
Schema is an agent skill from fcakyon/claude-codex-settings. Use when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't earn a rich result.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/required-properties.json` and `references/schema-examples.md`).
It sits in Marketing & SEO, covering Schema markup. The repository describes itself as: Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support. The licence is MIT.
When your agent uses it
- Reviewing structured data: JSON-LD for articles
- Local businesses
- What to do when markup doesnt earn a rich result
Example prompts
- “/schema”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit a035b4e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.google.comsearch.google.comvalidator.schema.orgschema.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Schema loads about 1.2k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 621 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from fcakyon/claude-codex-settings at commit a035b4e, republished under its MIT licence (© fcakyon). 621 words, ~1,162 tokens.
Download SKILL.mdSave it as
.claude/skills/schema/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- schema
- description
- Use when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't earn a rich result.
- license
- MIT
Schema markup
Structured data tells a search engine what a page is rather than making it rank. Done right it earns a richer result and makes the page easier for an engine to summarize. Done wrong it earns a manual action.
Four rules govern everything below:
- Mark up only what the page visibly shows. Schema describing content a reader can't see is a spam signal, and it's the single most common reason markup gets penalized rather than ignored.
- Use JSON-LD, in a
<script type="application/ld+json">in the head or at the end of the body. Google recommends it, and it's the only format you can add without touching the page's markup. - Only claim types and properties the engine actually supports for a rich result. Valid schema.org markup with no supported result does nothing for search, which is fine, but don't promise a rich result it can't produce.
- Validate before it ships, then watch Search Console. Markup that validates can still be wrong about the page.
Choosing the type
| Type | Use on | Required |
|---|---|---|
| Organization | Homepage, about page | name, url |
| WebSite | Homepage, to declare a site search | name, url |
| Article, BlogPosting | Posts and news | headline, image, datePublished, author |
| Product | Product pages | name, image, offers |
| SoftwareApplication | App and SaaS pages | name, offers |
| FAQPage | A page with real questions and answers | mainEntity |
| HowTo | Step-by-step instructions | name, step |
| BreadcrumbList | Any page with breadcrumbs | itemListElement |
| LocalBusiness | A location page | name, address |
| Event | Events and webinars | name, startDate, location |
references/schema-examples.md has a complete, valid block for each of these plus a combined @graph and a Next.js pattern. references/required-properties.json is the same table in the form the bundled validator reads, so adding a type means editing both.
When a page needs several types, prefer one @graph array over several separate script tags: entities can then reference each other by @id instead of repeating themselves.
Show full SKILL.md (316 more words)Show less
Reviewing existing markup
A fetch of the page shows only server-rendered JSON-LD. CMS SEO plugins commonly inject it client side, so absence in fetched HTML is not absence on the page. Report what the server HTML contained, then send them to the Rich Results Test, which renders JavaScript.
When markup exists but earns nothing, check in this order: a required property missing, a value in the wrong shape (dates must be ISO 8601, URLs absolute, enumerations exact), the type having no rich result to earn, or the markup describing something the page doesn't show.
From this skill directory, run node scripts/validate_schema.mjs <jsonld-file> on any block before you hand it over. It parses the JSON, checks each type against the required properties in references/required-properties.json, and catches the two value shapes that fail most often: a date that isn't ISO 8601 and a relative URL. It's mechanical, so a clean result means the syntax is right and nothing more.
Then point the user at the Rich Results Test at https://search.google.com/test/rich-results for eligibility, and the schema.org validator at https://validator.schema.org/ for correctness against the vocabulary. Those answer different questions from each other and from the tool, so a block can pass one and fail another. None of the three can tell you whether the markup describes what the page actually shows, which is the accuracy rule above and still yours to check.
Handing it over
Give the complete block, ready to paste, with the page's real values filled in rather than placeholders. Say where it goes, name any property you had to leave out and why, and note which rich result it makes the page eligible for, with eligible being the honest word. Google decides whether to show one.
Sources
- Google Search Central, Intro to how structured data works: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
- Google Search Central, Structured data general guidelines: https://developers.google.com/search/docs/appearance/structured-data/sd-policies
- Google Search Central, Search gallery of supported result types: https://developers.google.com/search/docs/appearance/structured-data/search-gallery
- schema.org: https://schema.org/
© fcakyon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in plugins/seo-skills/skills/schema of fcakyon/claude-codex-settings.
- SKILL.md
- references/required-properties.json
- references/schema-examples.md
- scripts/validate_schema.mjs
Open the folder on GitHubat commit a035b4e
Compare with similar skills
Schema next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Schema this skillfcakyon/claude-codex-settings | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | MIT | |
| SEO Audit with Search Consolenowork-studio/notfair-plugin | 3.9k | 1 repos | ~15k | Automated safety check: Warn | MIT | |
| Schema Markupfreekmurze/dotfiles | 1k | 14 repos | ~1.2k | Automated safety check: Pass | None | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 454 | 1 repos | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
SEO Audit with Search Console
nowork-studio/notfair-plugin
Runs a full SEO audit that combines Google Search Console, URL Inspection, PageSpeed Insights and a technical crawl, then ranks quick wins and a 30-day plan.
Schema Markup
freekmurze/dotfiles
When the user wants to add, fix, or optimize schema markup and structured data on their site.
SEO Optimizer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
Geo
liangdabiao/GEO-Content-Optimizer-Skill
完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料， 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 （llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。
More from fcakyon/claude-codex-settings
All 43 skills in this repoSlides
fcakyon/claude-codex-settings
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities.
Openobserve API
fcakyon/claude-codex-settings
This skill should be used when user asks to "query OpenObserve", "create OpenObserve dashboard", "edit OpenObserve panel", "fetch OpenObserve logs", "run OpenObserve search", "list OpenObserve…
Supabase JS
fcakyon/claude-codex-settings
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the…
Yolo Training
fcakyon/claude-codex-settings
This skill should be used when user asks to "improve my mAP", "why is my model overfitting", "my training is diverging", "read my results.csv", "interpret my training curves", "my AP50 is good but…
Dokploy Deploy
fcakyon/claude-codex-settings
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure…
Openship Config
fcakyon/claude-codex-settings
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.
Related
Categories
Questions about Schema
What does Schema do?
A skill your agent uses when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't…. Schema is an agent skill from fcakyon/claude-codex-settings. Use when adding, fixing, or reviewing structured data: JSON-LD for articles, products, FAQs, breadcrumbs, organizations, and local businesses, and what to do when markup doesn't earn a rich result.
When should I use Schema?
Schema fits situations like: reviewing structured data: JSON-LD for articles; local businesses; what to do when markup doesnt earn a rich result.
How do I install Schema in Claude Code?
Run `npx skills add fcakyon/claude-codex-settings --skill schema -a claude-code`. Or copy the skill folder (plugins/seo-skills/skills/schema in fcakyon/claude-codex-settings) into .claude/skills/schema in your project. Claude Code loads it when a task matches its description.
How do I install Schema in Codex?
Run `npx skills add fcakyon/claude-codex-settings --skill schema -a codex`. Or copy the skill folder (plugins/seo-skills/skills/schema in fcakyon/claude-codex-settings) into .agents/skills/schema in your project. Codex loads it when a task matches its description.
Can I use Schema in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fcakyon/claude-codex-settings --skill schema -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schema, .gemini/skills/schema, .github/skills/schema and .opencode/skills/schema in your project.
What does Schema need to run?
Going by SKILL.md and its folder, Schema needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.
Does Schema access the network?
SKILL.md names 4 domains. As links in the text: developers.google.com, search.google.com, validator.schema.org and schema.org. This is read from the text; nothing was executed.
Is Schema safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Schema use?
Schema is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Schema use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.
What are the alternatives to Schema?
Skills that share tags, products or a category with Schema: SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), SEO Audit with Search Console (nowork-studio/notfair-plugin, 3.9k stars) and Schema Markup (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Schema?
fcakyon (a GitHub user) maintains it in fcakyon/claude-codex-settings, which has 1,163 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 6, 2026.
Source: fcakyon/claude-codex-settings on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.