mirror of
https://github.com/block/goose.git
synced 2026-05-02 21:40:58 +00:00
docs: update skills extension to support .agents/skills directories (#6199)
Signed-off-by: Adrian Cole <adrian@tetrate.io> Signed-off-by: Joah Gerstenberg <joah@squareup.com> Co-authored-by: Adrian Cole <64215+codefromthecrypt@users.noreply.github.com> Co-authored-by: Amp <amp@ampcode.com>
This commit is contained in:
parent
7f9c21a455
commit
762b2cf54d
2 changed files with 15 additions and 19 deletions
|
|
@ -24,33 +24,29 @@ You can also ask goose what skills are available.
|
|||
- [recipes](/docs/guides/recipes/session-recipes): Shareable configurations that package instructions, prompts, and settings together
|
||||
:::
|
||||
|
||||
## Claude Compatibility
|
||||
## Skill Locations
|
||||
|
||||
goose skills use the same format as Claude Desktop skills. goose discovers skills from both `.claude/skills/` and `.goose/skills/` directories, so you can share skills between both tools or create tool-specific versions as needed.
|
||||
Skills can be stored globally and/or per-project. goose checks all of these directories in order and combines what it finds. If the same skill name exists in multiple directories, later directories take priority:
|
||||
|
||||
When the same skill name exists in multiple directories, goose follows the priority order listed in [Skill Locations](#skill-locations). Later directories override earlier ones regardless of whether they're `.claude` or `.goose` directories.
|
||||
1. `~/.claude/skills/` — Global, shared with Claude Desktop
|
||||
2. `~/.config/agents/skills/` — Global, portable across AI coding agents
|
||||
3. `~/.config/goose/skills/` — Global, goose-specific
|
||||
4. `./.claude/skills/` — Project-level, shared with Claude Desktop
|
||||
5. `./.goose/skills/` — Project-level, goose-specific
|
||||
6. `./.agents/skills/` — Project-level, portable across AI coding agents
|
||||
|
||||
Use global skills for workflows you use across projects. Use project-level skills for procedures unique to a codebase.
|
||||
|
||||
## Creating a Skill
|
||||
|
||||
Create a skill when you have a repeatable workflow that involves multiple steps, specialized knowledge, or supporting files.
|
||||
|
||||
### Skill Locations
|
||||
|
||||
Skills can be stored globally and/or per-project. goose checks all of these directories in order and combines what it finds. If the same skill name exists in multiple directories, the latest directory takes priority:
|
||||
|
||||
1. `~/.claude/skills/` — Global, shared with Claude Desktop
|
||||
2. `~/.config/goose/skills/` — Global, goose-specific
|
||||
3. `./.claude/skills/` — Current directory, shared with Claude Desktop
|
||||
4. `./.goose/skills/` — Current directory, goose-specific (highest priority)
|
||||
|
||||
Use global skills for workflows you use across projects. Use project-specific skills for procedures unique to a codebase.
|
||||
|
||||
### Skill File Structure
|
||||
|
||||
Each skill lives in its own directory with a `SKILL.md` file:
|
||||
|
||||
```
|
||||
~/.config/goose/skills/
|
||||
~/.config/agents/skills/
|
||||
└── code-review/
|
||||
└── SKILL.md
|
||||
```
|
||||
|
|
@ -93,7 +89,7 @@ When reviewing code, check each of these areas:
|
|||
Skills can include supporting files like scripts, templates, or configuration files. Place them in the skill directory:
|
||||
|
||||
```
|
||||
~/.config/goose/skills/
|
||||
~/.config/agents/skills/
|
||||
└── api-setup/
|
||||
├── SKILL.md
|
||||
├── setup.sh
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue