Problem

The spec defines a portable skill format but doesn't specify where agents should look for skills on the filesystem. This means every agent implementation invents its own convention, defeating the purpose of a standard format.

Current state (as far as I can tell):

• Claude (computer use): /mnt/skills/
• Claude Code: ?
• Codex: .codex/skills/
• Other agents: ?

If I write a skill, I have no idea where to put it so that multiple agents can find it.

Proposal

Define a standard search path, something like:

./.agent-skills/           # Project-level (checked first)
~/.agent-skills/           # User-level
$AGENT_SKILLS_PATH         # Optional override (colon-separated, like $PATH)

Agents SHOULD check these locations in order. Agents MAY support additional implementation-specific paths, but supporting the standard paths ensures portability.

Alternatives considered

• Environment variable only: Too invisible, easy to misconfigure
• Single global path only: Doesn't support project-specific skills
• Leave it to implementations: Current state, doesn't work

Additional context

Without this, "Agent Skills" is a file format, not an interoperability standard. The format is the easy part—discovery is what makes it actually portable.