Google backs the Agent Plugins standard

Google’s Antigravity-aligned developer blog published one of the clearest interoperability announcements of the week: Agent Plugins 1.0.0 now has Google as a core maintainer. The post argues for a small, vendor-neutral packaging standard that bundles Agent Skills and MCP servers into one portable directory. This matters because packaging is one of the main friction points in agent ecosystems today. If more clients accept the same manifest and layout, developers spend less time rewriting wrappers and more time shipping actual tool behavior.

Key Features or Updates

Google says Agent Plugins standardizes a plugin around a fixed directory layout, a shared plugin manifest, and separate MCP and skills components. The company also says support is already shipping in Agents CLI and Data Agent Kit, with more product integrations expected later.

Impact on Developers

This is the kind of plumbing announcement that can quietly reshape the agent tooling market. A shared package format lowers the cost of supporting multiple clients and makes it easier for plugin authors to distribute skills, MCP servers, and client-specific extensions without maintaining parallel packages.

How to use it

Developers building reusable agent tooling should read the spec and consider packaging new work around plugin.json, skills/, and mcp.json from the start. Even if you only target one client today, adopting the portable layout early reduces migration pain when you later expand to other IDEs, CLIs, or enterprise runtimes.