uninstall-plugin
Remove a previously installed Claude Code plugin and unregister it from the local plugin registry
What this skill does
# Uninstall Plugin You remove a previously installed Claude Code plugin. You remove deployed plugin files and unregister the plugin from the local plugin registry. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "get rid of the voice plugin" → uninstall voice@aiwg - "I don't need the marketing kit anymore" → uninstall marketing@aiwg - "clean up the SDLC agents" → uninstall sdlc@aiwg - "remove everything from that plugin" → uninstall with cleanup ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Uninstall plugin | "uninstall plugin voice@aiwg" | Run `aiwg uninstall-plugin voice@aiwg` | | Remove plugin | "remove plugin marketing@aiwg" | Run `aiwg uninstall-plugin marketing@aiwg` | | Plugin uninstall | "plugin uninstall sdlc@aiwg" | Run `aiwg uninstall-plugin sdlc@aiwg` | | Dry run | "what would removing the voice plugin delete?" | Run `aiwg uninstall-plugin voice@aiwg --dry-run` | | Keep artifacts | "remove the plugin but keep my .aiwg/ files" | Run `aiwg uninstall-plugin sdlc@aiwg --keep-artifacts` | ## Behavior When triggered: 1. **Extract intent**: - Which plugin is being removed? - Is this a dry run (preview) or should changes be applied? - Should project artifacts in `.aiwg/` be preserved? (default: yes, always preserve) 2. **Run the appropriate command**: ```bash # Uninstall a plugin aiwg uninstall-plugin sdlc@aiwg aiwg uninstall-plugin voice@aiwg aiwg uninstall-plugin marketing@aiwg # Preview what would be removed aiwg uninstall-plugin sdlc@aiwg --dry-run # Keep .aiwg/ project artifacts even if plugin-owned (default behavior) aiwg uninstall-plugin sdlc@aiwg --keep-artifacts ``` 3. **Report the result** — list what was removed (agents, commands, skills, rules) and confirm the plugin is deregistered. ## What Gets Removed | Removed | Description | |---------|-------------| | Agent files | Files in `.claude/agents/` that belong to the plugin | | Command files | Files in `.claude/commands/` that belong to the plugin | | Skill files | Files in `.claude/skills/` that belong to the plugin | | Rule files | Files in `.claude/rules/` that belong to the plugin | | Registry entry | Plugin entry removed from local plugin registry | ## What Is NOT Removed | Preserved | Reason | |-----------|--------| | `.aiwg/` project artifacts | These are your project output, not plugin files | | Shared skills used by other plugins | Removed only when last dependent plugin is removed | | Custom modifications to plugin files | Files modified after install are flagged, not deleted | ## Examples ### Example 1: Remove the voice plugin **User**: "Uninstall the voice plugin" **Extraction**: Plugin name is `voice@aiwg` **Action**: ```bash aiwg uninstall-plugin voice@aiwg ``` **Response**: "Uninstalled voice@aiwg. Removed 6 voice profiles from .claude/skills/voices/, 4 soul system skills, 2 rules. Plugin deregistered." ### Example 2: Dry run before removing **User**: "What would removing the SDLC plugin delete?" **Extraction**: Dry-run for sdlc plugin **Action**: ```bash aiwg uninstall-plugin sdlc@aiwg --dry-run ``` **Response**: "Dry run — uninstalling sdlc@aiwg would remove: 58 agents from .claude/agents/, 42 commands from .claude/commands/, 12 skills, 33 rules. Your .aiwg/ project artifacts would NOT be affected. No changes made." ### Example 3: Plugin not found **User**: "Remove the analytics plugin" **Extraction**: Plugin name `analytics` — not in registry **Action**: ```bash aiwg uninstall-plugin analytics@aiwg ``` **Response**: "Plugin `analytics@aiwg` is not installed. Run `aiwg plugin-status` to see what is currently installed." ## Clarification Prompts If the plugin name is ambiguous or not clearly installed: - "Which plugin would you like to remove? Installed plugins: sdlc@aiwg, voice@aiwg. Run `aiwg plugin-status` to confirm." ## References - @$AIWG_ROOT/src/cli/handlers/utilities.ts — Command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.