codex2claude
Skill8 starsChanged 3 months agoMITView on GitHub
Synchronize Codex user skills into Claude Code. Auto-discovers the Claude environment and syncs from %USERPROFILE%\.codex\skills into the Claude skills folder. Supports full sync and single-skill sync. Excludes Codex built-in .system and accepts both skill.md and SKILL.md.
In this repository32 other files it gives its agents.
- ai-genSkill
- any2mdSkill
- assignment-wordSkill
- cheatsheatSkill
- claude2antiSkill
- claude2codexSkill
- fincomp-deckSkill
- github-trendingSkill
- git-pushSkill
- html2mdSkill
- html2pdfSkill
- html2texSkill
- html-slidesSkill
- img-readerSkill
- latex-beamerSkill
- markitdownSkill
- md2docxSkill
- md2texSkill
- mergeSkill
- notesSkill
- paper-html-onepageSkill
- paper-reproSkill
- pdf2wordSkill
- pdf-readerSkill
- posterSkill
- repo-docsSkill
- repo-docs-zhSkill
- resume-builderSkill
- web-search-fallbackSkill
- word2htmlSkill
- word2mdSkill
- word2pdfSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Default target fallback: %USERPROFILE%\.claude\skills
- Very specific: line 17
Default behavior is to sync user/custom Codex skills only.
- Distinctive: line 23
Use this skill when the user asks to:
- Distinctive: line 26
update Claude skills from Codex
- Very specific: line 87
Do not copy %USERPROFILE%\.codex\skills\.system
- Very specific: line 89
Treat %USERPROFILE%\.codex\skills as the source of truth for Codex user skills
- Distinctive: line 90
If a skill exists as a junction/link, copy the real target contents
- Very specific: line 92
Prefer writing SKILL.md in Claude targets
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Codex to Claude (codex2claude)
Synchronize user-created Codex skills into Claude Code.
Scope
- Source:
%USERPROFILE%\.codex\skills - Exclude from source:
%USERPROFILE%\.codex\skills\.system - Target: Claude user skills folder, auto-discovered from the local Claude environment
- Default target fallback:
%USERPROFILE%\.claude\skills
Default behavior is to sync user/custom Codex skills only. Do not copy Codex built-in .system into Claude.
The sync logic should treat both SKILL.md and skill.md as valid skill entry files. When copying to Claude, normalize to SKILL.md so skill discovery is more reliable across environments.
When To Use
Use this skill when the user asks to:
- sync Codex skills to Claude
- update Claude skills from Codex
- replace a Claude skill with the Codex version
- copy one specific skill from Codex to Claude
Modes
Full Sync
For requests like:
- "sync all Codex skills to Claude"
- "update Claude skills from Codex"
Run:
powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>\scripts\sync-skills.ps1" -Mode fullBehavior:
- Creates a backup of existing Claude user skills
- Removes all Claude target skills
- Copies all Codex user skills except
.system - Resolves junction/source links by copying real contents
- Normalizes
skill.mdtoSKILL.mdwhen needed - Verifies sync result before cleaning up backup
Single Skill Sync
For requests like:
- "sync github-trending to Claude"
- "update md2tex skill to Claude"
Run:
powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>\scripts\sync-skills.ps1" -Mode single -SkillName github-trendingBehavior:
- Backs up the current Claude copy of that skill if it exists
- Replaces only that one target skill
- Normalizes
skill.mdtoSKILL.mdwhen needed - Verifies sync result before cleaning up backup
Output Handling
The script prints a JSON summary. Report to the user:
- mode used
- source and target paths
- backup path
- synced skills
- skipped items
- any errors
Notes
- Do not copy
%USERPROFILE%\.codex\skills\.system - First try to detect Claude via
where claude, then use the matching user Claude data directory - Treat
%USERPROFILE%\.codex\skillsas the source of truth for Codex user skills - If a skill exists as a junction/link, copy the real target contents
skill.mdandSKILL.mdshould both be accepted as source files- Prefer writing
SKILL.mdin Claude targets
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.