Antigravity plugins are installable bundles that give Google's Antigravity agents new skills, tools and rules in one go, and the plugin directory for finding them launched on October 29, 2026. You install them from the Antigravity App or the CLI, and each one can carry up to five kinds of add-on that switch on and off together.
Before the directory, connecting an agent to an outside system meant setting up MCP endpoints, environment variables, skills and subagents by hand for every repository. The directory gathers third-party and Google-built plugins in one place across the App and the CLI. Here's what goes inside a plugin, who launched with one, and what to check before you click install.
The five things inside a plugin
A plugin is a versioned, self-contained bundle defined by a plugin.json manifest. Everything in it installs, updates and toggles together.
| Component | What it does | Format |
|---|---|---|
| Skills | Packages of knowledge and multi-step procedures, loaded only when your request needs them | A SKILL.md file |
| MCP servers | Connect the agent to outside APIs and tools | Remote Streamable HTTP or local stdio |
| Rules | Persistent guardrails and conventions, such as query cost limits or read-only modes | Markdown |
| Hooks | Deterministic shell commands at session start, before and after a tool call, and on stop | Shell commands |
| Custom agents | Specialised personas with their own system prompt, tool allowlist, model choice and command policies | Markdown |
Two details matter for anyone responsible for security. Hooks run outside the model's reasoning, so a team can use them to block sensitive tool calls or redact secrets every time, not just when the model remembers. And a plugin's custom agent can either be your main session agent or run in the background in an isolated context window, for jobs such as a security audit or a log investigation. Rules can stay active whenever the plugin is enabled, or load only when the agent decides they're relevant.
Launch partners and the catalogue
The launch announcement names Atlassian, Canva, CrowdStrike, Databricks, Datadog, Dropbox, Figma, monday.com, Ping Identity, SentinelOne, Stripe and Unity as launch partners. The catalogue is grouped by category, including Google Workspace, cloud hosting, design, productivity, developer tools and business.
Beyond the partners, the directory lists Google Docs, Sheets, Slides, Calendar and Drive, along with Netlify, Vercel, Wix, WordPress, Trello, Notion, Linear, Zapier, Semrush and Zoho CRM. For a marketing or operations team, that's the interesting part: many tools you already use appear as installable plugins.
Installing one in the App or the terminal
- In the Antigravity App, open the Customizations panel and the Plugins tab. In the CLI, run /plugin (or /plugins) to open the plugin manager with its Installed and Discover tabs.
- Search the catalogue and open a plugin card, or press Enter in the CLI, to see exactly what it bundles.
- Click + in the App, or press Ctrl+S in the CLI, to install. Space toggles a plugin on or off in the CLI.
- Enter any tokens or workspace URLs it asks for, or finish the OAuth sign-in when your browser opens.
- Ask for the task in plain words, or type /skill-name to trigger a specific skill.
- Toggle the plugin off when you don't need it.
Plugins you install in the App sync automatically to the CLI's Installed tab. From the shell, agy plugin install followed by the plugin name installs one, agy plugin list shows what's installed, and agy plugin validate checks a plugin.json and its MCP configuration before you share it. You can also install from a GitHub repository or a local directory, build and publish your own, and technology partners can submit one through a partner interest form.
Credentials, OAuth and when a plugin stays off
This is the behaviour that trips people up. If a plugin needs an API key or other variables and you install it with the CLI, it stays disabled until you configure it. Toggling it on opens a setup dialog for each variable. OAuth plugins work the other way round: they install enabled and open your browser to finish sign-in when the server connects.
Plugins can ask once for the tokens or workspace URLs they need, and the tools they bring are scoped to the plugin's lifecycle. Once installed, MCP tools appear under names in the form plugin-name_server-name, and plugin agents hand work to background subagents by default. You can make one the primary agent with agy --agent followed by the agent name.
Skills as an open standard
Google describes skills as an open standard: a folder with a SKILL.md file carrying a name and a description in YAML frontmatter. The description is required, and it's what the agent reads to decide whether to apply the skill. Antigravity looks in .agents/skills by default and still supports .agent/skills. If the format is new to you, my explainer on what agent skills are covers the idea across tools.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Skills follow progressive disclosure. The agent sees only names and descriptions on every turn, reads the full instructions when a skill looks relevant, then follows them. That keeps the context window focused, and you can name a skill in your prompt to make sure it's used. Google's own tips for writing one:
- Keep each skill focused on one job.
- Write the description in the third person, with keywords that signal when to use it.
- Treat helper scripts as black boxes the agent runs rather than reads.
The same SKILL.md idea sits behind Claude plugins too, which helps if your team runs both tools.
Treat an install like granting access
I'd treat every plugin install as giving someone access to your systems, not as adding a theme. A plugin can carry hooks that run shell commands and MCP servers that reach outside services, so I'd open the card, read what it bundles and check which accounts it connects before anyone clicks +. I'd also switch plugins off when a project doesn't need them, because the toggle is right there in both the App and the CLI.
If you're deciding which plugins your team should connect to an agent, and which accounts they should never touch, that's the kind of thing I help with. I run AI training and workshops for teams, and help businesses with AI enablement, AI automation and GEO, which is about getting your business seen and cited in AI answers. Most of that work is with SaaS marketing teams, telecom companies and small businesses. Here's how we can work together.
Frequently asked questions
When did Antigravity plugins launch?
The plugin directory launched on October 29, 2026, across the Antigravity App and the CLI.
What can an Antigravity plugin include?
Up to five things: skills, MCP servers, rules, hooks and custom agents. They're defined in a plugin.json manifest and install, update and toggle together.
Why is my Antigravity plugin disabled after installing it?
If a plugin needs an API key or other variables and you install it with the CLI, it stays disabled until you configure it. Toggling it on opens a setup dialog for each variable.
How do I install an Antigravity plugin from the terminal?
Run /plugin to open the plugin manager, or use agy plugin install followed by the plugin name. agy plugin list shows what's installed.
