Skip to content
Skills Library
AI & agents · Tool integration

plugin-list

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

Repository
evo-nexus ↗
Licence
Apache-2.0
Last repository change
12.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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

Triggers from the description

quais plugins tenholist pluginsplugins instaladoso que tem instalado
Original author 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".

How it works

  1. How to use
  2. Error handling
  3. Notes for the agent
Original SKILL.md headings · 50 lines, 210 words
SKILL.md preview
---
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

```python
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":

```python
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.

Versions

The database has no other skills named plugin-list.

Database snapshot: 13.11.2026 · package version b9d873527526 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100plugin-marketplace
    Browse the EvoNexus plugin marketplace, searching for plugins by keyword, tag, or capability. Use when the user wants to find a plugin, asks what plugins are available, or describes a need that might have a plugin. Triggers on "procura plugin de X", "marketplace de plugins",…
  • 100plugin-update
    Update an installed EvoNexus plugin to a newer version from its source. Use when the user asks to update, upgrade, or bump a plugin to the latest version. Triggers on "atualiza plugin X", "update plugin X", "upgrade plugin Y".
  • 100update-plugin
    Refreshes the domain-expert marketplace catalog and updates installed Domain Expert plugins (domain-expert-core plus any per-domain plugin such as database, security, devops, os) to their latest versions. Also handles migrating off the old pre-marketplace monolithic…
  • 90upkeep
    Keep a project's plugins current — refresh the marketplaces, update installed plugins that have a newer version, and offer plugins new to the marketplaces the project uses, then hand over /reload-plugins. Use on /upkeep, when the upkeep notice says updates or new plugins exist,…
  • 100import-plugins
    Bring plugins the user already installed in Claude Code or Codex into Kiro, or import one straight from a marketplace GitHub URL. Use when the user mentions Claude Code plugins, Codex plugins, a plugin marketplace, or asks to bring, move, port or migrate their plugins to Kiro.…
  • 100refresh-plugin-cache
    This skill should be used when the user asks to "refresh the plugin cache", "update plugin cache", "sync plugin cache", "update installed plugins", "check for plugin updates", "are my plugins up to date", "is the plugin cache fresh", or "verify plugin versions". Scoped to…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.