Power-Ups: Installing Plugins
Sooner or later, someone's going to say it to you. In a forum, in a team chat, in a comment under a video: "oh, there's a plugin for that." And you'll nod along while quietly wondering what, exactly, a plugin is — and whether installing one is the kind of thing that ends badly.
By the end of this lesson you'll know what that sentence means, how to act on it in about four clicks, and — the part most people skip — how to check what you're agreeing to first.
What a plugin actually is
Think about what you've collected over the last few lessons: skills (a way of doing a job, taught once), helpers (specialists you can send off to work), connections to your other tools. You built and added each one yourself, one piece at a time.
A plugin is all of that in a box. Someone else assembles the pieces — a few skills, maybe a helper, a ready-made connection, plus hooks, which are small automations that run on their own at set moments (say, tidying up after each change — still within the permission rules you've set) — and ships the whole thing as one package. You install it in one move, and every piece inside starts working like you'd built it yourself.
And here's the fun part: you've already done this. That skill-creator you picked up in the lesson-six bonus? That was a plugin, installed from a marketplace. You just did it before you had the word for it.
Where plugins live: marketplaces
Plugins come from marketplaces — app stores, essentially. And the first one is already on your shelf: Anthropic's official marketplace comes built in. Nothing to add, nothing to configure; open the plugin browser and it's there.
It's worth a browse just to see the range. The integrations from last lesson live here — ready-made packs for GitHub, Jira, Asana, Linear, Notion, Slack, Sentry, Supabase — which is exactly what that closing tease meant: the connection, plus the skills to use it well, arriving as one install. These are work tools, though — same rule as lesson eight: check what your company allows first. Alongside them: skill-creator (an old friend by now) and a set of security helpers, among others.
Browsing and installing
The door is one you already know from lesson two: the "+" button beside the prompt box, then Plugins, then Add plugin. A directory window opens and you browse like any app store — click a plugin to read about it, click install, done.
One choice appears at install time worth understanding: scope — who gets this plugin. Just you means it follows you across all your projects. This project means everyone who shares the project folder gets it too — the same idea as project skills from lesson six. When in doubt, pick just-you; you can always widen later.
Prefer typing? The same install is one command:
/plugin install skill-creator@claude-plugins-official
See what a plugin brings
A plugin can carry a lot, so it pays to know what you're adding. Open a plugin's page and it lays out its full contents: every skill it brings — each one a new thing you can ask Claude to do — and every connection it opens to your other tools.
The connections are the part to look at closely. One plugin might reach into Slack, Notion, your calendar, your email — real access to real accounts. Often that's exactly what you want; you just want to have seen it first. Read that list the way you'd read an app's permissions screen.
Take the Marketing plugin as an example: a single install brings eight skills — things like drafting a post or auditing your SEO — and opens thirteen connections, to tools from Slack to Gmail. One box, a lot inside.
Two more things before you widen your net. Every plugin also takes up a slice of Claude's attention the whole time it's installed, used or not — so a few good ones beat a drawerful. And in the desktop app you see a plugin's full contents most clearly once it's on its page, which means the real safeguard sits one step earlier: in where you install from. That's next.
The wider world: a trust ladder
The official store isn't the whole ecosystem — anyone can publish plugins, and that's genuinely good news. It also means your caution should rise a notch with each step away from home. Three rungs:
Rung one — the official marketplace. Curated by Anthropic, already added, no decisions to make. Browse freely.
Rung two — Anthropic's community marketplace. Third-party plugins that have passed Anthropic's validation checks. It doesn't come pre-added; you add it deliberately, with one command:
/plugin marketplace add anthropics/claude-plugins-community
Rung three — anywhere on the internet. Anyone can host a marketplace — often it's just a page on GitHub (a site where people share and host code) — and you add it by its address. This is where the ecosystem's long tail lives, and where you become the reviewer, because Anthropic doesn't verify third-party plugins, and plugins run with your permissions — they can do anything on your computer that you can. Only add marketplaces from people and companies you already trust, and check what each plugin brings every single time.
One reframe makes the whole ladder manageable: adding a marketplace installs nothing. It just puts a store on your street — every install afterwards is still your call, one plugin at a time. Which means the add-a-marketplace moment is the real trust decision. Make it about the source, and the rest follows.
Living with your plugins
The same "+" → Plugins menu has a Manage plugins view: everything you've installed, with the ability to disable a plugin (keep it, switch it off) or uninstall it entirely. Updates flow in from the marketplace on their own for the official store.
Remember how every plugin keeps taking up a slice of Claude's attention? That's the reason pruning matters. A plugin you never use is still occupying that space — the app even flags ones you haven't touched in a while. If it's been idle for a month, disable it. Nothing is lost; flip it back on the day you need it.
Making your own — a postcard from further down the road
Everything a plugin contains, you already know how to make. Package your own skills and helpers into a plugin, share it with your team, even host a small marketplace of your own — it's all possible, and it's maker territory this course deliberately stays out of. When the day comes, Anthropic's plugin docs have the full walkthrough. File it away.
So that's the ecosystem: real capability in one move, kept safe by installing from sources you trust and checking what each plugin brings. There's one more cockpit to show you, though. Everything in this course has happened in the app — friendly buttons, menus, the "+" — but Claude Code has an older, plainer home where many workplaces run it: the terminal. Same Claude, same skills, same plugins — different cockpit. Next lesson, we take the tour.
Window-shop, install one, see what it brought
You can skip this and still follow everything — it's here if you like learning by doing.
All of this stays inside the official marketplace — the safe end of the pool.
- Open the store. Click + beside the prompt box → Plugins → Add plugin.
- Window-shop. Open two or three plugins and read what each one's for — its description and the tasks it promises. Notice how different plugins carry very different cargo.
- Install one. Skipped the lesson-six bonus? Now's the moment: install skill-creator (it pays off later in the course). Already have it? Pick anything light that looks genuinely useful. Choose just-you scope.
- See what it brought. Open its page (or Manage plugins) and look over the skills and connections it added — then try it, by its command or by asking Claude to use it.
What you should see: the plugin's skills now available in your session, and its full contents — every skill and connection — laid out on its page.
Not ready to install anything? Steps one and two alone teach the whole habit — window-shopping is free.