Best Claude Code Plugins 2026: 11 Tested, 4 Worth Keeping

Originally published on Build to Launch. This is the condensed version.

I wrote the original article. An AI assistant condensed it, and I checked this version before I published it.

Have you installed a Claude Code plugin and then wondered why your sessions got slower, or why something ran that you never asked for?

That was my starting point. I build and ship with Claude Code every day. When the official marketplace grew to 101 plugins (as of March 2026), I stopped guessing and tested them on real work. Content plugins went on my actual writing system. Business plugins got my actual positioning questions. Coding plugins went into a real feature build for an app I maintain.

Eleven plugins in total. Below are the parts that matter most if you are deciding what to install this week.

What a Claude Code plugin is

"Plugin" gets used for four different things, and they cost you in four different ways. A plugin can bundle any of these:

• Skills. What most people mean by "using a plugin." You trigger one with a slash command like /brand-voice:enforce-voice or /marketing:seo-audit. It runs once and stops. Cost: per use.
• Hooks. They attach to events (session start, file write, commit) and fire every time without you asking. Cost: every session they are active.
• Commands. The management layer: /plugin install, /plugin disable, /plugin marketplace add. Free.
• MCP servers. Connections to databases, APIs and file systems. They ship inside plugins so often that people treat the two as the same thing. Cost: per query. (I wrote up the MCP servers I use daily separately.)

One install can give you a skill, a hook and an MCP config at once. Three behaviors, three cost levels. When a session feels heavy, this is the first place I look.

One more source of confusion: the plugin system lives in Claude Code only. Claude on the web has MCPs and built-in tools, with no terminal, no hooks and no slash-command plugins. Claude Desktop has MCP-based extensions. If you read about a Claude Code plugin and cannot find it in the web app, that is why.

/plugin install security-guidance@claude-plugins-official /plugin marketplace add owner/repo /plugin install brand-voice@knowledge-work-plugins 

Three levels of trust

Level 1: Anthropic's official marketplace. claude-plugins-official is built in. As of March 2026 it held 101 plugins: 33 built by Anthropic and 68 from partners such as GitHub, Playwright, Supabase, Figma, Vercel, Linear, Sentry and Stripe. Two more Anthropic marketplaces need a manual add: life-sciences (17 plugins) and knowledge-work-plugins (14 role-based plugins, including Sales, Marketing and Brand Voice).

A side note on labels: claude.com/plugins tags 11 plugins as Cowork-only. I installed Brand Voice, Marketing, Sales, Productivity and Cowork Plugin Management directly in Claude Code. They work there.

Level 2: community marketplaces. Any GitHub repo, added with /plugin marketplace add owner/repo. No verification. Also, a repo that advertises "1,916 skills" does not hold 1,916 things you can /plugin install. Some entries are full plugin packages and some are loose skill files.

Level 3: discovery sites. Indexes that scan GitHub for plugin.json. Useful for search, and they are not a source of trust.

Anthropic's own docs put it plainly: "Plugins and marketplaces are highly trusted components that can execute arbitrary code on your machine. Only install from sources you trust."

The results I can share here

Each plugin got three questions. Where does it work? Where does it break? Does it earn a place in the stack?

First, something that went wrong before any test ran. The knowledge-work-plugins marketplace failed schema validation when I tried to install from it. I had to fix the files in a local copy before I could test Brand Voice, Marketing, Sales or Productivity at all. An official Anthropic marketplace that would not install was not the start I expected.

Brand Voice: KEEP

Three skills: discover your brand materials, generate guidelines, enforce them while you write. On my content-engine folder it:

• found 15 brand documents spread across subdirectories
• found 34 Gumroad products I had never checked for consistency
• wrote a 963-line guidelines file that loads in later sessions

It breaks if you write for several channels in different voices. Left on globally, it pulls everything toward one guideline set. The one-time discovery pays back on every article after, so it stays.

explanatory-output-style: CONDITIONAL KEEP

This one is a hook, so it shapes every response. When I asked Claude to explain the plugin marketplace, the answer scored 9/10 for clarity from me: layered explanation, component walkthroughs, ASCII flow diagrams. For tutorials and docs, that is the structure you want.

A quick coding question also gets a structured lesson. So does a content edit. And every exchange pays the token cost. I turn it on for teaching work and leave it off the rest of the time.

Marketing: KEEP

Six skills covering SEO audit, drafting, brand review, competitive research, campaign planning and email sequences. I ran four of them over about 1 hour 40 minutes:

• SEO audit (30 min): 25 keyword opportunities, 7 competitors benchmarked, a 90-day plan.
• Drafting (45 min): three SEO-driven drafts of about 2,900, 4,100 and 3,600 words with Brand Voice applied. They still needed editing, and they were real working drafts.
• Brand review (25 min): 4 high-priority issues, including missing personal intros, uncited revenue claims and gaps in affiliate disclosure. Compliance score 85/100.

I enable it for content planning sessions and disable it for short social posts.

Sales: SKIP (for creators and builders)

I ran /competitive-intelligence on Build to Launch. In 2 minutes it produced an HTML battlecard with tabs, a comparison matrix, a dark theme and talk tracks. It looked finished.

Then I read the data. It said I had 2,000 subscribers. I have 5,000+. It compared me to The Rundown AI (2M subscribers) and DeepLearning.AI (7M learners), a different league entirely.

Marketing has a competitive-brief skill, so I asked both the same question. Marketing took about 45 minutes and came back with 3 comparable competitors, a "stuck-in-the-middle builder" positioning gap, 10+ content gaps and 7 actions. Grounded in my real tier. Sales is built for people with CRM pipelines and regular customer calls. If that is not you, most of it sits unused.

Productivity: SKIP if you already have a system

/start gives you task breakdowns, priority ranking and file-based memory across sessions. The design is thoughtful. If you already run Notion, Linear or a well-kept markdown file, it adds a second layer that manages the same information. I confirmed it works and moved on.

What is in the full guide

Those are 5 of the 11. The full guide on Build to Launch continues with:

• the coding plugin results, including feature-dev cutting 4 database tables before a line of code was written
• the stack I keep, with always-on vs session-based toggle logic for content, coding and UI work
• a 9-question scorecard to run before you install anything
• every breakage I hit and what I would do instead

If you are new to Claude Code, How to Onboard to Claude Without the Learning Curve covers the setup this post assumes. The Claude Code Hub indexes every guide I have on Claude tools.

FAQ

Do Claude Code plugins work in Claude Desktop or on claude.ai? No. The plugin system (skills, hooks, slash commands, marketplaces) is Claude Code only. Desktop and web support MCP connections.

Are the "Cowork" plugins limited to Cowork? The site labels them that way. I installed five of them from knowledge-work-plugins and ran them in Claude Code.

Are community plugins safe? Community marketplaces have no verification, and plugins can run arbitrary code on your machine. Start with the official marketplace and read what a plugin bundles before you install it.

Why does my session feel slower after installing plugins? Check for hooks. A hook runs on every session or every response, so its cost adds up even when you never call it. A skill costs you only when you use it.

Where do plugins live? In ~/.claude/plugins/. Install once globally and they work across projects.

Which plugin earned a permanent place in your setup, and which one did you uninstall after a day? Tell me in the comments. I am collecting candidates for the next round of tests.

More of my tests on real work are on my blog, Build to Launch.

— Jenny