You've learned to create skills, configure hooks, and use subagents. But what if someone has already built exactly what you need?
A plugin bundles multiple Claude Code components into one installable package:
Think of plugins as: Complete capability packages. Instead of manually setting up skills, hooks, agents, and MCP servers separately, you install one plugin and everything works together.
Without plugins, adding GitHub integration means:
With plugins, you run:
Done. GitHub integration works—including MCP config, any bundled skills, and automation hooks.
The principle: Check what exists before building from scratch.
Run this command in Claude Code right now:
What you'll see:
The official Anthropic marketplace is automatically available. No setup needed.
Use Tab to switch between tabs:
Let's install commit-commands—a plugin that helps with git workflows.
What happens:
After installing commit-commands, make a small change to any file, then run:
What happens:
That's it! You just extended Claude Code with one command.
These use the Language Server Protocol (LSP)—the same technology that powers VS Code's code intelligence.
After installing (e.g., typescript-lsp), Claude can:
Note: LSP plugins require the language server binary installed on your system. If you see "Executable not found," install the required binary:
Connect Claude to services you already use:
Now Claude can interact with GitHub issues, PRs, and repositories directly.
When you install a plugin, choose where it applies:
Recommendation: Start with User scope for personal tools, Project scope for team standards.
Go to the Installed tab.
The official marketplace is just the start. You can add others:
GitHub repositories:
GitLab or other git hosts:
Local development:
Anthropic maintains the official plugins repository with verified plugins:
This gives you access to all officially maintained plugins including Ralph Wiggum (Lesson 17).
Rule of thumb: Check the marketplace before building from scratch.
You've installed plugins. Now let's create one from the skills and components you've already built.
Throughout this chapter, you created skills (Lesson 9), configured subagents (Lesson 11), connected MCP servers (Lesson 12), and set up hooks (Lesson 15). Packaging these as a plugin lets you share them with teammates or use them across all your projects.
A plugin is a folder with a specific layout:
Critical: Components go at the root level, not inside .claude-plugin/. The .claude-plugin/ folder only contains the manifest.
Every plugin needs a plugin.json file inside .claude-plugin/:
That's the minimum. Four fields. Your plugin is ready to use.
If you downloaded the Skills Lab in Lesson 7, let's turn it into a plugin:
Step 1: Navigate to your Skills Lab folder:
Step 2: Create the manifest folder and file:
Step 3: Create plugin.json:
Step 4: Test your plugin locally:
Step 5: Verify skills appear with namespace:
Your Skills Lab is now a plugin.
Why have marketplaces at all?
You could share plugins without a marketplace—just tell someone to clone your repo and use --plugin-dir. But marketplaces provide:
Can you list your plugin on someone else's marketplace?
Yes. Options include:
Most developers create their own marketplace for personal/team use, then submit polished plugins to the official marketplace for broader distribution.
To share your plugin with others, create a marketplace:
Step 1: Create a marketplace.json in your .claude-plugin/ folder:
Step 2: Push to GitHub (or GitLab, or any git host)
Step 3: Others can now add your marketplace:
You can now discover, install, and create plugins—the complete lifecycle. Lesson 17 introduces the Ralph Wiggum Loop—an autonomous iteration pattern where Claude validates and refines its own work. You'll see how to combine everything you've learned (skills, subagents, hooks, and your own plugins) into self-correcting workflows.
🔍 Explore the Marketplace:
"Run /plugin and show me what's in the Discover tab. What categories of plugins are available? Which ones would be useful for [your work: web development / Python / data analysis]?"
What you're learning: Plugin discovery—understanding what capability extensions exist before building from scratch. The ecosystem often has what you need.
📦 Install and Test:
"Help me install the commit-commands plugin. After it's installed, walk me through using /commit-commands:commit to commit a change. What other commands does this plugin provide?"
What you're learning: The full plugin workflow—from installation through verification. Knowing the complete cycle builds confidence with new plugins.
🔌 Code Intelligence:
"I write [TypeScript / Python / Rust / Go]. Help me install the LSP plugin for my language. What do I need to install on my system first? After installation, show me how Claude can now jump to definitions and find references."
What you're learning: How plugins add capabilities Claude doesn't have natively—in this case, language-server-level code understanding.
🔗 External Integration:
"I want to connect Claude to [GitHub / Slack / Linear]. Help me install the appropriate plugin. What capabilities does it add? Show me an example of using it."
What you're learning: Platform integration through plugins—extending Claude's reach to external services without writing custom MCP servers.
⚖️ Plugin Decision:
"I need Claude to help with [describe your task]. Should I: (a) install an existing plugin, (b) create a custom skill, (c) just ask Claude directly? Help me decide based on what's available in the marketplace."
What you're learning: The build vs. buy decision for AI capabilities—when to use existing solutions vs. creating custom ones.
📦 Package Your Skills:
"Help me package my Skills Lab directory as a plugin. Create the plugin.json manifest, organize my skills into the correct directory structure, and test it with --plugin-dir."
What you're learning: Plugin creation workflow—turning your existing Claude Code components into shareable, installable packages.
🌐 Create Your Marketplace:
"I have a plugin ready. Help me create a marketplace.json file, push it to GitHub, and show me how others can install my plugin."
What you're learning: Plugin distribution—sharing your work with teammates or the broader community through marketplace catalogs.