sync-agent-skills
Skill7 starsChanged 5 months agoMITView on GitHub
Maintain repository agent skills across Codex and Claude. Use when adding, removing, renaming, or editing skills under `.agents/skills`, when Claude cannot see repository skills, when `.claude/skills` symlinks need to be generated or checked, or when updating the skill loading bridge between `.agents/skills` and tool-specific skill directories.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- JeffreyFerreiras/ai-skillstheir own version, first seen Sep 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- JeffreyFerreiras/ai-skills★ 1same 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- release-publishSkill
- release-tagSkill
- release-versionSkill
- self-checkSkill
- submit-prSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use .agents/skills as the only maintained source for repository skills.
- Very specific: line 12
Read .agents/skills/README.md to confirm the current loading policy.
- Very specific: line 13
Put durable repository rules in .agents/rules/.
- Distinctive: line 15
After adding, removing, renaming, or editing repository skills, run:
- Distinctive: line 21
Verify the bridge with:
- Distinctive: line 28
If package scripts or the sync script changed, also run:
- Very specific: line 36
Do not copy skill contents into .claude/skills.
- Very specific: line 37
Do not maintain .claude/skills by hand except to inspect or remove broken local state after the sync script reports a conflict.
- Very specific: line 39
Treat .agents/skills as tracked repository source.
- Very specific: line 40
Treat .claude/skills as generated local symlinks for Claude.
- Distinctive: line 41
Do not overwrite existing non-symlink Claude skills.
- Very specific: line 42
Only remove stale Claude symlinks that point back into this repository's .agents/skills.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sync Agent Skills
Use .agents/skills as the only maintained source for repository skills.
Workflow
- Read
.agents/skills/README.mdto confirm the current loading policy. - Put durable repository rules in
.agents/rules/; put reusable workflows in.agents/skills/<skill-name>/SKILL.md. After adding, removing, renaming, or editing repository skills, run:
pnpm skills:syncVerify the bridge with:
pnpm skills:check pnpm vitest run scripts/tests/sync-agent-skills.test.tsIf package scripts or the sync script changed, also run:
pnpm harness:check:release
Safety Rules
- Do not copy skill contents into
.claude/skills. - Do not maintain
.claude/skillsby hand except to inspect or remove broken local state after the sync script reports a conflict. - Treat
.agents/skillsas tracked repository source. - Treat
.claude/skillsas generated local symlinks for Claude. - Do not overwrite existing non-symlink Claude skills.
- Only remove stale Claude symlinks that point back into this repository's
.agents/skills.
Expected Bridge
pnpm skills:sync creates links shaped like:
.claude/skills/<skill-name> -> ../../.agents/skills/<skill-name>pnpm skills:check should report:
Agent skills are in sync.Restart Claude or Codex sessions after skill changes if the tool does not pick up the updated skill list.
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.

