Allow symlinked Skill folders/files

[ldorigo]

What feature would you like to see?

Different agents (i.e. claude code) have a different directory for skills. Following symlinks mean that one can define a single skill tree for all agents and simply link them to the proper locations. Currently I need to use a brittle mechanism that copies the full skill files. Symlinks are nice. Honor symlinks.

Additional information

No response

[JeongJuhyeon]

Wouldn't be ideal if like with custom instructions, it again takes a year of having to use dozens of links and copies before we settle on a skills version of AGENTS.md that every agent looks at instead of all having different folders and names. Hoping that some lessons were learnt there. Github Copilot for one just supports .claude/skills out of the box in addition to its own .github/skills.

[philipp-spiess]

Agree this would be a very good quality of life change. ~/.codx/AGENTS.md already follows symlinks so this feels more like an oversight.

[asonawalla]

I think a slightly better approach might be to allow users to define the skills tree in codex config. Symlinks are certainly better than syncing edits, but having the tools look in a central, configurable location sounds ideal.

[xxchan]

Or we hope this can get into the agentskills spec... agentskills/agentskills#15

[banagale]

This would be very much appreciated. It is something of a blocker, as .codex/ can live under version control and when dealing with worktrees we're talking about a lot of unwanted file copies.

[etraut-openai]

Working on it: #8801