| name | plugin |
| description | Manage Antigravity plugins with safe install, doctor, remove, and lightweight index workflows. |
| argument-hint | <list|show|doctor|install|remove|validate|index> [args] |
/omagy:plugin
Use this skill to inspect, install, validate, diagnose, and remove Antigravity
plugins through Omagy's safe lifecycle wrapper.
This is not a marketplace. It is a plugin lifecycle manager and lightweight
index client that delegates installation to Antigravity CLI's native
agy plugin commands.
Commands
omagy plugin list --json
omagy plugin show <name> --json
omagy plugin doctor <name> --json
omagy plugin validate <path> --json
omagy plugin install <path-or-git-url> --json
omagy plugin remove <name> --json
omagy plugin index add <name> <url> --json
omagy plugin index list --json
omagy plugin index search <query> --json
omagy plugin index install <index>/<plugin> --json
Slash Workflow
/omagy:plugin list lists installed plugins.
/omagy:plugin doctor without a name must not ask an interactive question.
Print available plugin names and the exact follow-up command.
/omagy:plugin remove without a name must not ask an interactive question.
Print available plugin names and the exact follow-up command.
/omagy:plugin install <target> prints an install plan only. It must clearly
say that no files were written and include the exact next command to copy if
the user wants to continue.
/omagy:plugin install <target> confirm <generated-confirmation> applies the
exact install plan shown in the previous step.
/omagy:plugin remove <name> prints a removal plan only. It must clearly say
that no files were removed and include the exact next command to copy if the
user wants to continue.
/omagy:plugin remove <name> confirm <generated-confirmation> applies the
exact removal plan shown in the previous step.
Do not use agy's interactive Question UI for plugin install/remove. Do not
offer Write-in prompts.
Do not ask the user to understand or manually construct confirmation tokens.
Always present a complete copyable slash command, for example:
/omagy:plugin remove example-plugin confirm abc123...
Safety Rules
- Do not use
--yes or --force.
- Do not overwrite conflicts automatically.
- Treat plugins with hooks as high risk and call that out in the plan.
- Treat plugins with MCP servers as capable of launching local processes or
connecting to remote services.
- Never remove native user skills or global MCP config when removing a plugin.
- After installing, run
omagy plugin doctor <name> --json.