Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Vet an Antigravity plugin before the one-click install: what the bundle can do, and what Google does not check

Written November 1, 2026 · Edited November 4, 2026

For an Antigravity user about to one-click-install a plugin: inventory what the bundle can do and which accounts it signs into before the agent suggests the install for you, and judge the listing by what its own page shows.

What a plugin is

A plugin is a versioned, self-contained bundle defined by a plugin.json manifest. Google's plugin documentation states that a single plugin can bundle any combination of five components: skills, MCP servers, custom agents and subagents, rules, and lifecycle hooks. The parts install, update, and toggle on or off together as one unit. That is the whole point of the bundle, and the whole risk of the one-click install: one click can add instructions, external tools, account access, standing rules, and background agents at once. On 29 October 2026, the Antigravity changelog added partner plugins to the Marketplace, including Canva, Figma, Linear, Notion, Stripe, Supabase, and Vercel, on shelves including Developer Tools, Productivity & Project Management, and Cloud Hosting & Deployment, with a Featured spotlight for plugins such as Firebase, Notion, Linear, and Stripe. The same release added plugin sign-in right after adding a plugin, and agent-suggested installs: when a plugin would help with your task, the agent can find it in the Marketplace and suggest it with a card for adding it. Neither sign-in after adding nor agent-suggested installs is available yet for business and enterprise accounts.

What each part can do, from the plugin documentation: skills are task workflows, helper scripts, and reference docs, loaded on demand, with only the skill name and description loaded at session startup and the full instructions read when your prompt matches; MCP servers connect the agent to external APIs, databases, and developer tools, and their tools are namespaced as <plugin-name>_<server-name>; custom agents and subagents are specialized agents with their own system prompts, model tiers, and tool allowlists, and can run as background subagents or as your primary session agent; rules are persistent coding conventions, constraints, or file-scoped instructions that apply automatically whenever the plugin is enabled; lifecycle hooks are shell commands or prompt evaluations for events such as PreToolUse, PostToolUse, SessionStart, and Stop, which run automatically in the background while the plugin is enabled and can inspect, block, or augment tool calls. A plugin can also declare required configuration variables, such as an API token or workspace URL, or an OAuth 2.0 sign-in flow. The changelog states that plugin pages now show the plugin's developer and version, with links to its website and repository, and that the Marketplace tab and the pages of plugins from third-party developers show a notice about third-party developer tools, with a link to the Google Privacy Policy. Nothing in the changelog or the plugin documentation describes a Google review, audit, or signing check for Marketplace plugins. The page shows a developer, a version, links, and a third-party notice, and nothing more than that. Do not treat a listing as an approval.

Before you start

Pick one plugin and do not install it yet. Open its Marketplace page and keep it open for the whole pass. You need its developer, version, website and repository links, and the contents of its Overview, Skills, MCP, Agents, and Rules tabs. If any tab is empty or missing, that is a finding, not a pass: an empty tab means the page does not tell you what that part of the bundle contains. Work in a throwaway workspace for the first install, not in a live project, so a plugin that turns out to be wrong touches nothing you care about.

Steps

  1. Record the page facts. On the plugin's page, write down the developer name, the version, and the website and repository links. Follow the repository link and confirm it leads to the project the page names. A page with no repository link, or a link that leads somewhere else, ends the pass: do not install a bundle whose author you cannot trace from its own page.
  2. Inventory the five parts. Open each tab on the plugin's page and list what it contains, in plain words: each skill and what it teaches the agent to do; each MCP server and which external service it reaches; each custom agent or subagent and whether it can run in the background; each rule and when it applies; each hook and which event it runs on. For example, Google's Marketplace announcement describes the Stripe plugin as connecting through the Stripe MCP server to look up customers, payments, and subscriptions, search Stripe documentation, and build or debug payment integrations. That description comes from Google's announcement, not from the Stripe plugin's own page: for the plugin you are installing, the inventory must come from its own page, and anything the page does not name is unknown, not assumed absent.
  3. Check the sign-in before you give it an account. Look for the Accounts tab on the plugin's page, and read whether the plugin connects to an account, what kind of sign-in it uses, and what variables it asks for. Plugins that connect to an account have an Accounts tab where you can add, reconnect, or disconnect accounts, and adding one from a shelf, the Featured spotlight, or its page takes you straight to its sign-in. If a plugin declares required variables, such as an API token, installing it from the command line leaves it disabled until configured, and toggling it on opens a setup dialog for each variable. If it uses OAuth 2.0 without required variables, it installs enabled and prompts you in the browser to complete sign-in when its MCP server connects. Decide which account you will sign in with before installing, and use an account with the least access the plugin needs. If the page does not state what access the sign-in grants, treat that access as unknown and check the service provider's own documentation before signing in.
  4. Do not accept an agent-suggested install unread. If the agent suggests a plugin with an install card, the card is a shortcut, not a vetting result. Run steps 1 to 3 on the suggested plugin's page first. A suggestion means the agent judged the plugin relevant to your task. It says nothing about what the bundle contains or what its sign-in can reach.
  5. Install in the throwaway workspace and list what loaded. Install the plugin, then run agy plugin list and confirm the plugin appears with the version from step 1 and the enabled state you expect. Check the MCP tools it registered under their namespaced names, and confirm the skills, agents, rules, and hooks you inventoried are the ones present. If anything loads that was not in the inventory, stop and remove the plugin: the bundle on your machine differs from the bundle you read about.
  6. Test one task, then decide. Give the agent one small task that uses the plugin, on throwaway data, and watch which tools it calls and what it sends. Then write down the decision: keep, keep with the plugin disabled except when needed, or remove. A plugin that stays enabled keeps its rules and hooks active and its subagents available for automatic delegation. Disabling it when you are not using it is the normal state for a plugin you trust only for one job.

What can go wrong

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Vet a skill before you install it · SkillSpector · Export Jules work and rebuild scheduled tasks before the shutdown