/plugin-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",
$ npx -y skills add evolution-foundation/evo-nexus --skill plugin-marketplace --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-marketplace
Context preview
The summary Claude sees to decide when to auto-load this skill.
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",
SKILL.md
plugin-marketplace.SKILL.mdname: plugin-marketplace
description: 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", "plugins disponíveis para Y", "tem algum plugin que faz Z".
metadata:
category: plugins
version: 1.0.0
Plugin Marketplace
Browse the curated `registry.json` from `github.com/EvolutionAPI/evonexus-plugins` plus community plugins. Help the user find what they need and hand off to `plugin-install` when they pick one.
How to use
Step 1 — Fetch registry
from dashboard.backend.sdk_client import evo
marketplace = evo.get("/api/plugins/marketplace")Cached 10min backend-side. If backend returns 503 `marketplace_unreachable`, tell the user the registry is offline and suggest direct install via git URL (`plugin-install`).
Step 2 — Filter by user intent
Each entry: `{id, name, version, repo_url, tier, tags, description, verified, author, homepage}`.
- If user provided a keyword, match against `name`, `description`, `tags`
- If user wants "verified only", filter `verified=true`
- If user wants a specific `tier` (essential vs full-stack), filter
Default: don't filter, show everything ordered by `verified=true` first, then alphabetical.
Step 3 — Render results
### 🟢 PM Essentials (verified)
Agents, skills, routines para gestão de projetos com sincronização Linear.
v1.0.0 · tags: pm, linear, showcase · MIT · @EvolutionAPI/evonexus-plugin-pm-essentials
### 🟢 Pipedrive Suite (verified)
CRM integrado: pipeline, deals, health scores.
v0.4.1 · tags: crm, pipedrive · MIT · @user/evonexus-plugin-pipedrive
### Community: Custom Linear Sync
Fork extendido com webhooks do Linear.
v2.0.0 · tags: linear, webhooks · @community/evonexus-plugin-linear-webhooks
Use `🟢 verified` green badge, no badge for community.
Step 4 — Offer to install
If the user expresses interest in a specific plugin ("instala o Pipedrive", "quero esse aí"), hand off to `plugin-install` skill passing the `repo_url` directly.
Error handling
- Empty registry (nothing returned) — possible fresh registry or fetch error. Suggest direct install via git URL.
- `HTTP 503 marketplace_unreachable` — fetcher failed (offline or GitHub down). Offer to retry or install directly by URL.
Notes for the agent
- Don't invent plugins. Only list what backend returns.
- Verified badge is meaningful — `verified=true` means the Evolution team reviewed. Default recommendations to verified.
- If user asks "what's new", sort by installed_at descending (latest first).
- Respect tier: `tier=full-stack` plugins are bigger commitment (UI, backend), `tier=essential` are lighter.
Read more
name: plugin-marketplace description: 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", "plugins disponíveis para Y", "tem algum plugin que faz Z". metadata: category: plugins version: 1.0.0
Plugin Marketplace
Browse the curated `registry.json` from `github.com/EvolutionAPI/evonexus-plugins` plus community plugins. Help the user find what they need and hand off to `plugin-install` when they pick one.
How to use
Step 1 — Fetch registry
from dashboard.backend.sdk_client import evo
marketplace = evo.get("/api/plugins/marketplace")Cached 10min backend-side. If backend returns 503 `marketplace_unreachable`, tell the user the registry is offline and suggest direct install via git URL (`plugin-install`).
Step 2 — Filter by user intent
Each entry: `{id, name, version, repo_url, tier, tags, description, verified, author, homepage}`.
- If user provided a keyword, match against `name`, `description`, `tags`
- If user wants "verified only", filter `verified=true`
- If user wants a specific `tier` (essential vs full-stack), filter
Default: don't filter, show everything ordered by `verified=true` first, then alphabetical.
Step 3 — Render results
### 🟢 PM Essentials (verified) Agents, skills, routines para gestão de projetos com sincronização Linear. v1.0.0 · tags: pm, linear, showcase · MIT · @EvolutionAPI/evonexus-plugin-pm-essentials ### 🟢 Pipedrive Suite (verified) CRM integrado: pipeline, deals, health scores. v0.4.1 · tags: crm, pipedrive · MIT · @user/evonexus-plugin-pipedrive ### Community: Custom Linear Sync Fork extendido com webhooks do Linear. v2.0.0 · tags: linear, webhooks · @community/evonexus-plugin-linear-webhooks
Use `🟢 verified` green badge, no badge for community.
Step 4 — Offer to install
If the user expresses interest in a specific plugin ("instala o Pipedrive", "quero esse aí"), hand off to `plugin-install` skill passing the `repo_url` directly.
Error handling
- Empty registry (nothing returned) — possible fresh registry or fetch error. Suggest direct install via git URL.
- `HTTP 503 marketplace_unreachable` — fetcher failed (offline or GitHub down). Offer to retry or install directly by URL.
Notes for the agent
- Don't invent plugins. Only list what backend returns.
- Verified badge is meaningful — `verified=true` means the Evolution team reviewed. Default recommendations to verified.
- If user asks "what's new", sort by installed_at descending (latest first).
- Respect tier: `tier=full-stack` plugins are bigger commitment (UI, backend), `tier=essential` are lighter.
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