My Claude Cowork plugins sent me a bill last week. Not in money. In connectors.
I opened a session and got a list of 16 connectors waiting for my authorisation, plus one plugin server that timed out after 30 seconds. I had not asked for any of them. They arrived bundled inside three plugins I installed from Anthropic's own list.
Claude Cowork plugins are installable packages that bundle skills, connectors, and sub-agents into one add. They are available on paid Claude plans, and they work inside the Cowork tab of the Claude desktop app. One plugin can add a dozen capabilities in a single click, which is exactly why you should vet each one before you install it.
That list of 16 made me do something I should have done earlier. I sorted every plugin and skill on my machine into two piles. One pile does real content work, and the other just sits there.
I have been blogging since 2005 and I run 14+ niche blogs, plus Threads accounts and an email list. I also built two SaaS tools, Threadeazy and VoiceLab. So my setup is not a demo; it carries real weekly work.
If you are new to Cowork itself, start with my plain-English guide to what Claude Cowork is. This post assumes you have the tab open and are now staring at the Plugins screen, wondering what to add.
What Are Claude Cowork Plugins, and How Are They Different From Skills?
A skill is one saved set of instructions for one job. A plugin is a box that can hold several skills, plus connectors to outside tools and sometimes sub-agents. A sub-agent is a helper Claude hands one part of a task to.
You install the box in one click, and everything inside it arrives at once.
That difference matters more than it sounds. When you add a skill, you know exactly what you added. When you add a plugin, you add whatever its author decided to pack.
Here is how I explain the three pieces to friends:
| Piece | What it is | What it touches | Risk if you add it blindly |
|---|---|---|---|
| Skill | One recipe for one job | Only the files you give it | Low: it just sits unused |
| Connector | A link to an outside service | That service's data, once you authorise it | Medium: more accounts linked |
| Plugin | A bundle of skills, connectors, sub-agents | Everything it bundles | Higher: you get the whole bundle |
Anthropic's help article on using plugins in Claude Cowork adds one warning worth reading twice. Plugins can include local servers that run on your computer with the same permissions as any other program. Its advice is short: only install plugins from sources you trust.
Claude Cowork skills are the part that does the work
In my setup, the plugin is rarely the hero. The Claude Cowork skills inside it, or the ones I wrote myself, carry the actual job.
I wrote about how to build one in my step-by-step guide to Claude skills. The short version: a skill is a recipe card Claude keeps, so you stop retyping the recipe.
The Claude Cowork Plugins I Installed for Content Work
I run three plugins from Anthropic's knowledge-work list, plus a set of tool plugins on the Claude Code side. The desktop app saves plugins to my account, so they also show up in Claude Code. Only a few of them touch content work every week.
Let me break it down by what each one does for a blog, a Threads account, or an email list.
The marketing plugin: installed, mostly unused
The marketing plugin ships 8 skills: brand review, campaign plan, competitive brief, content creation, draft content, email sequence, performance report, and SEO audit. On paper, that is a content creator's dream.
In practice, I have not wired a single one of those 8 skills into my routines. I checked every scheduled routine on my machine, all 99 of them, and none call the marketing plugin.
Why keep it, then? Its skill files are worth reading once. They show how Anthropic structures a content skill, which is a useful model if you plan to write your own.
The productivity plugin: two small jobs
The productivity plugin handles tasks, daily planning, and memory of ongoing work. Two of my scheduled routines call its start skill to set up the day's context.
That is a small footprint. It is also exactly the right footprint for a plugin: one job, done on a schedule, with no extra accounts linked.
The plugin-management plugin: for building your own
The third one, cowork-plugin-management, lets you create and customise plugins. In April I built and uploaded my own plugin for promoting Threadeazy and VoiceLab.
That plugin did not last. More on that in the skipped section.
My own skills carry the blog, Threads and email work
Here is the thing. The work that ships every week runs on skills I wrote, not on any of the Claude Cowork plugins from a list.
My anti-AI-writing filter runs in 9 of my 99 scheduled routines. My SEO optimiser runs in 7, and my content auditor runs in 5.
My Threads batch writer and email copywriter sit in the instructions for those two channels. Every Threads batch and every email draft goes through them.
Those Claude Cowork skills know my voice, my banned words, and my formatting rules. No plugin from a public list could know those things, because they came from 20 years of my own mistakes.
The Claude Code side: tools, not writing
On the Claude Code side, I run a WordPress plugin, a Hostinger plugin, and an n8n workflow designer. Hostinger shows up in 5 of my scheduled routines, because several of my sites live there.
These are not writing tools. They move finished content to where it lives. If you only write, you can skip this layer for months.
What I Skipped, Switched Off, or Never Connected
I switched off one plugin I built myself, left about 16 bundled connectors unauthorised, and kept several developer plugins away from my content folders. Each decision came from the same question: does this touch work I do every week?
Let me take them one at a time.
The plugin I built and then switched off
In April I built a plugin called SaaS Promo Studio. It walked me through a content brief, picked the right writing skill, and logged every promo post to a tracking file.
It is switched off in my settings today. Looking at it now, the plugin was a wrapper around skills I already had. The Threads writer, the email copywriter, and the YouTube script writer each did the real work on their own.
That was my lesson. A plugin that only routes you to your own skills adds a step without adding a capability.
The 16 connectors I never authorised
The marketing and productivity plugins together bundle connectors for tools like Ahrefs, HubSpot, Klaviyo, Figma, Asana, ClickUp, Slack, and more. My session listed 16 of them waiting for authorisation.
I left them unconnected. I use Notion and Canva every week, and both already reach Claude through connectors I set up separately. The other 14 are not part of my content week, so linking them would only widen what Claude can reach.
Does that mean the marketing plugin is bad? Not really. It was built for a team with a full marketing stack, and a solo blogger simply has a smaller one.
Developer plugins I would skip for content work
I also have plugins for Firebase, RunPod, and TypeSafe installed. They serve my app-building work, not my writing.
If your work is blogs, Threads, and email, I would skip all three. The Firebase one even timed out on connection last week. Every plugin is one more thing that can fail at startup.
How to Judge Claude Cowork Plugins Before You Install Them
Judge a plugin by what it bundles, not by its name. Read its skill list, count its connectors, check who built it, and confirm it solves a job you already do every week. If it fails two of these checks, skip it.
This is the checklist I now run before adding anything. It takes about 10 minutes per plugin.
The 5-question plugin vetting checklist for Claude Cowork plugins
- Who built it? Anthropic's own list, a known vendor, or a stranger's repository? A plugin can run local programs, so the author matters more than the star count.
- What exactly does it bundle? Open the plugin details and list every skill, connector, and sub-agent. If you cannot list them, you do not know what you are installing.
- Which weekly job does it replace? Name the job in one sentence, like "my Friday email draft." If you cannot name a job that repeats weekly, wait.
- Does it duplicate a skill I already have? Compare skill names with your existing ones. Two skills called "SEO audit" means you will not always know which one ran.
- What happens if I remove it tomorrow? If nothing breaks, it was decoration. If a weekly job breaks, it has earned its place.
Run this once and keep the answers in a note. Six months later, that note tells you what to remove.
A quick scoring rule
Give each question one point for a clear answer. A plugin scoring 4 or 5 goes in. A score of 3 goes in on trial for two weeks, and anything lower stays out.
Here is how my own list reads against it. The productivity plugin answers all five questions cleanly. SaaS Promo Studio fails questions 3, 4, and 5, which matches the fact that I had already switched it off.
The Install Order I Would Follow Today
Install skills before plugins, and plugins before connectors. Start with one writing skill that matches your voice, add one plugin only when a weekly job asks for it, and connect outside services last. This order keeps every addition traceable.
If I were setting up Claude plugins for content creators from zero, this is the exact sequence.
- Week 1: One voice skill. Write or install a skill that holds your banned words and style rules. Run every draft through it.
- Week 2: One checking skill. Add an auditor or SEO checker that reads a finished draft and lists problems. Mine runs on every blog post before it goes to Notion.
- Week 3: The productivity plugin. Add it for task and daily planning only. Leave its bundled connectors off.
- Week 4: One channel skill. Pick your main channel, Threads or email, and add a skill that writes in its format.
- Month 2: Connectors, one at a time. Connect only the services a skill actually needs, such as your notes app or your design tool.
- Month 3: Publishing plugins. Only now consider WordPress or hosting plugins, once the writing side runs without you babysitting it.
Why skills come before plugins
Skills are small enough to understand completely. Once you know what a good skill looks like, you can read a plugin's skill list and judge it in minutes.
Start with plugins instead, and you inherit someone else's idea of your workflow. That is how I ended up with 16 connector prompts I never asked for.
Claude Cowork workflows to build after month 1
Once your Claude Cowork skills hold your voice, chain them into small workflows. My blog workflow is draft, voice filter, audit, then Notion. Each step is a skill I can test on its own.
If AI drafts still sound flat after the voice skill, read how I humanize AI content without losing the point. For the chaining itself, my post on automating a content workflow with Claude walks through the steps.
The best Claude plugins for content creators slot into a workflow like this one. They do not replace it.
When the Best Claude Cowork Plugins Work, and When They Don't
The best Claude Cowork plugins replace a job you already repeat. They fail when you install them hoping a job will appear. The plugin follows the workflow, never the other way round.
Here is the honest split from my own setup.
Plugins work if:
- You already do the job weekly and can describe it in one sentence.
- You use the tools its connectors link to, today, not someday.
- You have read the full skill list and none duplicate yours.
- You will check its output for the first two weeks.
Plugins do not work if:
- You install a bundle "to explore" and never name the job it should do.
- Your voice and rules live only in your head, so generic writing skills fill the gap.
- You are a solo creator installing a plugin built for a 20-person marketing team.
- You stack three plugins that each bring their own version of the same skill.
My Claude Cowork workflows got simpler as I removed things, not as I added them. That was the most useful lesson in this whole exercise.
Common Plugin Mistakes and How to Fix Them
The most common plugin mistakes are connector sprawl, duplicate skills, and keeping plugins that no longer do a job. Each one has a fix that takes under 15 minutes.
Mistake 1: Connector sprawl. You install a plugin and it asks to link a dozen services. It happens because team plugins bundle every tool a big team might use.
The fix: Authorise only the connectors a skill you actually run needs, and leave the rest off.
Mistake 2: Duplicate skills. My own skill list shows two content auditors and two SEO audits, from different sources. It happens because plugins and personal skills grow separately.
The fix: Name your own skills distinctly, and call them by full name inside your routines.
Mistake 3: Keeping a plugin out of guilt. Switching off something you built can feel like admitting a mistake. It happens because effort makes us attached.
The fix: Use question 5 from the checklist. If nothing breaks when it is gone, switch it off, as I did with SaaS Promo Studio.
Mistake 4: Ignoring startup failures. A plugin server that times out can fail without much noise at the start of a session. It happens because nobody reads the warnings above a long task.
The fix: Read the session warnings once a week, and remove anything that fails twice.
A monthly clean-up rule
Once a month, list all your Claude Cowork plugins and the last real use of each. Anything with no use in 30 days gets switched off, not deleted.
Switching off keeps the option to come back, and it costs you nothing.
Where a Ready-Made Skill Stack Fits
If writing your own voice and checking skills feels like the slow part, that is fair. It took me months, one irritation at a time.
That is why I put together the Content Creator's Claude Skill Stack: 18 ready-made skills for content creators, with a plain-English setup guide. It covers the skill layer from weeks 1 to 4 of the install order above. You start with tested files instead of a blank folder.
You do not need it to follow this post. If you would rather build your own, my guide to Claude Code skills for content creators shows how I started.
Frequently Asked Questions About Claude Cowork Plugins
These are the questions I see most often about plugins and skills in Cowork, answered in short form.
What are Claude Cowork plugins?
Claude Cowork plugins are packages that bundle skills, connectors, and sub-agents into a single install. You add one from the Plugins tab under Customize in the Claude desktop app. One plugin can add 8 or more skills and a dozen connectors at once, so read its contents first.
Are Claude Cowork plugins free?
Plugins are available on paid Claude plans: Pro, Max, Team, and Enterprise, according to Anthropic's help article. Your Claude plan is the entry ticket. Connectors inside them may link to paid services, so check what each connected tool costs before you authorise it.
What is the difference between a Claude Cowork plugin and a skill?
A skill is one saved set of instructions for one job, such as checking a draft for banned words. A plugin is a bundle that can hold several skills plus connectors and sub-agents. The marketing plugin, for example, ships 8 skills and around 10 connectors in one add.
What are the best Claude Cowork plugins for content creators?
For a solo creator, the productivity plugin is the safest first add, because it handles tasks and planning without needing new accounts. The marketing plugin is worth reading for how its skills are built, but it is designed for teams. The skills that move my blog, Threads, and email work are ones I wrote myself. My voice filter alone runs in 9 of my 99 routines.
Are Claude Cowork plugins safe to install?
They are as safe as their author. Anthropic warns that plugins can include local servers that run on your computer with the same permissions as any other program. Install only from sources you trust, list every bundled connector before adding one, and authorise connectors one at a time.
How many Claude Cowork plugins should I install?
Fewer than you think. I run three plugins from Anthropic's list for knowledge work, and only one of them, productivity, is called by any of my scheduled routines. Start with one plugin, use it for two weeks, and add the next only when a weekly job asks for it.
Do Claude Cowork skills work outside Cowork?
Yes. Anthropic's help article says skills and commands work in chat, Cowork, and Claude Code, while hooks and sub-agents run only in Cowork and Claude Code. Plugins you add are saved to your account, so they follow you when you sign in with the same account.
Can I build my own Claude Cowork plugin?
Yes. The cowork-plugin-management plugin helps you create and customise one, and you can upload a plugin file you built. I built one in April 2026 for promoting my own products, then switched it off. Looking back, it only routed me to skills I already had.
How do I remove a Claude Cowork plugin I no longer use?
Turn it off first rather than deleting it, so you can bring it back if a job breaks. In Claude Code, plugins have an on and off switch in settings, and mine shows one plugin set to off. Review your list monthly and switch off anything with no real use in 30 days.
Which Claude Cowork workflows should I set up first?
Start with a voice check and a draft audit, because every post, thread, and email passes through both. My anti-AI-writing filter and content auditor run on every blog draft before it reaches Notion. Add channel workflows, like a Threads batch writer, in week 4.
The Plugin Pile Is Smaller Now
That list of 16 connectors looked like a warning when it appeared. It turned out to be a free audit.
After the sort, my content week runs on a handful of skills I wrote. One plugin from Anthropic's list handles daily planning, and a few tool plugins move finished posts.
Everything else is either switched off or waiting for a job to earn it a place. I am still adding things, but now every addition has to name its job first.
So here is my question for you. Open your Plugins tab today and count what is installed. How many of them did real work for you this week?