Summary

Project skills stored in a .agents/skills/ directory that sits in a subdirectory of the git repo are not discovered by Warp. Skills placed at the repo root work correctly. This contradicts the documented behavior: "For Git repositories, Warp includes all skills from your current directory up through the repository root."

Problem

When the working directory is a subfolder of the git repo and .agents/skills/ is located there (not at the repo root), Warp does not surface those skills in the slash command autocomplete or via natural language invocation. Moving .agents/skills/ to the repo root makes them discoverable again.

Reproduction steps or desired workflow

1. Create a monorepo with structure:

   repo-root/           ← git root
   └── sub-project/
       └── .agents/
           └── skills/
               └── my-skill/
                   └── SKILL.md   ← valid name + description frontmatter
   

2. Open Warp with working directory set to repo-root/sub-project/.
3. Open an agent conversation.
4. Type /my-skill in the slash command menu — skill does not appear.
5. Move .agents/skills/my-skill/ to repo-root/.agents/skills/my-skill/.
6. Repeat step 4 — skill now appears correctly.

Expected behavior

Skills in .agents/skills/ at the current working directory (or any ancestor up to the repo root) are discovered and available via slash commands, as documented.

Actual behavior

Only skills at the repository root .agents/skills/ are discovered. Skills in a .agents/skills/ folder inside a subdirectory of the repo are silently ignored, even when the agent session is started from that subdirectory.

Artifacts

None attached.

Warp version

0.2026.04.27.15.32.02

Operating system

macOS

Possible source references

• Git repo root: /Users/.../Wakam/ — skills placed here ARE discovered
• Skills location: /Users/.../Wakam/Pricing/.agents/skills/ — 5 skills (spec-gate, implement, implementation-gate, test-implementation, execute-api-call), all with valid YAML frontmatter, NOT discovered when working in Pricing/