Agent Plugins defines a fixed directory layout with a lightweight `plugin.json`, optional `skills/`, and `mcp.json` for tool servers. The spec is intentionally narrow: it standardizes packaging and discovery while leaving installation, permissions, and UX decisions to individual clients.
For plugin and skill authors, the main payoff is less duplicated packaging work across different agent ecosystems. A portable plugin box means reusable skills and MCP servers can travel more cleanly between clients without per-platform wrappers drifting out of sync.
Developers can package skills under `skills/`, declare MCP servers in `mcp.json`, and publish a minimal `plugin.json` manifest that points to the shared schema. If you already ship skills or tool servers to multiple agent clients, this is the standard to watch for reducing packaging friction.
Read Original Post →