Install
/plugin install {plugin-name}@claude-plugins-officialWho this is for
Fits people already using Claude Code who want to install plugins from this Anthropic-managed curated directory. Official text: this is a high-quality Claude Code plugin directory; plugins can be installed directly from that marketplace through Claude Code’s plugin system.
Better fit: people who have already seen a concrete plugin name in the directory and will judge trust themselves before install. Official text names no plugin on this page. Poor fit: anyone who wants to skip the trust judgment, or treat directory plugins as software Anthropic has guaranteed.
Before starting, you must be able to run the /plugin install command inside Claude Code. Do not apply this command to other environments that were never written.
Finish a first try in 3 minutes
Follow only the official Claude Code plugin-system path. The first try installs one plugin you have already seen in the directory and trust; do not enable extra software of unclear origin yet.
Precondition: the current environment can already use Claude Code. You have a real plugin name in hand; the original page uses the template {plugin-name} and gives no concrete name to copy. Do not invent plugin names or skill paths.
Install location: install in a Claude Code session using the official format.
/plugin install {plugin-name}@claude-plugins-official
Replace {plugin-name} with the name you saw in the official directory. Official repository:
https://github.com/anthropics/claude-plugins-official
Low-risk trigger: read that plugin’s notes before install and confirm you trust it. Official requirement: confirm trust before install, update, or use. Anthropic does not control MCP servers, files, or other software inside a plugin, and cannot verify that they work as expected or will not change later. So the first try should not touch production data or external systems; after install, first check that it appears in the plugin list.
Success: the plugin installs under its name (slug) and you can see it in the session. If you get plugin-not-found, first check whether the name was changed; do not invent a new name and retry.
Usage cases
Case 1: Install a trusted plugin from that marketplace. In Claude Code run /plugin install {plugin-name}@claude-plugins-official. Fits people who already chose a plugin and only want the official plugin system. Evidence gives only this template, no example plugin. After install, first confirm the plugin appears; if it would start an MCP server or change files, stop and check, then continue.
Case 2: Keep a published plugin’s name unchanged. Official text: once a plugin is published, name must not change, because users install by that slug; a rename turns install into plugin-not-found. Fits people who already installed a directory plugin and plan to update or keep using it. Before an update, confirm you still trust it. Do not change the official name for “easier to remember.”
Usage limits
The only officially named install format is /plugin install {plugin-name}@claude-plugins-official. Do not fill in other marketplace names, plugin names, or skill paths yourself.
Before install, update, or use, you must trust that plugin. Anthropic does not control the MCP servers, files, or other software inside it, and cannot guarantee unchanged behavior.
A published plugin’s name cannot change, or existing installs will report plugin-not-found.
Official text writes the install path only on Claude Code’s plugin system; it gives no steps for other environments and names no concrete plugin inventory on this page.