ref-sp-agents-plugin-marketplaceslisted

# Plugin Marketplaces ## Purpose Turn a repo that already holds skills into an **agent plugin** published through a **plugin marketplace**, without restructuring the repo and without leaking skills that were never meant to leave it. A plugin is a **cross-client format**, not a Claude-only one. Claude Code, GitHub Copilot CLI, and VS Code all install plugins, all read a `plugin.json`, and all consume the same `SKILL.md` standard. One repo, published once, serves all three — see [Cross-client compatibility](#cross-client-compatibility). This skill is scoped to **distributing skills**. It is not a general plugin-authoring guide: hooks, MCP servers, LSP servers, agents, and commands are plugin components too, but they are out of scope here — consult the upstream references for those. What this skill owns is the part that is genuinely easy to get wrong: **which directories get published, how paths survive the install cache, and how a release reaches an existing user.** ## When to use this skill - Packaging an existing skills directory as a plugin. - Creating a `marketplace.json` catalog, or choosing where to host it. - Deciding which skills are allowed into a published plugin. - Making one published plugin installable from Claude Code, Copilot CLI, and VS Code. - Cutting a release, or choosing between pinned and rolling versioning. - Debugging an installed plugin that is missing skills, or that will not update. ## Scope boundaries This skill owns **publishing** — the manif