SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
“Ship correct, complete metadata.”
Install Fixing Metadata
$ npx skills add kapishdima/soundcn --skill fixing-metadata -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kapishdima/soundcn fixing-metadata --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/kapishdima/soundcn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fixing-metadata .claude/skills/fixing-metadata && 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 "fixing-metadata" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadata into .claude/skills/fixing-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-metadata", 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/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadataType 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 kapishdima/soundcn --skill fixing-metadata -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kapishdima/soundcn fixing-metadata --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fixing-metadata .agents/skills/fixing-metadata && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fixing-metadata" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadata into .agents/skills/fixing-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-metadata", 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 kapishdima/soundcn --skill fixing-metadata -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kapishdima/soundcn fixing-metadata --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fixing-metadata .cursor/skills/fixing-metadata && 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 "fixing-metadata" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadata into .cursor/skills/fixing-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-metadata", 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/kapishdima/soundcn.git --path .agents/skills/fixing-metadata--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 kapishdima/soundcn --skill fixing-metadata -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kapishdima/soundcn fixing-metadata --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fixing-metadata .gemini/skills/fixing-metadata && 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 "fixing-metadata" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadata into .gemini/skills/fixing-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-metadata", 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 kapishdima/soundcn fixing-metadataInstalls 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 kapishdima/soundcn --skill fixing-metadata -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fixing-metadata .github/skills/fixing-metadata && 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 "fixing-metadata" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadata into .github/skills/fixing-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-metadata", 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 kapishdima/soundcn --skill fixing-metadata -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kapishdima/soundcn fixing-metadata --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fixing-metadata .opencode/skills/fixing-metadata && 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 "fixing-metadata" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-metadata into .opencode/skills/fixing-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-metadata", 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
fixing-metadata- GitHub stars
- 862
- Used in
- 1 other repo
- Token cost
- ~1k tokens
- SKILL.md length
- 551 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
- Works in 8 steps: correctness and duplication (critical) → title and description (high) → canonical and indexing (high) → …
- SKILL.md covers how to use, when to apply, rule categories by priority and quick reference, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
About this skill
Fixing Metadata is a skill in kapishdima/soundcn (862 stars). Its SKILL.md is about 1k tokens, and copies of it appear in 1 other owners' repositories. Licence: MIT.
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7cbfbb3. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Fixing Metadata loads about 1k tokens when it runs. Until then it costs about 12 tokens; SKILL.md has 551 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from kapishdima/soundcn at commit 7cbfbb3, republished under its MIT licence (© kapishdima). 551 words, ~1,033 tokens.
Download SKILL.mdSave it as
.claude/skills/fixing-metadata/SKILL.md (or your agent's skills folder).- name
- fixing-metadata
- description
- Ship correct, complete metadata.
fixing-metadata
Ship correct, complete metadata.
how to use
/fixing-metadataApply these constraints to any metadata work in this conversation./fixing-metadata <file>Review the file against all rules below and report:- violations (quote the exact line or snippet)
- why it matters (one short sentence)
- a concrete fix (code-level suggestion)
Do not introduce new frameworks or SEO libraries unless explicitly requested. Prefer minimal diffs.
when to apply
Reference these guidelines when:
- adding or changing page titles, descriptions, canonical, robots
- implementing Open Graph or Twitter card metadata
- setting favicons, app icons, manifest, theme-color
- building shared SEO components or layout metadata defaults
- adding structured data (JSON-LD)
- changing locale, alternate languages, or canonical routing
- shipping new pages, marketing pages, or shareable links
rule categories by priority
| priority | category | impact |
|---|---|---|
| 1 | correctness and duplication | critical |
| 2 | title and description | high |
| 3 | canonical and indexing | high |
| 4 | social cards | high |
| 5 | icons and manifest | medium |
| 6 | structured data | medium |
| 7 | locale and alternates | low-medium |
| 8 | tool boundaries | critical |
quick reference
1. correctness and duplication (critical)
- define metadata in one place per page, avoid competing systems
- do not emit duplicate title, description, canonical, or robots tags
- metadata must be deterministic, no random or unstable values
- escape and sanitize any user-generated or dynamic strings
- every page must have safe defaults for title and description
2. title and description (high)
- every page must have a title
- use a consistent title format across the site
- keep titles short and readable, avoid stuffing
- shareable or searchable pages should have a meta description
- descriptions must be plain text, no markdown or quote spam
3. canonical and indexing (high)
- canonical must point to the preferred URL for the page
- use noindex only for private, duplicate, or non-public pages
- robots meta must match actual access intent
- previews or staging pages should be noindex by default when possible
- paginated pages must have correct canonical behavior
Show full SKILL.md (242 more words)Show less
4. social cards (high)
- shareable pages must set Open Graph title, description, and image
- Open Graph and Twitter images must use absolute URLs
- prefer correct image dimensions and stable aspect ratios
- og:url must match the canonical URL
- use a sensible og:type, usually website or article
- set twitter:card appropriately, summary_large_image by default
5. icons and manifest (medium)
- include at least one favicon that works across browsers
- include apple-touch-icon when relevant
- manifest must be valid and referenced when used
- set theme-color intentionally to avoid mismatched UI chrome
- icon paths should be stable and cacheable
6. structured data (medium)
- do not add JSON-LD unless it clearly maps to real page content
- JSON-LD must be valid and reflect what is actually rendered
- do not invent ratings, reviews, prices, or organization details
- prefer one structured data block per page unless required
7. locale and alternates (low-medium)
- set the html lang attribute correctly
- set og:locale when localization exists
- add hreflang alternates only when pages truly exist
- localized pages must canonicalize correctly per locale
8. tool boundaries (critical)
- prefer minimal changes, do not refactor unrelated code
- do not migrate frameworks or SEO libraries unless requested
- follow the project’s existing metadata pattern (Next.js metadata API, react-helmet, manual head, etc.)
review guidance
- fix critical issues first (duplicates, canonical, indexing)
- ensure title, description, canonical, and og:url agree
- verify social cards on a real URL, not localhost
- prefer stable, boring metadata over clever or dynamic
- keep diffs minimal and scoped to metadata only
© kapishdima, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/fixing-metadata of kapishdima/soundcn.
Open the folder on GitHubat commit 7cbfbb3
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in kapishdima/soundcn, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Fixing Metadata 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 |
|---|---|---|---|---|---|---|
| Fixing Metadata this skillkapishdima/soundcn | 862 | 1 repos | ~1k | 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 | |
| Portaljs Add Dcatdatopian/portaljs | 2.4k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Schema Markupfreekmurze/dotfiles | 1k | 15 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.
Portaljs Add Dcat
datopian/portaljs
Make a PortalJS portal harvestable by national/EU/US open-data portals — emit standards-compliant DCAT catalog feeds (DCAT 2/3, DCAT-AP, DCAT-US, national profiles) in JSON-LD, Turtle, and RDF/XML…
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 kapishdima/soundcn
Generate Creative Ideas
kapishdima/soundcn
Creative problem-solving and ideation using SCAMPER, First Principles, Random Word, and AI-optimized techniques.
Fixing Motion Performance
kapishdima/soundcn
Fix animation performance issues.
Fixing Accessibility
kapishdima/soundcn
Fix accessibility issues.
Related
Categories
Questions about Fixing Metadata
How do I install Fixing Metadata in Claude Code?
Run `npx skills add kapishdima/soundcn --skill fixing-metadata -a claude-code`. Or copy the skill folder (.agents/skills/fixing-metadata in kapishdima/soundcn) into .claude/skills/fixing-metadata in your project. Claude Code loads it when a task matches its description.
How do I install Fixing Metadata in Codex?
Run `npx skills add kapishdima/soundcn --skill fixing-metadata -a codex`. Or copy the skill folder (.agents/skills/fixing-metadata in kapishdima/soundcn) into .agents/skills/fixing-metadata in your project. Codex loads it when a task matches its description.
Can I use Fixing Metadata 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 kapishdima/soundcn --skill fixing-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fixing-metadata, .gemini/skills/fixing-metadata, .github/skills/fixing-metadata and .opencode/skills/fixing-metadata in your project.
What does Fixing Metadata need to run?
SKILL.md names no scripts, command-line tools or credentials: Fixing Metadata is instructions for the agent only.
Does Fixing Metadata access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Fixing Metadata 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. Review the folder before installing.
What licence does Fixing Metadata use?
Fixing Metadata is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fixing Metadata use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fixing Metadata?
Skills that share tags, products or a category with Fixing Metadata: SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), Portaljs Add Dcat (datopian/portaljs, 2.4k 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 Fixing Metadata?
kapishdima (a GitHub user) maintains it in kapishdima/soundcn, which has 862 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on June 9, 2026.
Source: kapishdima/soundcn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.