create-repo-skill
Skill4 starsChanged 12 days agoMITView on GitHub
Create or update a skill in this repository the right way — canonical home in .agents/skills, internal-vs-public marking, symlink mirroring into .claude/skills, and public docs registration for product skills. Use whenever adding a new skill, converting a workflow into a skill, or when .claude/skills and .agents/skills look out of sync.
2 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- every-app/open-seoword for word, first seen Oct 8, 2026
- madalinpopa/skillstheir own version, first seen Sep 14, 2026
Other versions2 projects use a version of this.
Word for word · 1
- every-app/open-seo★ 28k100% same
Edited · 0
None found.
Wrote their own version · 1
- madalinpopa/skills★ 0same name
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.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ai-prompt-researchSkill
- ai-visibility-auditSkill
- competitive-landscapeSkill
- competitor-analysisSkill
- deslopSkill
- evaluate-skillSkill
- keyword-clusteringSkill
- keyword-researchSkill
- link-prospectingSkill
- local-seoSkill
- merge-readySkill
- observability-triageSkill
- openseo-release-notesSkill
- openseo-review-web-contentSkill
- papercutsSkill
- review-briefSkill
- review-simplifySkill
- review-ui-statesSkill
- seo-auditSkill
- seo-coachSkill
- seo-project-setupSkill
- seo-reportSkill
- setup-openseoSkill
- simple-issue-descriptionSkill
- stageshowSkill
- test-auditSkill
- verify-local-mcpSkill
The file
Files
Create a repo skill
The layout (invariants)
.agents/skills/<kebab-name>/SKILL.mdis the only canonical home for every skill — public product skills (SEO workflows customers install) and internal repo skills (agent workflows likemerge-ready,papercuts, this one) alike. Users install from this tree vianpx skills add every-app/open-seo..claude/skills/contains only symlinks into.agents/skills/— one per skill that Claude Code agents working in this repo should auto-load. Never copy files:.agents/skills/is prettier-ignored (vendored skills are hash-pinned) while.claude/skills/is not, so a copy gets reformatted on the.claudeside and the trees drift — this happened to three skills before symlinks became the rule.prettier --check .does not descend into the symlinks, so a symlink stays byte-identical to its canonical source by construction.- Vendored skills (external origin) are hash-pinned in
skills-lock.json(created by theskillsCLI on first vendor). Never hand-edit a vendored skill's content; re-vendor with theskillsCLI so the lock hash stays valid. .agents/skills/**is part of the review control plane (seeAGENTS.md): changes require explicit maintainer review via CODEOWNERS. Make the change on a branch and call it out in the PR — never treat skill edits as incidental.
Creating a skill
mkdir .agents/skills/<kebab-name>and writeSKILL.mdwith frontmatter:--- name: <kebab-name> # must match the directory name description: <what it does + explicit "use when ..." triggers> metadata: internal: true # ONLY for internal repo skills — omit for product skills ---- Decide which kind it is:
Internal repo skill (agent/dev workflow): set
metadata.internal: true. Do NOT register it on any public surface. If repo agents should auto-load it, add the mirror symlink:ln -s ../../.agents/skills/<name> .claude/skills/<name>- Public product skill (a customer-facing SEO workflow): no
internalflag, usually no.claude/skillssymlink (repo agents don't need customer workflows). A public skill is auto-served to SAM, the live in-app agent — the marking is fail-open, so a missinginternal: trueships repo-dev instructions to end users. Give it the standard "Project context" preamble (copy a sibling likeseo-audit) with the skill's required sections, and register it everywhere users discover skills:src/server/features/sam/samSkills.test.ts— add the name to the pinned public roster (the test fails otherwise; that failure is the guard)web/content/docs/skills/<name>.mdx— docs page (mirror a sibling likecompetitor-analysis.mdx: what it does, when to use it, what you get back, how to get the best result)web/content/docs/skills/index.md— bullet in the right workflow sectionweb/content/docs/skills/meta.json— nav entrysrc/routes/_app/ai.tsx—SKILL_NAMES.agents/skills/seo-coach/SKILL.md— one line in the "What each workflow does" rosterplugins/openseo/skills/<name>— add the skill to theskillslist inscripts/sync-plugin-skills.mjs, then runpnpm sync-plugin-skills(this directory holds real copies, not symlinks — the Claude Code and Codex plugins bundle from here, and Codex's installer silently skips symlinked files, so a symlink would ship a skill-less plugin).pnpm ci:checkre-runs the sync and fails on drift, so a missed update here is caught, but the skill count and roster below are prose and aren't checked — update them by hand: bothplugins/openseo/*/plugin.jsondescriptionfields, the Codex manifest'sinterface.longDescription, and the skill lists inweb/content/docs/claude-code-plugin.mdandweb/content/docs/codex-plugin.md- Optional:
web/src/lib/feature-pages.tsandweb/content/docs/skills/setup.mdif it deserves marketing/setup placement
- If the skill references MCP tools, use exact tool names and keep them in sync with
src/server/mcp/server.ts— the tool names in skills are load-bearing for agents following them. For public skills also checksrc/server/features/sam/samChatTools.ts: SAM's toolset is a curated subset, and a skill step that names a tool SAM lacks dead-ends in the in-app agent. pnpm format:write(covers the docs pages;.agents/skillsitself is intentionally untouched), then commit. Skill prose followsopenseo-review-web-contentstandards when public.
Sync check (run when in doubt, and after any skill change)
for d in .claude/skills/*/; do n=$(basename "$d")
[ -L "${d%/}" ] || echo "DRIFT RISK — not a symlink: $n"
[ -e ".agents/skills/$n" ] || echo "BROKEN — no canonical source: $n"
doneAnything flagged: move the canonical content to .agents/skills/<name>/ (reconciling differences deliberately — diff both sides first, newest intent wins), delete the .claude copy, and replace it with the symlink.
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.

