How do I install the Plugin Remover skill?

Run npx skillmds@latest add richfrem/plugin-remover in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plugin Remover safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plugin Remover?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plugin Remover free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plugin Remover?

richfrem (@richfrem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plugin Remover by richfrem — Agent Skill

Name: Plugin Remover
Rating: 4.5 (4 reviews)
Author: richfrem

File contents

Plugin Remover Skill

Overview

This skill orchestrates the safe, interactive removal of plugins from the local agent environment and updates the canonical tracking registries (plugin-sources.json and skills-lock.json).

By relying on the plugin_remove.py TUI, this skill ensures that no ghost files, orphaned symlinks, or stale hook registrations remain after a plugin is uninstalled.

Key Architecture Rules

Execution: All deletions must be run transparently through plugin_remove.py. Do NOT attempt to manually rm -rf plugin directories directly from .agents/.
Target Folders: Artifacts are automatically scrubbed from .agents/skills, .agents/workflows, .claude/, .gemini/, etc.
Registries: The uninstaller automatically parses and scrubs the removed plugin from both skills-lock.json and plugin-sources.json to keep auto-update loops synchronized.

Instructions

Whenever the user asks to "remove a plugin", "uninstall a skill", or "delete a plugin", guide them to use the interactive TUI or run headless via flags.

Remove via GitHub (remote, no local clone required)

# Interactive TUI — lists all plugins tracked in plugin-sources.json
uvx --from git+https://github.com/richfrem/agent-plugins-skills plugin-remove

# Headless: remove a specific plugin without prompting
uvx --from git+https://github.com/richfrem/agent-plugins-skills plugin-remove --plugins agent-orchestration/ --yes

# Headless: remove all tracked plugins
uvx --from git+https://github.com/richfrem/agent-plugins-skills plugin-remove --all --yes

Remove via Local Path (development / offline)

# Interactive TUI from local clone
uvx --from . plugin-remove

# Headless: remove a specific plugin
uvx --from . plugin-remove --plugins agent-orchestration/ --yes

# Or run the underlying Python script directly:
python plugins/plugin-manager/scripts/plugin_remove.py
python plugins/plugin-manager/scripts/plugin_remove.py --plugins agent-orchestration/ --yes
python plugins/plugin-manager/scripts/plugin_remove.py --dry-run

What Removal Does

For each selected plugin, the uninstaller:

Deletes the plugin directory/files from .agents/skills/, .agents/workflows/, .agents/agents/, .agents/hooks/, .claude/, .gemini/, etc.
Removes the plugin entry from plugin-sources.json (auto-update registry).
Removes the plugin entry from skills-lock.json.

Dependencies

Python 3.8+ (No external pip dependencies required).
plugin-sources.json must exist and contain tracked plugins. Run plugin-add first.

---name: plugin-removerdescription: Interactively select and uninstall agent plugins and skills from the local .agents/ environment.---# Plugin Remover Skill## OverviewThis skill orchestrates the safe, interactive removal of plugins from the local agent environment and updates the canonical tracking registries (`plugin-sources.json` and `skills-lock.json`).By relying on the `plugin_remove.py` TUI, this skill ensures that no ghost files, orphaned symlinks, or stale hook registrations remain after a plugin is uninstalled.## Key Architecture Rules- **Execution**: All deletions must be run transparently through `plugin_remove.py`. Do NOT attempt to manually `rm -rf` plugin directories directly from `.agents/`.- **Target Folders**: Artifacts are automatically scrubbed from `.agents/skills`, `.agents/workflows`, `.claude/`, `.gemini/`, etc.- **Registries**: The uninstaller automatically parses and scrubs the removed plugin from both `skills-lock.json` and `plugin-sources.json` to keep auto-update loops synchronized.## InstructionsWhenever the user asks to "remove a plugin", "uninstall a skill", or "delete a plugin", guide them to use the interactive TUI or run headless via flags.### Remove via GitHub (remote, no local clone required)```bash# Interactive TUI — lists all plugins tracked in plugin-sources.jsonuvx --from git+https://github.com/richfrem/agent-plugins-skills plugin-remove# Headless: remove a specific plugin without promptinguvx --from git+https://github.com/richfrem/agent-plugins-skills plugin-remove --plugins agent-orchestration/ --yes# Headless: remove all tracked pluginsuvx --from git+https://github.com/richfrem/agent-plugins-skills plugin-remove --all --yes```### Remove via Local Path (development / offline)```bash# Interactive TUI from local cloneuvx --from . plugin-remove# Headless: remove a specific pluginuvx --from . plugin-remove --plugins agent-orchestration/ --yes# Or run the underlying Python script directly:python plugins/plugin-manager/scripts/plugin_remove.pypython plugins/plugin-manager/scripts/plugin_remove.py --plugins agent-orchestration/ --yespython plugins/plugin-manager/scripts/plugin_remove.py --dry-run```### What Removal DoesFor each selected plugin, the uninstaller:1. Deletes the plugin directory/files from `.agents/skills/`, `.agents/workflows/`, `.agents/agents/`, `.agents/hooks/`, `.claude/`, `.gemini/`, etc.2. Removes the plugin entry from `plugin-sources.json` (auto-update registry).3. Removes the plugin entry from `skills-lock.json`.## Dependencies- Python 3.8+ (No external pip dependencies required).- `plugin-sources.json` must exist and contain tracked plugins. Run `plugin-add` first.

Frequently asked questions

Plugin Remover