diff --git a/documentation/docs/guides/context-engineering/using-skills.md b/documentation/docs/guides/context-engineering/using-skills.md
index b5b9f540a1..8a5c0cfdd5 100644
--- a/documentation/docs/guides/context-engineering/using-skills.md
+++ b/documentation/docs/guides/context-engineering/using-skills.md
@@ -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
diff --git a/documentation/docs/mcp/skills-mcp.md b/documentation/docs/mcp/skills-mcp.md
index 3bbfe8088e..290a62a1b0 100644
--- a/documentation/docs/mcp/skills-mcp.md
+++ b/documentation/docs/mcp/skills-mcp.md
@@ -10,7 +10,7 @@ import GooseBuiltinInstaller from '@site/src/components/GooseBuiltinInstaller';
 
 The Skills extension loads *skills* — reusable sets of instructions that teach goose how to perform specific tasks or follow particular workflows.
 
-goose automatically discovers skills at startup and uses them when relevant to your request. goose skills are compatible with Claude Desktop's skill format, so skills you create for one tool work with both. To learn about creating skills and how goose uses them, see [Using Skills](/docs/guides/context-engineering/using-skills).
+goose automatically discovers skills at startup and uses them when relevant to your request. goose loads skills from `.agents/skills/` in your project directory and `~/.config/agents/skills/` globally, making skills portable across different AI coding agents. To learn about creating skills and how goose uses them, see [Using Skills](/docs/guides/context-engineering/using-skills).
 
 ## Configuration
 
@@ -20,7 +20,7 @@ goose automatically discovers skills at startup and uses them when relevant to y
   <TabItem value="ui" label="goose Desktop" default>
   <GooseBuiltinInstaller
     extensionName="Skills"
-    description="Load and use skills from the .claude/skills or .goose/skills directories"
+    description="Load and use skills from the .agents/skills directory"
   />
   </TabItem>
   <TabItem value="cli" label="goose CLI">
@@ -48,7 +48,7 @@ goose automatically discovers skills at startup and uses them when relevant to y
 
 ## Example Usage
 
-Let's say you have a skill that goose discovers on startup in `~/.config/goose/skills/deploy/SKILL.md`:
+Let's say you have a skill that goose discovers on startup in `~/.config/agents/skills/deploy/SKILL.md`:
 
 ```markdown
 ---