AI HOT (Curated Pool)Aug 7, 2026, 00:53 UTC+8

Agent Plugins 1.0.0: Google, Amazon, Microsoft, and others ship a unified agent plugin spec

Agent Plugins 1.0.0 发布：谷歌、亚马逊、微软等支持的统一智能体插件规范

Agent Plugins 1.0.0 is an open, vendor-neutral spec that packages Agent Skills and MCP servers into a portable directory. Google joins Amazon, Cursor, Microsoft, OpenAI, and Vercel as a core maintainer. The format is deliberately minimal: plugin.json declares only a name and schema, skills live in skills/, and MCP servers go in mcp.json with explicit transport types. v1 intentionally omits install mechanisms, permission models, and sandboxing—those are left to each client. The post also notes that a single skill or single MCP server doesn't need a plugin; the format earns its keep when components must travel together.

Why it matters: Five major players jointly shipping a unified agent plugin spec — strong cross-source signal with real ecosystem impact. Capped at 78 because it's a spec release, not a runnable product; adoption remains to be seen.

Read the original ↗Export Markdown

Take

This is worth a click because it fixes a real pain point: you build a skill and an MCP server, it works on one client, then you try a second client and the directory layout, manifest format, and MCP config are all different. You fork, maintain two copies, and they drift. Agent Plugins is deliberately minimal—a fixed directory structure, a plugin.json that only declares a name and schema version, skills in skills/, MCP servers in mcp.json with explicit transport types. No discovery paths, no precedence order, no inline declarations. Components fail independently.

What v1 deliberately omits is more telling than what it includes: no install mechanism, no permission model, no sandboxing. All left to each client. So you can package and distribute now, but you'll need to handle the security boundary yourself. Google joining as a core maintainer rather than launching their own thing signals they're aligning with the industry here instead of fragmenting further.

One detail I appreciate: the post explicitly says a single skill or single MCP server doesn't need a plugin. The format earns its keep only when components must travel together. That's a refreshingly pragmatic line to draw—they're not trying to make this the answer to everything.

Source: AI HOT (Curated Pool) · developers.googleblog.com
Published: Aug 7, 2026, 00:53 UTC+8 · Aug 7, 2026