What
In /plugin, removing a plugin that failed to load now tells the uninstall step to remove it anyway, even if a settings file still has the plugin switched on. Where the plugin is installed (for example for your user or for a project) is now worked out in the same step.
Why
Broken plugins should be easier to get rid of.
Names in the bundle/plugin
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Set up a skills repository Claude can update touched a line naming /plugin after this was published.
To upload instead, in [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), click **Add**, choose **Upload a plugin**, and upload a `.zip` or `.plugin` archive of up to 200 MB. The archive h…claude-tag/admins/skills-repo see the edit
Confirmed since
Anthropic's documentation has since written up /plugin, on MCP, plugins, skills, and hooks.
| `.claude-plugin/plugin.json` | Plugin manifest (name, description, version). Required unless a top-level `SKILL.md` serves as the manifest; see the note below this table. A directory with neither is ignored. |third-party/claude-desktop/extensions see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is unclear what happened before when settings still enabled a failed plugin you tried to remove.
Anthropic's documentation agrees
Anthropic's documentation has since written up /plugin, on MCP, plugins, skills, and hooks.