Sharing skills between Codex and Claude Code? Claude ignores .agents/skills, so symlink each skill into .claude/skills

#What changed

Nothing broke, but a common setup trips people up. @DannielDevOps reported on X that three skills dropped into .agents/skills worked in Codex, yet Claude Code acted as if they weren't there until the same paths were also listed in CLAUDE.md. @NyxBetween replied that this is expected behavior (source).

We checked both sets of docs. Codex's skills guide says Codex scans .agents/skills in every directory from where you launch it up to the repo root, plus $HOME/.agents/skills for personal skills. Claude Code's skills guide lists only .claude/skills (project) and ~/.claude/skills (personal). Both tools follow the open Agent Skills format, so the same SKILL.md works in each. They just look in different folders.

#Who is affected

Anyone keeping one set of skills for a team that uses both Codex and Claude Code. If your skills live only in .agents/skills, Claude Code won't list them in /skills, won't match them automatically, and can't run them by name.

#What to do now

1. Keep the real skill folders in .agents/skills, since that is the path Codex and several other tools share.
2. Symlink each one into Claude's folder, for example mkdir -p .claude/skills && ln -s ../../.agents/skills/deploy .claude/skills/deploy. Claude Code's docs say a skill entry in the personal or project location can be a symlink to a folder elsewhere, and Codex's docs say it follows symlinked skill folders too.
3. Do the same for personal skills: link folders from ~/.agents/skills into ~/.claude/skills.
4. Check the result with /skills in Claude Code and /skills or $ in Codex. Claude Code picks up changes in an existing .claude/skills folder without a restart; if you just created that folder, run /reload-skills.
5. Listing skill paths in CLAUDE.md also works as a stopgap, but that puts the text in context every turn instead of loading each skill only when it's used.

#What is not confirmed

Whether Claude Code will add .agents/skills to its search path later. @NyxBetween's reply says it's being tracked, but we found no announcement or date. Symlinks inside a repo need care on Windows checkouts where Git's symlink support is off.