fix(skills): update create-skill SKILL.md + workflows to canonical skill paths

After last fire fixed sf-skill-ecosystem.md, three more sites in the
create-skill skill were still teaching the legacy ~/.sf/agent/skills/
and .pi/agent/skills/ paths:

- create-skill/SKILL.md:91 quick reference
- create-skill/workflows/create-new-skill.md:18 (scope question)
- create-skill/workflows/create-new-skill.md:102 (Step 5 directory creation)
- create-skill/workflows/audit-skill.md:19,29 (skill enumeration ls commands)

Now point at the canonical four-directory ecosystem
(~/.agents/skills/, ~/.claude/skills/, plus project-local variants)
that the runtime actually scans (per skill-discovery.ts:16-17,
skill-telemetry.ts:34-35, preferences-skills.ts:39-43).

The audit-skill ls block now enumerates all four locations so the
audit report matches what SF will actually load.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

src/resources/skills/create-skill/SKILL.md

@@ -87,9 +87,9 @@ Then proceed directly to the workflow.
 <quick_reference>
 ## Skill Structure Quick Reference
 
-**Skill directories:**
-- Global: `~/.sf/agent/skills/{skill-name}/`
-- Project-local: `.pi/agent/skills/{skill-name}/`
+**Skill directories (SF scans all four):**
+- Global: `~/.agents/skills/{skill-name}/` or `~/.claude/skills/{skill-name}/`
+- Project-local: `<project>/.agents/skills/{skill-name}/` or `<project>/.claude/skills/{skill-name}/`
 
 **Simple skill (single file):**
 ```yaml

src/resources/skills/create-skill/workflows/audit-skill.md

@@ -13,25 +13,27 @@
 
 **DO NOT use AskUserQuestion** - there may be many skills.
 
-Enumerate skills from both directories:
+Enumerate skills from all four directories:
 ```bash
 echo "=== Global skills ==="
-ls ~/.sf/agent/skills/ 2>/dev/null || echo "(none)"
+ls ~/.agents/skills/ 2>/dev/null || echo "(none)"
+ls ~/.claude/skills/ 2>/dev/null || echo "(none)"
 
 echo "=== Project-local skills ==="
-ls .pi/agent/skills/ 2>/dev/null || echo "(none)"
+ls .agents/skills/ 2>/dev/null || echo "(none)"
+ls .claude/skills/ 2>/dev/null || echo "(none)"
 ```
 
 Present as:
 ```
 Available skills:
 
-Global (~/.sf/agent/skills/):
+Global (~/.agents/skills/ + ~/.claude/skills/):
 1. create-skill
 2. manage-stripe
 ...
 
-Project-local (.pi/agent/skills/):
+Project-local (.agents/skills/ + .claude/skills/):
 3. project-deploy
 ...
 ```

src/resources/skills/create-skill/workflows/create-new-skill.md

@@ -15,8 +15,8 @@
 **Ask the user:**
 "Should this skill be global or project-local?"
 
-1. **Global** (`~/.sf/agent/skills/`) — Available in all SF sessions
-2. **Project-local** (`.pi/agent/skills/`) — Available only in this project
+1. **Global** (`~/.agents/skills/` or `~/.claude/skills/`) — Available in all SF sessions
+2. **Project-local** (`<project>/.agents/skills/` or `<project>/.claude/skills/`) — Available only in this project
 
 ## Step 2: Adaptive Requirements Gathering
 
@@ -99,11 +99,11 @@ See references/recommended-structure.md for templates.
 ## Step 5: Create Directory
 
 Use the scope selected in Step 1 to determine the base path:
-- **Global:** `~/.sf/agent/skills/{skill-name}`
-- **Project-local:** `.pi/agent/skills/{skill-name}`
+- **Global:** `~/.agents/skills/{skill-name}` (or `~/.claude/skills/{skill-name}`)
+- **Project-local:** `<project>/.agents/skills/{skill-name}` (or `<project>/.claude/skills/{skill-name}`)
 
 ```bash
-BASE_PATH="{selected-base}/agent/skills/{skill-name}"
+BASE_PATH="{selected-base}/skills/{skill-name}"
 mkdir -p $BASE_PATH
 # If complex:
 mkdir -p $BASE_PATH/workflows