ship-pluginlisted
Install: claude install-skill wardawgmalvicious/claude-plugins
# Ship a plugin: from a repo to an install that runs
A plugin that validates can still fail every user it reaches: its server
never starts, chat skips half of it, an update never arrives, or an
organization's members see it under a name nobody chose. Each failure is
silent, and each depends on **the route the plugin travels**. This skill
names the route first, then checks what ships, what each surface loads,
what `version` does, what an org sync fixes for good, and how to test
the install and the plugin's own skills without the user's real config.
It does not teach plugin layout or components: the Claude Code docs'
`plugins/components` page and `claude plugin validate` own those. A mod,
a pane or a hook module that changes Claude Code's own interface, is
`plugin-authoring`'s. Submitting to Anthropic's directory is out of
scope.
This skill is path-scoped to `.claude-plugin/*.json`, so it is listed
only once a session reads or writes a `plugin.json` or
`marketplace.json` in its working directory. A plugin's own repository
holds both; anywhere else it costs nothing.
Every claim below was read in the Claude Code and claude.com docs on
2026-10-22 against Claude Code 2.1.308, unless it says otherwise.
Past it, its `references/`, then the live page: code.claude.com by the
`claude-code-docs` MCP server or
`curl -s https://code.claude.com/docs/en/<page>.md`, and claude.com,
which that server does not cover, by
`curl -s https://claude.com/docs/<path>.md`. A live page that
contradic