The claude plugin Commands
Level 4 · Setup and extensions
How to add a marketplace and install plugins from your shell. Then how to list and remove them, and the commands to check and test one you make.
Course contentsLesson 13 of 17
Level 1 · Get started
Level 2 · Inside a conversation
Level 3 · Parallel work and review
Level 4 · Setup and extensions
Level 5 · Scripts and servers
After this lesson you can
- Install a plugin in the scope you mean
- Check a plugin in CI with validate
- Load a plugin for one session to test it
12 mincovers 10 glossary entries
Worth reading first: The claude mcp Commands
How to install plugins, and test your own, from the shell
A plugin bundles skills, agents, hooks and MCP servers so they install together. Plugins come from a marketplace, a list you add once. claude plugin marketplace add takes a GitHub repo, a git link, a file on the web or a folder on your own disk. Then claude plugin install adds one by its name.
An install goes in user scope by default, for all your projects. --scope project shares it with the team through the repo's settings, and --scope local keeps it to you in this project. Name it as name@marketplace when two marketplaces offer the same name. --json prints a result a script can read.
claude plugin list shows what is installed, with the version, scope and status of each. claude plugin details shows one plugin's parts and how much context they cost. claude plugin uninstall removes one from a scope, and remove and rm are other names for it.
Some plugins were installed only because another one needed them. claude plugin prune clears those once nothing needs them, and it never removes a plugin you chose. Add --dry-run to see the list first.
Making a plugin has two checks. claude plugin validate reads the manifest, or the skills, agents and commands in a folder, and lists what is wrong. It ends with code 0 when it passes and 1 when it fails, so a CI job can stop a broken plugin. --strict also fails on warnings.
claude plugin eval asks the harder question: does it help? Each test case is a prompt plus graders that score the answer. Claude Code runs each case several times in a clean session with only that plugin loaded. By default it also runs each case without the plugin, so the report shows the gain.
To try a plugin before you install it, --plugin-dir loads one from a folder or a .zip for this session only. Repeat the flag for more. Nothing is installed, so it is gone when the session ends. --disable-slash-commands turns off every skill and command, for a clean test with none of them.
Two more launch flags help while you build. --init runs your Setup hooks before a -p run. --init-only runs them and then exits. --dangerously-load-development-channels turns on a channel that is not on the approved list. That lets you test one you are building. It asks you first, so it only works in a chat.
claude plugin marketplace add my-org/claude-plugins
claude plugin install code-review@claude-plugins-official --scope project
claude plugin validate ./my-plugin --strict
claude plugin eval ./my-plugin
claude --plugin-dir ./my-pluginWorked example
Jack's plugin passes but does not help
Jack's plugin passes claude plugin validate with no errors. He runs claude plugin eval on 10 cases, and 6 pass with the plugin.
Without it, 6 pass too. The files are right, but the plugin adds nothing yet, so he rewrites its main skill before he shares it.
The words for this lesson10
Check yourself
A plugin passes claude plugin validate. What does that prove?
Finished this lesson?
Marking it complete also marks its 10 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.