IssueRaiser

Proposal: include a standard folder where agent skills should be

I highly appreciate that skills is becoming a standard that we can use across many different agent harnesses. To make it even smoother, I believe that agreeing on a standard name for the agent skills folder would benefit everyone. This would allow different harnesses to have a default folder to find skills without requiring each project to put them in a different folder and create symlinks that match the specific folder of each harness. Example: Claude is looking at `.claude/skills/` and Github Copilot is looking at `.github/skills/`. Edit: now we have Codex also looking at its own folder `.codex/skills/` My suggestion for the name would be `.agents/skills/`, but I don't really care much about the name as long as it's agreed upon and standardized. It could even be just `.skills/`. ## Adoption Please help to keep the lists below up to date. 😄 ### Ready * Amp: https://ampcode.com/manual#agent-skills * Augment Code (Auggie): https://docs.augmentcode.com/cli/skills#skill-file-structure * Goose: https://block.github.io/goose/docs/guides/context-engineering/using-skills/#skill-locations * Codex: https://github.com/openai/codex/pull/10317 and https://github.com/openai/codex/pull/10437 * VS Code: https://github.com/microsoft/vscode/pull/292414 * VTCode: https://github.com/vinhnx/VTCode/issues/600 * Pi: https://github.com/badlogic/pi-mono/issues/1211 (configurable) * Mistral Vibe: https://github.com/mistralai/mistral-vibe/blob/ec7f3b25eaf47c447f4005561ae2ff32545d3dff/CHANG

Posted by douglascamata on Dec 19, 2025, 2:18 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Software)

Proposal: include a standard folder where agent skills should be

douglascamataDec 19, 2025, 2:18 PM

I highly appreciate that skills is becoming a standard that we can use across many different agent harnesses. To make it even smoother, I believe that agreeing on a standard name for the agent skills folder would benefit everyone. This would allow different harnesses to have a default folder to find skills without requiring each project to put them in a different folder and create symlinks that match the specific folder of each harness. Example: Claude is looking at `.claude/skills/` and Github Copilot is looking at `.github/skills/`. Edit: now we have Codex also looking at its own folder `.codex/skills/` My suggestion for the name would be `.agents/skills/`, but I don't really care much about the name as long as it's agreed upon and standardized. It could even be just `.skills/`. ## Adoption Please help to keep the lists below up to date. 😄 ### Ready * Amp: https://ampcode.com/manual#agent-skills * Augment Code (Auggie): https://docs.augmentcode.com/cli/skills#skill-file-structure * Goose: https://block.github.io/goose/docs/guides/context-engineering/using-skills/#skill-locations * Codex: https://github.com/openai/codex/pull/10317 and https://github.com/openai/codex/pull/10437 * VS Code: https://github.com/microsoft/vscode/pull/292414 * VTCode: https://github.com/vinhnx/VTCode/issues/600 * Pi: https://github.com/badlogic/pi-mono/issues/1211 (configurable) * Mistral Vibe: https://github.com/mistralai/mistral-vibe/blob/ec7f3b25eaf47c447f4005561ae2ff32545d3dff/CHANG

Comments (0)

No comments yet. Start the discussion.

Comment on this issue