hermes-plugin-operationslisted

# Hermes Plugin Operations Use this skill when a user asks to install, reinstall, remove, migrate, enable, disable, or troubleshoot a Hermes plugin. This is a class-level companion to the protected `hermes-agent` skill, focused on practical plugin lifecycle work. ## Workflow 1. **Load `hermes-agent` first when available.** Use it for the current CLI surface and safety notes. Treat live docs/README from the target plugin repo as authoritative for plugin-specific install steps. 2. **Inspect current state before changing anything.** - `hermes plugins list --plain --no-bundled` - Check `$HERMES_HOME/plugins` (default `~/.hermes/plugins`) for old files/directories matching the plugin's old and new names. - Check `$HERMES_HOME/config.yaml` for `plugins.enabled` and stale `plugins.disabled` entries. 3. **For reinstall/migration, remove old artifacts deliberately.** - If an old plugin was a single file, remove both the `.py` file and matching `__pycache__` bytecode. - If an old plugin was a directory, remove the whole old plugin directory. - Remove the old plugin name from `plugins.enabled`; preserve unrelated enabled plugins. 4. **Follow the plugin's current installer or README exactly.** For standalone third-party plugins, Hermes expects a directory containing `plugin.yaml` under `$HERMES_HOME/plugins/<plugin-name>/`, then the plugin name in `plugins.enabled`. 5. **Verify installation, not just copy files.** - `hermes plugins list --plain --no-bundled` shoul