# Uninstall

> Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

- Skill: `daddia/uninstall` (Agent Skill)
- Install (CLI): `npx skillmds@latest add daddia/uninstall`
- Raw SKILL.md: https://api.skillmd.com/api/skills/daddia/uninstall/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: daddia (https://skillmd.com/u/daddia)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/daddia/uninstall

---

# /strategy-builder-hub:uninstall

## When to use

Fully remove hub-installed community skill — confirm paths, delete files, log uninstall.

## What this skill does not do

- **Does not touch first-party plugins.**
- **Does not delete without explicit yes.**
- **Does not disable-only** — suggest `/strategy-builder-hub:disable` to keep files.

## Preconditions

| Input | If missing |
|---|---|
| Skill name | Ask |
| Install log entry | Refuse if not recorded |
| Load `skill-manager` reference | Required before substantive work |

## Provisional mode

N/A — confirm-before-delete always.

## Trust spine

Governance-tracking; install-log audit; built-in plugin refusal.

## Workflow

Run the `uninstall` workflow from the skill-manager reference skill.

Safety rules:

1. **Only uninstall community skills installed through this hub.**
2. **Never uninstall first-party plugin skills.**
3. **Confirm before removing files** — show every path; proceed only on explicit `yes`.
4. **Log the uninstall** to `install-log.yaml`.

If the user wants to keep files, suggest `/strategy-builder-hub:disable` instead.

> Detailed workflows live in the `skill-manager` reference skill.

## Worked example

**Input:** `uninstall old-scan` — in install log, not first-party.

**Expected output:** Deletion paths listed; user types yes; files removed; log entry `uninstall`.

## Propose profile update

When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), **propose a profile update**: show the exact diff against `~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/CLAUDE.md` (org-wide facts go to `org-profile.md`), ask for confirmation, and write only on yes. Only `/strategy-builder-hub:practice-setup` auto-applies a full profile write.

## Outputs

Follows plugin `CLAUDE.md` § Outputs. Next: `registry-browser` for replacement skill, or done.