Skip to content
Automation
Skill

/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".

From plugin
evo-nexus
549193 skills38 agents40 commands9 MCP

Claude Code

$ npx -y skills add evolution-foundation/evo-nexus --skill plugin-list --agent claude-code

SKILL.md

plugin-list.SKILL.md
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.
Read more
@evolution-foundation
Ships withevo-nexus

The open source operating system for AI-powered businesses

549193 skills38 agents9 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
549
Star history of evolution-foundation/evo-nexus on GitHub, a chart by star-history.com

Other skills on evo-nexus.

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n12d209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
agent-browser

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…

@vercel-labs-2@vercel-labs-2Install Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about plugin-list.

Which coding agents can use plugin-list?
plugin-list installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.