agent-plugins-spec

Why we included this project

Teams building agent skills or MCP servers who want those components to travel between different agent clients, rather than living inside a single product, will find a concrete answer here. The project defines a minimal, vendor-neutral package format: a plugin directory with a small manifest plus skill or MCP configuration files, and a conforming client loads an extension just by reading the manifest. It is a specification, not a runtime, so its value is as a contract to design against when you are authoring distributable extensions or building a client that should consume them. The quick-start example takes minutes to grasp, and the versioned spec plus JSON schemas give implementers something concrete to validate against. If you are deciding how to package agent capabilities for reuse across tools, this is a short, readable baseline to start from.