plugin-update

Update installed EvoNexus plugins to newer marketplace versions with migration safeguards.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill plugin-update-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-update
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/plugin-update
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill plugin-update-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updating plugins manually can break setups, miss required migrations, or leave the system in an inconsistent state when versions change.

Core Features & Use Cases

  • Finds the latest plugin release by comparing the installed plugin version against the marketplace version.
  • Previews what will change by surfacing changelog/release notes, new required environment variables, and upcoming migrations impact before execution.
  • Performs a safe update flow by running the full install/update pipeline with safeguards and clear error guidance for common failure modes.
  • Supports typical user intent such as “update/upgrade/bump plugin X” to the newest available version.

Quick Start

Ask your assistant to update the plugin "my-plugin" to the latest available version in EvoNexus.

Frequently Asked Questions about plugin-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely upgrade an EvoNexus plugin to a newer version?

To safely upgrade an EvoNexus plugin, the update process compares your installed version against the marketplace release, previews changelog and migration impacts, and requires explicit confirmation before applying the update.

What happens if I try to update a missing plugin or one that is already the latest version?

If the plugin is already the latest version or missing from the installation, the update process detects this by fetching current metadata and halts execution, providing clear error guidance instead of proceeding with the update.

Can I preview environment variable changes and release notes before a plugin update?

Yes, before executing a plugin update, the process surfaces release notes, new required environment variables, and upcoming migration impacts so you understand exactly what changes will occur.

How are migration-chain issues and HTTP errors handled during a plugin version upgrade?

Migration-chain issues and HTTP 404, 409, or 500 outcomes are handled by invoking the backend update endpoint with correct error handling, ensuring the system avoids inconsistent states and provides clear failure guidance.

Do I need to manually run database migrations after bumping an EvoNexus plugin?

No, bumping an EvoNexus plugin handles migration scenarios automatically by surfacing the migration impact beforehand and running the full update pipeline with safeguards to preserve configuration consistency.

What is the safest way to handle version upgrades for installed marketplace plugins?

The safest way to handle version upgrades for installed marketplace plugins is to fetch current and latest metadata, review the changelog and migration impact, and require explicit confirmation before invoking the backend update endpoint.