Direct Answer: How Do You Install a Plugin in Claude Code?
To install a plugin from a marketplace in Claude Code, execute these three steps in your interactive terminal session:
- Add the Marketplace: Run
/plugin marketplace add <owner/repo>to register the source repository. - Install the Plugin: Run
/plugin install <plugin-name>@<marketplace-name>to install the package. - Reload Plugins: Run
/reload-pluginsto load skills, commands, and subagents into your active terminal.
Step 1: Adding the Marketplace Registry
A marketplace is a GitHub repository that hosts a catalog file located at .claude-plugin/marketplace.json. When you register a marketplace, Claude Code fetches the catalog and registers its published plugins for installation.
In your Claude Code terminal, type:
/plugin marketplace add owner/repo-name
Example: To add the Alew3 media skills marketplace:
/plugin marketplace add alew3/skills
Anthropic also provides an official marketplace (claude-plugins-official), which is enabled automatically when you first launch Claude Code.
Step 2: Choosing Your Installation Scope
When installing a plugin, Claude Code prompts you to select one of three installation scopes:
| Scope | Flag | Description | Best For |
| --- | --- | --- | --- |
| User Scope | --user | Installed globally in ~/.claude/plugins/. Available across all projects on your machine. | Personal utilities, shell helpers, default git workflows. |
| Project Scope | --project | Saved in your project repository's .claude/ configuration. Shared with teammates via Git. | Team linters, repository-specific review agents, project MCPs. |
| Local Scope | --local | Active only within the current workspace on your machine, without committing files to Git. | Private experimentation or testing client credentials. |
Run the installation command:
/plugin install <plugin-name>@<marketplace-name>
Example: To install the buildatscale developer tools from the buildatscale-claude-code marketplace:
/plugin install buildatscale@buildatscale-claude-code
Step 3: Reloading Your Active Session
Unlike traditional CLI tools that require restarting your terminal, Claude Code allows in-session reloading:
/reload-plugins
Once reloaded, all slash commands declared in the plugin's commands/ directory become immediately callable with tab-completion (e.g., /pr, /commit), and any declared subagents become available.
How to Manage, Update, and Remove Plugins
Inspecting Installed Plugins
To view an interactive list of all active packages, their scopes, and enabled components, run:/plugin
Navigate to the Installed tab using your arrow keys to review package versions and toggle plugins on or off.
To view a plain CLI list of enabled plugins:
/plugin list --enabled
Updating a Plugin
To pull the latest release of an installed plugin:/plugin update <plugin-name>@<marketplace-name>
Uninstalling a Plugin
To cleanly remove a plugin and deactivate its hooks and commands:/plugin uninstall <plugin-name>@<marketplace-name>
Local Development: Testing Plugins Without Installing
If you are developing your own plugin or reviewing an open-source repository before committing it, you can load it temporarily for a single session using the --plugin-dir flag:
claude --plugin-dir ./path/to/my-plugin
To validate that your plugin's .claude-plugin/plugin.json manifest and folder structure meet official standards before sharing:
claude plugin validate ./path/to/my-plugin
Frequently Asked Questions
What happens if two plugins define the same slash command?
Claude Code resolves command collisions based on installation scope priority (project overrides user). If two plugins in the same scope define identical command names, you can qualify the invocation or disable the conflicting package in /plugin.
Can plugins execute commands without asking?
Plugins withhooks can run pre-tool and post-tool checks deterministically. However, Claude Code continues to enforce its standard approval prompts for bash commands, file modifications, and network requests unless explicitly bypassed by user flags.