Home › Rules › Antigravity plugins

Google Antigravity plugins: install, marketplace and skills

From Google's own Antigravity docs (Plugins, Marketplace, Agent skills and Customization discovery), checked Nov 6, 2026. Sources below.

• Guide
• Antigravity
• Plugins
• Marketplace
• Skills
• Beginners

Short answer: an Antigravity plugin is a versioned pack that can hold skills, MCP servers, custom agents, rules and lifecycle hooks in one place. You install curated plugins from the Antigravity Marketplace (official name antigravity-plugins-official), from a GitHub URL, or from a local folder. In the CLI that's agy plugin install; in the App it's Customizations → Marketplace. Skills that come from a plugin are named plugin:skill, so they don't clash with your own. This page goes deeper on install and the marketplace. For writing a single skill folder, see Google Antigravity skills.

Plugin vs skill

Google's plugins doc says plugins "package reusable skills, Model Context Protocol (MCP) servers, custom agents and subagents, rules, and lifecycle hooks into a single versioned unit." A skill on its own is the smaller piece. You can ship skills without a plugin; a plugin is how you ship several customizations (and often MCP) as one install.

How to install a plugin

From your shell (agy plugin install)

Outside an interactive CLI session, Google's docs show three sources. Marketplace installs need an active agy sign-in, and the only marketplace name supported today is antigravity-plugins-official:

# Official marketplace (needs an active agy sign-in)
agy plugin install firebase@antigravity-plugins-official
# Bare name defaults to @antigravity-plugins-official
agy plugin install firebase

# From a GitHub repository URL
agy plugin install https://github.com/<owner>/<repo>

# From a local plugin folder
agy plugin install /path/to/local/plugin

Google's example output for a marketplace install is: Installed plugin "firebase" from antigravity-plugins-official.

Inside the CLI (/plugin)

In an interactive Antigravity CLI session, type /plugin (alias /plugins) to open the Plugins Manager. Tab switches between Installed and Discover. On Discover you can search the catalog, open details, install with Ctrl+S, or pick "Install from local directory." You can also run the same actions inline without opening the panel:

/plugin install firebase@antigravity-plugins-official
/plugin install /path/to/local/plugin
/plugin list
/plugin enable <plugin-name>
/plugin disable <plugin-name>
/plugin uninstall <plugin-name>

In the Antigravity App

1. Open the Customizations tab in the left sidebar (below Automations).
2. Choose the Marketplace tab to browse curated plugins, or Installed to manage what you already have.
3. Click a card to see Overview, Skills, MCP, Agents and Rules tabs, starter prompt chips, and the plugin README, then click Add (or click + on the list).
4. On Installed, use the ⋮ menu (or the plugin card) to enable, disable, configure or uninstall.

Google notes that plugins you install in the App are "automatically updated and shown" in the CLI's Installed tab (cross-surface sync).

Drop a plugin folder in place (App, CLI or IDE)

• One project: put the plugin folder in .agents/plugins/ at the workspace root. It only activates in that project.
• Every project on this machine: put it in ~/.gemini/config/plugins/.

The standalone Antigravity IDE uses the same two locations. The CLI stages marketplace and agy plugin install installs under ~/.gemini/config/plugins/<plugin_name>/.

Official marketplace vs GitHub vs local

Google's Marketplace page also points to a separate interest form if you want to submit a validated plugin for listing, and to Build with Google for curated Google stacks (Firebase, Flutter, Chrome DevTools, BigQuery and others) that you can enable during onboarding or under Settings → Customizations → Build with Google Plugins in the App.

After install: skills, MCP, agents, rules

• Skills: at session start Antigravity loads only each enabled plugin skill's name and description, then reads the full SKILL.md when your prompt matches. Or type /<skill-name> (Google's examples include /dart-add-unit-test and /hello). In the App, a plugin's detail page can also show suggested prompt chips you click to start a guided task.
• MCP tools: ask the agent to use the connected service. Bundled tools are namespaced as <plugin-name>_<server-name>. Google's docs name examples such as Firebase, Dart and Flutter, Stripe, Datadog, Figma and Jira.
• Credentials: if a plugin needs API keys or config variables, a CLI marketplace install leaves it disabled until you configure it. Toggling it on in Installed (or pressing Space in the CLI Installed tab) opens a setup dialog. OAuth plugins without required variables install enabled and prompt in the browser when the MCP server connects.
• Custom agents / subagents: with subagent: true (default), the main agent can hand specialized work to the plugin's subagents. With mainAgent: true (default), you can pick the plugin agent as your session agent (App agent selector, CLI /agents, or agy --agent <name>; agy agents lists them).
• Rules and hooks: always-on and triggered plugin rules apply while the plugin is enabled. Bundled PreToolUse, PostToolUse, SessionStart and Stop hooks run in the background.

How plugin skills are named

Google's customization-discovery doc says skills from a plugin are named <plugin>:<skill>, so they don't conflict with your other skills. Our Antigravity skills page puts that as plugin:skill. Same idea: the plugin name is the prefix.

Priority for same-name skills (not plugins) is separate: your project skill beats one in ~/.gemini/config/, which beats a built-in skill. In the CLI, skills in ~/.gemini/antigravity-cli/skills/ and ~/.gemini/skills/ come first. Rules don't replace each other; Antigravity loads every rule it finds. More on writing skills and the SKILL.md format: Antigravity skills and SKILL.md examples.

List, enable, disable, uninstall

# What's installed (add --json for skill names and paths)
agy plugin list
agy plugin list --json

# Turn a plugin off without deleting it
agy plugin disable <plugin-name>
agy plugin enable <plugin-name>

# Remove it
agy plugin uninstall <plugin-name>

agy plugin list prints a short summary (enabled or disabled, version, source, component counts). Google's sample shows plugins such as firebase, flutter and gcalendar from antigravity-plugins-official. Pass --json for full skill, agent, rule, MCP server and hook names plus install paths. In the App, use the Installed tab's ⋮ menu. In the CLI panel, Space toggles enable/disable; Ctrl+S uninstalls from Installed (or installs from Discover).

Coming from Gemini CLI or Claude Code?

Google's plugins doc says you can import existing extensions from ~/.gemini/extensions/ or ~/.claude/plugins/ (or pass a directory):

# Import Gemini CLI or Claude Code extensions as plugins
agy plugin import
agy plugin import gemini
agy plugin import claude

The Gemini CLI migration guide also says agy plugin import gemini turns Gemini CLI extensions into plugins, while project skills still have to move from .gemini/skills/ to .agents/skills/ yourself. More: GEMINI.md examples and Antigravity skills (Gemini CLI section).

How this relates to workflows → skills

Plugins are a packaging layer. Skills replaced Antigravity's older workflows. Google's migration guide says workflows are deprecated (they still run for now), and the open Agent Skills standard is what to move to. In the Antigravity App 2.12.0 or later you can run /migrate-workflows (App only, not CLI or IDE). Skills load only their name and description up front, then the full instructions on demand. A plugin can then ship several of those skills (plus MCP and the rest) as one install. For the skill folder itself, see workflows vs skills.

Build your own (short)

A plugin is a directory with a plugin.json manifest (or .antigravity-plugin/plugin.json) plus optional skills, MCP configs, agents, rules and hooks. Google's starter manifest looks like this:

{
  "$schema": "https://antigravity.google/schemas/v1/plugin.json",
  "name": "my-first-plugin",
  "displayName": "My First Plugin",
  "version": "1.0.0",
  "description": "Starter plugin that bundles custom skills and MCP tools.",
  "logo": "assets/logo.svg",
  "suggestedPrompts": [
    "Run a readiness check on the current project"
  ]
}

Validate locally with agy plugin validate ./my-plugin or agy plugin validate --strict ./my-plugin (strict treats warnings as errors). Full authoring steps are on Google's Build plugins page. This guide stays on install and the marketplace.

Plugin or skill not loading?

• Is the plugin enabled? Check agy plugin list or Customizations → Installed. A plugin that needs API variables stays disabled until you fill them in.
• Right folder? Installed plugins live under ~/.gemini/config/plugins/<name>/. Manual drops go in that folder or .agents/plugins/. Each plugin needs a plugin.json in its folder (or in .antigravity-plugin/ / .gemini-plugin/).
• Skill file name: skills use SKILL.md with YAML frontmatter. Google's discovery doc also lists depth and manifest exclude patterns as common misses.
• CLI slash commands stale? After adding skills, run /skills reload or start a new conversation. /skills lists skills by source; /plugin opens the plugin panel.
• Name clash: another skill with the same name may be winning on priority. Plugin skills use the plugin:skill form, which avoids that clash with your own skills.

For rules files and triggers (separate from plugins), see Google Antigravity rules. For plan quotas and AI credits while you try plugins, see Google Antigravity limits.

Related

• Google Antigravity skills (skills folder, SKILL.md, workflows vs skills)
• Google Antigravity subagents (custom agents, agents folder, examples)
• Google Antigravity rules (examples, triggers, where the files go)
• Google Antigravity limits and AI credits (free tier, quotas, AI credits)
• SKILL.md examples for every tool (format, frontmatter, where the folder goes)
• Antigravity vs Claude Code vs Codex (prices, limits, rules files)
• GEMINI.md examples (Gemini CLI and Antigravity)
• Custom slash commands
• Every rules file format
• Free rules file generator

Sources

• Google Antigravity docs: Plugins
• Google Antigravity docs: Marketplace
• Google Antigravity docs: Agent skills
• Google Antigravity docs: Build plugins
• Google Antigravity docs: Customization discovery
• Google Antigravity docs: Build with Google
• Google Antigravity docs: Migrate from workflows to skills
• Google Antigravity docs: Migrating from Gemini CLI
• Google Antigravity docs: CLI reference
• Google Antigravity docs: FAQ
• Agent Skills specification

All plugin, marketplace and install steps checked Nov 6, 2026 on Google's own Antigravity docs. The Marketplace catalog changes often. If something here no longer matches, tell us at [email protected].