docs(skills): document .copilot/skills/ canonical path + .squad/skills/ fallback

docs/src/content/docs/concepts/portability.md

@@ -64,7 +64,7 @@ squad export --out ./backups/team.json  # custom path
 | Agent charters | ✅ |
 | Agent histories | ✅ (split into portable vs project-specific) |
 | Casting state | ✅ |
-| Skills | ✅ All earned skills from `.squad/skills/` |
+| Skills | ✅ All earned skills from `.copilot/skills/` (and `.squad/skills/` legacy fallback) |
 | Decisions | ✅ |
 
 Skills are fully portable — they export and import with perfect fidelity.
@@ -101,7 +101,7 @@ Plugins are community-curated bundles of agent templates, skills, and best pract
 ### What's in a Plugin
 
 - **Agent templates** — specialized role charters (e.g., "AWS DevOps", "Python Data Science")
-- **Skills** — reusable `.squad/skills/SKILL.md` files
+- **Skills** — reusable `.copilot/skills/{name}/SKILL.md` files
 - **Instructions** — `decisions.md` snippets for conventions and routing
 - **Sample prompts** — ready-to-use prompts that activate plugin capabilities
 
@@ -126,7 +126,7 @@ Or use the command:
 /plugin install awesome-copilot/react-component-library
 ```
 
-Squad downloads the bundle, merges agent templates into `.squad/agents/`, adds skills to `.squad/skills/`, updates `decisions.md`, and seeds agents with the new knowledge.
+Squad downloads the bundle, merges agent templates into `.squad/agents/`, adds skills to `.copilot/skills/`, updates `decisions.md`, and seeds agents with the new knowledge.
 
 ### Managing Marketplaces
 
@@ -175,7 +175,7 @@ Declare external Squad sources and automatically inherit their context at sessio
 
 ### What Gets Inherited
 
-- **Skills** — all `.squad/skills/*/SKILL.md` files
+- **Skills** — all `.copilot/skills/*/SKILL.md` (and `.squad/skills/*/SKILL.md`) files
 - **Decisions** — `.squad/decisions.md`
 - **Wisdom** — `.squad/identity/wisdom.md`
 - **Casting Policy** — `.squad/casting/policy.json`

docs/src/content/docs/features/skills.md

@@ -25,15 +25,34 @@ Agents learn from real work and write skill files — reusable patterns, convent
 ## Where Skills Live
 
 ```
-.squad/skills/{skill-name}/SKILL.md
+.copilot/skills/{skill-name}/SKILL.md
 ```
 
 Each skill is a directory containing a `SKILL.md` file. Skills are **team-wide knowledge** — not tied to individual agents. All agents can read and use any skill.
 
+> **Note:** `.squad/skills/` is a supported legacy path. Skills there are still discovered at read time and take **highest** scan precedence. The CLI, SDK tool, and `squad init` all write to `.copilot/skills/` by default. See [Skill directory precedence](#skill-directory-precedence) below.
+
 > **Portable across projects**: Skills export and import with your team. When you move a trained team to a new repo, all their earned knowledge comes with them.
 
 ---
 
+## Skill directory precedence
+
+Squad scans five directories for skills at read time. When the same skill name appears in more than one location, the highest-precedence copy wins:
+
+| Priority | Directory | Notes |
+|----------|-----------|-------|
+| 1 | `.squad/skills/` | Legacy path — **highest** scan priority for backward compatibility |
+| 2 | `.copilot/skills/` | **Current write target** — CLI commands, SDK tool, and `squad init` write here |
+| 3 | `.github/skills/` | GitHub-native path |
+| 4 | `.claude/skills/` | Claude-specific path |
+| 5 | `.agents/skills/` | Generic agents path |
+
+**Writes default to `.copilot/skills/`** — that is what the CLI `skill` commands, the SDK skill tool, sharing/consult, and `squad init` create. `.squad/skills/` is retained for backward compatibility; any skill already there continues to work and takes highest precedence if a same-named skill also exists in `.copilot/skills/`.
+
+> **Tip:** If you have skills in `.squad/skills/` from an older install, they continue to work as-is. To consolidate, move them to `.copilot/skills/` — but remove the `.squad/skills/` copy first, otherwise the old location will shadow the new one.
+---
+
 ## Types of Skills
 
 ### Built-in Skills
@@ -92,7 +111,7 @@ Confidence only goes up, never down. A skill that reaches `high` stays there.
 After successfully setting up a CI pipeline, an agent might create:
 
 ```
-.squad/skills/ci-github-actions/SKILL.md
+.copilot/skills/ci-github-actions/SKILL.md
 ```
 
 ```markdown
@@ -117,7 +136,7 @@ After successfully setting up a CI pipeline, an agent might create:
 
 - Skills compound over time. A mature project has skills covering testing patterns, deployment procedures, API conventions, and more.
 - Built-in skills are overwritten on upgrade. Earned skills are never touched.
-- **Skills are shared across the whole team** — any agent can read any skill. They're stored in a flat `.squad/skills/` directory, not per-agent files.
+- **Skills are shared across the whole team** — any agent can read any skill. They're stored in a flat `.copilot/skills/` directory by default, not per-agent files. (`.squad/skills/` is still scanned as a legacy fallback — see [Skill directory precedence](#skill-directory-precedence).)
 - You can manually edit skill files if you want to seed knowledge (e.g., paste your team's existing conventions into a `SKILL.md`).
 - **Skills survive export/import** — your team's accumulated knowledge is fully portable across projects.
 
@@ -127,7 +146,7 @@ After successfully setting up a CI pipeline, an agent might create:
 list all skills
 ```
 
-Shows all skill files in `.squad/skills/` with confidence levels for earned skills.
+Shows all skill files in `.copilot/skills/` (and `.squad/skills/` if present) with confidence levels for earned skills.
 
 ```
 what's the confidence level for the CI skill?