Skip to content

Proposal: include a standard folder where agent skills should be #15

@douglascamata

Description

@douglascamata

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

Pending

Not adopting yet

There are too many tools to list here. Anyone not mention in "ready" or "pending" is considered not adopting yet.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions