Google Antigravity Plugins Guide

Google Antigravity is Google’s agent-first platform for building software, with an app, an IDE, and a CLI called agy. A plugin packages several add-ons into one versioned unit you can install and share.

Skills

Instructions and resources for specific tasks

MCP servers

Connections to outside tools and data

Agents

Custom agents and subagents

Rules

Standing guidance for the agent

Hooks

Scripts that run on events, such as before or after a tool call

One plugin can teach the agent a whole workflow, not just one trick.

• Browse the Marketplace in the Antigravity app under Customizations
• Official plugins include Firebase, Flutter, and Google Calendar
• Plugins connect to services such as Stripe, Datadog, Figma, and Jira
• Community plugins on GitHub

• App: open Customizations, pick a plugin, and install
• CLI: type /plugin inside agy to open the plugin manager
• Shell: agy plugin install firebase@antigravity-plugins-official
• From GitHub: agy plugin install followed by the repository URL
• From a folder: agy plugin install followed by a local path

Workspace

Put the plugin in .agents/plugins/ in your project; active only there

Global

Put it in ~/.gemini/config/plugins/; active in every workspace

Use workspace plugins for project-specific tools and global plugins for things you use everywhere.

agy plugin list

See what is installed

agy plugin enable / disable

Turn a plugin on or off without deleting it

agy plugin uninstall

Remove a plugin

agy plugin validate --strict

Check a plugin before sharing it

agy --agent <name>

Start a session with a plugin’s agent

Run agy plugin import gemini to bring Gemini CLI extensions across, or agy plugin import claude to import Claude Code extensions.

• Plugins that need settings stay off until you fill them in
• Turning them on opens a setup dialog
• Plugins using OAuth ask you to sign in through your browser when they connect
• Store API keys in the configuration, never in shared files

• Create a folder with a plugin.json file at the root
• Add a name, display name, version, description, and logo
• Add skills, an MCP config, agents, rules, or a hooks.json file
• Add suggested prompts so people know how to use it
• Validate it, then test it in a workspace

• Your team’s coding standards as rules
• A deploy checklist as a skill
• A connection to your issue tracker through MCP
• A hook that runs tests after each edit

• Hooks run shell commands automatically while a plugin is enabled
• Read a plugin’s files before enabling it
• Prefer official and well-known plugins
• Give MCP servers the smallest permissions they need
• Disable plugins you are not using