claude2codex
Skill8 starsChanged 3 months agoMITView on GitHub
Synchronize Claude Code user skills into Codex. Auto-discovers the Claude environment and syncs from the Claude skills folder into %USERPROFILE%\.codex\skills. Supports full sync and single-skill sync. Preserves Codex built-in .system skills and accepts both skill.md and SKILL.md.
In this repository32 other files it gives its agents.
- ai-genSkill
- any2mdSkill
- assignment-wordSkill
- cheatsheatSkill
- claude2antiSkill
- codex2claudeSkill
- 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
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Default source fallback: %USERPROFILE%\.claude\skills
- Very specific: line 17
Default behavior is to sync user/custom Claude skills only.
- Distinctive: line 23
Use this skill when the user asks to:
- Distinctive: line 26
update Codex skills from Claude
- Very specific: line 87
Do not touch %USERPROFILE%\.codex\skills\.system
- Distinctive: line 89
Treat the discovered Claude skills directory as the source of truth for user skills
- Distinctive: line 90
If a skill exists in Claude as a junction/link, copy the real target contents into Codex
- Very specific: line 92
Prefer writing SKILL.md in Codex targets
- Distinctive: line 93
If the user asks whether Anthropic built-in skills should be included, answer: no by default
≈ “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
Claude to Codex (claude2codex)
Synchronize user-created Claude Code skills into Codex.
Scope
- Source: Claude user skills folder, auto-discovered from the local Claude environment
- Default source fallback:
%USERPROFILE%\.claude\skills - Target:
%USERPROFILE%\.codex\skills - Preserve:
%USERPROFILE%\.codex\skills\.system
Default behavior is to sync user/custom Claude skills only. You do not need to include Anthropic built-in system skills because they are not stored in this source folder and Codex already has its own .system.
The sync logic should treat both SKILL.md and skill.md as valid skill entry files. When copying to Codex, normalize to SKILL.md so skill discovery is more reliable across environments.
When To Use
Use this skill when the user asks to:
- sync Claude skills to Codex
- update Codex skills from Claude
- replace a Codex skill with the Claude version
- copy one specific skill from Claude to Codex
Modes
Full Sync
For requests like:
- "sync all Claude skills to Codex"
- "update Codex skills from Claude"
Run:
powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>\scripts\sync-skills.ps1" -Mode fullBehavior:
- Creates a backup of existing Codex user skills
- Removes all Codex skills except
.system - Copies all skills from Claude source folder into Codex
- 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 Codex"
- "update md2tex skill to Codex"
Run:
powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>\scripts\sync-skills.ps1" -Mode single -SkillName github-trendingBehavior:
- Backs up the current Codex 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 touch
%USERPROFILE%\.codex\skills\.system - First try to detect Claude via
where claude, then use the matching user Claude data directory - Treat the discovered Claude skills directory as the source of truth for user skills
- If a skill exists in Claude as a junction/link, copy the real target contents into Codex
skill.mdandSKILL.mdshould both be accepted as source files- Prefer writing
SKILL.mdin Codex targets - If the user asks whether Anthropic built-in skills should be included, answer: no by default
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.