/plugin-list
List all installed EvoNexus plugins with status, version, and update availability. Use when the user asks about installed plugins, wants an inventory, or mentions plugins generally. Triggers on "quais plugins tenho", "list plugins", "plugins instalados", "o que tem instalado".
$ npx -y skills add evolution-foundation/evo-nexus --skill plugin-list --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-list
Context preview
The summary Claude sees to decide when to auto-load this skill.
List all installed EvoNexus plugins with status, version, and update availability. Use when the user asks about installed plugins, wants an inventory, or mentions plugins generally. Triggers on "quais plugins tenho", "list plugins", "plugins instalados", "o que tem instalado".
SKILL.md
plugin-list.SKILL.mdname: plugin-list
description: List all installed EvoNexus plugins with status, version, and update availability. Use when the user asks about installed plugins, wants an inventory, or mentions plugins generally. Triggers on "quais plugins tenho", "list plugins", "plugins instalados", "o que tem instalado".
metadata:
category: plugins
version: 1.0.0
Plugin List
Return the current inventory of installed plugins.
How to use
Step 1 — Fetch installed plugins
from dashboard.backend.sdk_client import evo
plugins = evo.get("/api/plugins")Response is a JSON array of `{id, name, version, status, tier, installed_at, source_url}`.
Step 2 — (Optional) Cross-check marketplace for updates
If user hints at "desatualizados" / "outdated" / "updates":
marketplace = evo.get("/api/plugins/marketplace")Match installed vs marketplace by `id`; flag when `installed.version < marketplace.version` (semver).
Step 3 — Render compact markdown table
| slug | name | version | status | update? |
|------|------|---------|--------|---------|
| pm-essentials | PM Essentials | 1.0.0 | active | — |
| int-pipedrive | Pipedrive Suite | 0.4.1 | active | 0.5.0 |
Order by `name` ascending. Hide columns user didn't ask for.
Close with a one-line summary: total installed, N with updates, N broken (`status=broken` = manifest SHA mismatch, suggest `plugin-health`).
Error handling
- Empty `[]` — say plainly no plugins installed, offer `plugin-marketplace`.
- HTTP 5xx — verify the dashboard backend is running; don't invent data.
Notes for the agent
- Omit `source_url` from output unless asked — long and noisy.
- If `status` is `routine_activation_pending`, surface explicitly — scheduler offline during install, restart needed.
Read more
name: plugin-list description: List all installed EvoNexus plugins with status, version, and update availability. Use when the user asks about installed plugins, wants an inventory, or mentions plugins generally. Triggers on "quais plugins tenho", "list plugins", "plugins instalados", "o que tem instalado". metadata: category: plugins version: 1.0.0
Plugin List
Return the current inventory of installed plugins.
How to use
Step 1 — Fetch installed plugins
from dashboard.backend.sdk_client import evo
plugins = evo.get("/api/plugins")Response is a JSON array of `{id, name, version, status, tier, installed_at, source_url}`.
Step 2 — (Optional) Cross-check marketplace for updates
If user hints at "desatualizados" / "outdated" / "updates":
marketplace = evo.get("/api/plugins/marketplace")Match installed vs marketplace by `id`; flag when `installed.version < marketplace.version` (semver).
Step 3 — Render compact markdown table
| slug | name | version | status | update? | |------|------|---------|--------|---------| | pm-essentials | PM Essentials | 1.0.0 | active | — | | int-pipedrive | Pipedrive Suite | 0.4.1 | active | 0.5.0 |
Order by `name` ascending. Hide columns user didn't ask for.
Close with a one-line summary: total installed, N with updates, N broken (`status=broken` = manifest SHA mismatch, suggest `plugin-health`).
Error handling
- Empty `[]` — say plainly no plugins installed, offer `plugin-marketplace`.
- HTTP 5xx — verify the dashboard backend is running; don't invent data.
Notes for the agent
- Omit `source_url` from output unless asked — long and noisy.
- If `status` is `routine_activation_pending`, surface explicitly — scheduler offline during install, restart needed.
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