Mage Remote Run Plugin

Use this skill to work on the mage-remote-run extensibility model. It covers JavaScript plugins, configuration injection, static plugin configuration, lifecycle events, MCP behavior, and virtual commands.

Workflow

1. Identify whether the task needs executable JavaScript, static configuration, or both.
2. Read the matching reference file before editing:
   • references/plugin-management.md for registration and distribution behavior.
   • references/plugin-runtime.md for plugin module shape, runtime context, events, connection guards, MCP notes, and built-in lib helpers.
   • references/plugin-configuration.md for config mutation, saveConfig(), and static config files.
   • references/virtual-commands.md for config-driven REST command definitions.
3. Prefer the lowest-complexity extension that solves the request:
   • Use a virtual command when the task is a declarative REST request.
   • Use a plugin when the task needs custom logic, event listeners, or dynamic behavior.
   • Combine both when a plugin needs runtime logic plus reusable command definitions.
4. Match functionality to supported connection types. Guard commands when they do not work across all profile types.
5. When the task involves MCP, remember that plugin commands become MCP tools automatically and execution runs in isolated contexts.