Chapter 14 · CLI
Plugins and marketplaces: discovery and install
Plugins extend Claude Code with ready-made capabilities: commands, agents, hooks and more. They come from marketplaces, and before installing you should understand what they do and who stands behind them.
Video
Steps
- Discover plugins through the built-in marketplace or organization-approved sources, and read the docs before installing.
- Check what the plugin installs: which commands, hooks or permissions it requests, treating it like installing new code.
- After install, verify the components load and work in a new session, and remove plugins you do not use.
- In an organization, admins can define allowed marketplaces; follow the policy instead of bypassing it.
Common pitfall: A plugin from an unknown source can run code in your context with your permissions; install only from sources you vetted.
Hands-on exercise: Browse the marketplace, read about one relevant plugin and record what it installs. Decide whether you would install it and why.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
Why check a plugin before installing?
Recap
- Read the docs before installing
- A plugin runs with your permissions
- In organizations follow marketplace policy