| 1 | --- |
| 2 | name: skill-installer |
| 3 | description: Install, update, trust, or inspect Codewhale skills from GitHub or local skill folders. Use when the user asks for available skills or wants a community skill installed. |
| 4 | --- |
| 5 | |
| 6 | # Skill Installer |
| 7 | |
| 8 | Use this skill when the user wants to find, install, update, trust, or remove a |
| 9 | Codewhale skill. |
| 10 | |
| 11 | ## Commands |
| 12 | |
| 13 | - List installed skills: `/skills` |
| 14 | - Activate a skill: `/skill <name>` |
| 15 | - Scaffold a new skill: `/skill new` |
| 16 | - Install from GitHub: `/skill install github:<owner>/<repo>` |
| 17 | - Update installed skills: `/skill update` |
| 18 | - Remove a skill: `/skill uninstall <name>` |
| 19 | - Trust a skill for script/tool use: `/skill trust <name>` |
| 20 | |
| 21 | ## Workflow |
| 22 | |
| 23 | 1. Identify the source: |
| 24 | - Existing local folder with `SKILL.md` |
| 25 | - GitHub repo or registry entry |
| 26 | - User request for a new skill scaffold |
| 27 | 2. Prefer Codewhale's native `/skill` commands over ad hoc copying. |
| 28 | 3. For GitHub/community skills, inspect the `SKILL.md` before recommending |
| 29 | trust. Treat scripts and companion files as untrusted until reviewed. |
| 30 | 4. After installing, tell the user to restart the session if the skill does not |
| 31 | appear immediately in the available-skills list. |
| 32 | 5. If a skill conflicts by name with a workspace skill, explain that workspace |
| 33 | skill directories take precedence over global `~/.codewhale/skills`, with |
| 34 | `~/.deepseek/skills` retained as a legacy fallback. |
| 35 | |
| 36 | Do not execute community skill scripts unless the user explicitly asks and the |
| 37 | skill has been reviewed or trusted. |
| 38 |