plugin-developmentlisted

# Plugin Development ## Purpose Package a coherent set of agent capabilities — skills, slash commands, hooks, and MCP servers — into something another person can install in one step and that works immediately. ## When to Use - Distributing skills or commands to a team or publicly. - Bundling a set of related capabilities that belong together. - Publishing to a plugin marketplace. - Versioning and updating an existing plugin. ## Capabilities - Plugin structure and manifest. - Bundling skills, commands, hooks, agents, and MCP servers. - Versioning and compatibility. - Testing a plugin before distribution. - Marketplace publication. ## Inputs - The capabilities to bundle, and their coherence as a set. - The audience and what they already have installed. - Any external dependencies: MCP servers, API keys, binaries. ## Outputs - A plugin that installs cleanly and works without further configuration. - A manifest with accurate metadata. - Documentation of what it provides and what it requires. ## Workflow 1. **Bundle around a coherent purpose** — A plugin is a set of capabilities that a specific kind of user needs together. A grab-bag of unrelated skills is a worse experience than several focused plugins. 2. **Write the manifest accurately** — Name, description, version, and what it provides. This is what users see when deciding whether to install. 3. **Declare the dependencies honestly** — If a skill requires an MCP server, an API key, or a binary on the PATH, say so p