打包了，但不可移植：为什么符合智能体插件标准很罕见，以及为什么符合标准还不够
Packaged, But Not Portable: Why Conforming to the Agent Plugin Standard Is Rare, and Why Conforming Would Not Be Enough
浏览论文内容
中文总结 AI 辅助
针对编码智能体插件标准采纳率低（仅6.2%验证通过）及命名冲突（81%共享名称）问题，本文构建AgentPluginZoo语料库分析原因，提出需增加限定能力标识等四概念以支持组合，并建议使符合性可观察。
中文摘要 AI 辅助
编码智能体通过插件进行扩展：插件是可安装的捆绑包，包含技能、子智能体、命令、钩子和工具服务器。2026年7月24日，一项开放规范（Agent Plugins v1.0.0）标准化了此类捆绑包的布局和描述方式，以便一个插件能在任何智能体上运行。我们提出了从业者会问的两个问题：生态系统是否采纳了该标准，以及如果插件确实符合标准，是否足以使其与用户已安装的其他插件协同工作？我们通过构建AgentPluginZoo来回答这两个问题，这是一个具有来源追踪的语料库，包含30,655个仓库中的68,072个插件捆绑包，并随附其发现账本、评分代码和分析发布。仅有6.2%的插件通过验证，但差距是浅层的而非结构性的：96.6%的插件在添加一个缺失的样板字段后即可加载。真正的成本在别处。40.2%的插件可以加载，但规范要求客户端丢弃作者编写的字段，主要是关于插件所提供内容的声明。此外，符合标准对第二个问题毫无帮助：81%的导出能力的捆绑包与另一个插件共享名称，且没有命名空间或优先级规则来决定由哪个插件响应。本文主张，社区在组合需要模型时却标准化了打包格式，指出了该模型必须添加的四个概念——限定能力标识、声明的能力表面、优先级规则和插件间关系——并表明它们适合同一规范的附加v1.1配置文件，而非竞争性标准。随后为今天打包扩展的从业者和正在发展标准的人员提出了建议，其中最重要的是，符合性必须变得可观察，然后才能变得普遍。语料库和代码可在以下网址获取：https://this https URL
英文摘要
Coding agents are extended by plugins: installable bundles that ship skills, sub-agents, commands, hooks, and tool servers. On 24 July 2026, an open specification (Agent Plugins v1.0.0) standardised how such a bundle is laid out and described, so that one plugin could run on any agent. We ask the two questions a practitioner would ask of it: is the ecosystem adopting the standard, and if a plugin did conform, would that be enough to make it work alongside the other plugins a user has installed? We answer both by building AgentPluginZoo, a provenance-tracked corpus of 68,072 plugin bundles across 30,655 repositories, released with its discovery ledger, scoring code, and analysis. Only 6.2% validate, but the gap is shallow rather than structural: 96.6% would load after adding one missing boilerplate field. The real cost lands elsewhere. 40.2% would load while the specification obliges the client to discard fields their authors wrote, mostly declarations of what the plugin ships. Moreover, conformance settles nothing for the second question: 81% of capability-exporting bundles share a name with another plugin, with no namespace or precedence rule to decide which one answers. This paper argues the community standardised a packaging format when composition needs a model, names the four concepts such a model must add - qualified capability identity, a declared capability surface, a precedence rule, and inter-plugin relations - and shows they fit an additive v1.1 profile of the same specification rather than a competing standard. Recommendations follow for practitioners packaging extensions today and for the people evolving the standard, chief among them that conformance must be made observable before it can become common. The corpus and code are available at https://github.com/tezansahu/agentpluginzoo
发表机构
- Microsoft , India（微软印度）
机构由 AI 辅助整理，请以论文原文为准。
