/plugin-uninstall
Uninstall an EvoNexus plugin, reverting the files it copied and running its uninstall.sql. Use when the user asks to remove, uninstall, or delete a plugin. Triggers on "desinstala plugin X", "remove plugin X", "uninstall plugin X", "tira o plugin Y".
$ npx -y skills add evolution-foundation/evo-nexus --skill plugin-uninstall --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/plugin-uninstall
Context preview
The summary Claude sees to decide when to auto-load this skill.
Uninstall an EvoNexus plugin, reverting the files it copied and running its uninstall.sql. Use when the user asks to remove, uninstall, or delete a plugin. Triggers on "desinstala plugin X", "remove plugin X", "uninstall plugin X", "tira o plugin Y".
SKILL.md
plugin-uninstall.SKILL.mdname: plugin-uninstall
description: Uninstall an EvoNexus plugin, reverting the files it copied and running its uninstall.sql. Use when the user asks to remove, uninstall, or delete a plugin. Triggers on "desinstala plugin X", "remove plugin X", "uninstall plugin X", "tira o plugin Y".
metadata:
category: plugins
version: 1.0.0
Plugin Uninstall
Remove a plugin from the workspace using `DELETE /api/plugins/<slug>`. Uninstall is reverse-order via `.install-manifest.json`.
How to use
Step 1 — Resolve the slug
If not given, call list and ask which one:
from dashboard.backend.sdk_client import evo
plugins = evo.get("/api/plugins")Validate exists:
detail = evo.get(f"/api/plugins/{slug}")If HTTP 404, say so and stop.
Step 2 — Show what will be removed
Read `manifest` from detail. Summarise:
- Files in `.claude/agents/plugin-<slug>-*.md`, `.claude/skills/plugin-<slug>-*/`, `.claude/commands/plugin-<slug>-*.md`, `.claude/rules/plugin-<slug>-*.md`
- Heartbeats registered by the plugin (disappear from `/heartbeats`)
- Routines (scheduler SIGHUP reload on removal)
- Claude hook handlers under `plugins/<slug>/claude-hook-handlers/`
- Contents of `migrations/uninstall.sql` — full text
- Contents of `hooks/pre-uninstall.sh` and `hooks/post-uninstall.sh` — full text
**Important**: user data created **inside** plugin-managed tables is usually DROPped by uninstall SQL. Tell the user explicitly and ask if they want to export first.
Step 3 — Require explicit confirmation
Accept only clear affirmatives. If user hesitates, offer:
- Export first via `GET /api/plugins/<slug>/readonly-data/<query>` if declared
- Disable instead of remove: `evo.patch(f"/api/plugins/{slug}", {"enabled": False})` — reversible, keeps data
Step 4 — Run uninstall
evo.delete(f"/api/plugins/{slug}")Step 5 — Report
On success, summarise: files removed, tables dropped, hooks cleared. Point to `/plugins` for confirmation.
Error handling
- `HTTP 404 not_found` — slug doesn't exist. Reprompt.
- `HTTP 409 uninstall_failed` — reverse-order chain failed. Surface specific step. Offer manual recovery (delete `plugins/<slug>/` after fixing, then retry).
- `HTTP 500 sql_rollback_failed` — rare. DB may be inconsistent. Check `ADWs/logs/plugins/`.
Notes for the agent
- Disable ≠ uninstall. Disable keeps data and is reversible.
- If plugin has routines, scheduler reloads automatically. If offline, user must restart.
Read more
name: plugin-uninstall description: Uninstall an EvoNexus plugin, reverting the files it copied and running its uninstall.sql. Use when the user asks to remove, uninstall, or delete a plugin. Triggers on "desinstala plugin X", "remove plugin X", "uninstall plugin X", "tira o plugin Y". metadata: category: plugins version: 1.0.0
Plugin Uninstall
Remove a plugin from the workspace using `DELETE /api/plugins/<slug>`. Uninstall is reverse-order via `.install-manifest.json`.
How to use
Step 1 — Resolve the slug
If not given, call list and ask which one:
from dashboard.backend.sdk_client import evo
plugins = evo.get("/api/plugins")Validate exists:
detail = evo.get(f"/api/plugins/{slug}")If HTTP 404, say so and stop.
Step 2 — Show what will be removed
Read `manifest` from detail. Summarise:
- Files in `.claude/agents/plugin-<slug>-*.md`, `.claude/skills/plugin-<slug>-*/`, `.claude/commands/plugin-<slug>-*.md`, `.claude/rules/plugin-<slug>-*.md`
- Heartbeats registered by the plugin (disappear from `/heartbeats`)
- Routines (scheduler SIGHUP reload on removal)
- Claude hook handlers under `plugins/<slug>/claude-hook-handlers/`
- Contents of `migrations/uninstall.sql` — full text
- Contents of `hooks/pre-uninstall.sh` and `hooks/post-uninstall.sh` — full text
**Important**: user data created **inside** plugin-managed tables is usually DROPped by uninstall SQL. Tell the user explicitly and ask if they want to export first.
Step 3 — Require explicit confirmation
Accept only clear affirmatives. If user hesitates, offer:
- Export first via `GET /api/plugins/<slug>/readonly-data/<query>` if declared
- Disable instead of remove: `evo.patch(f"/api/plugins/{slug}", {"enabled": False})` — reversible, keeps data
Step 4 — Run uninstall
evo.delete(f"/api/plugins/{slug}")Step 5 — Report
On success, summarise: files removed, tables dropped, hooks cleared. Point to `/plugins` for confirmation.
Error handling
- `HTTP 404 not_found` — slug doesn't exist. Reprompt.
- `HTTP 409 uninstall_failed` — reverse-order chain failed. Surface specific step. Offer manual recovery (delete `plugins/<slug>/` after fixing, then retry).
- `HTTP 500 sql_rollback_failed` — rare. DB may be inconsistent. Check `ADWs/logs/plugins/`.
Notes for the agent
- Disable ≠ uninstall. Disable keeps data and is reversible.
- If plugin has routines, scheduler reloads automatically. If offline, user must restart.
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

