Anthropic defined the standards inside Agent Plugins. So why isn’t it helping govern the format?

7.2 relevance

Standards governance for Agent Plugins involving major players, highly relevant to multi-agent systems and platform engineering.

AI/ML thenewstack.io

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For platform engineers building multi-agent toolchains, this means plugin portability remains aspirational: you still fork and maintain skills per client unless you align with both Anthropic's specs and the steering committee's evolving governance.

Key Takeaways

Audit your agent plugin dependencies against the Agent Plugins 1.0.0 manifest structure and track the MAINTAINERS file for governance shifts before committing to cross-client portability.

Anthropic defined the standards inside Agent Plugins. So why isn’t it helping govern the format?

Summary

Vercel's Agent Plugins 1.0.0, backed by AWS, Cursor, Microsoft, OpenAI, and Google, standardizes plugin packaging but defers skill format and wire behavior to Anthropic's Agent Skills and MCP specs, respectively. Anthropic donated MCP to the Linux Foundation's Agentic AI Foundation and open-sourced Agent Skills, yet sits on neither the technical steering committee nor the core maintainer roster. The spec explicitly provides only a 'small interoperability floor,' leaving clients to independently handle discovery, precedence, and component semantics.

Author

Janakiram MSV