Welcome to the 12th edition of Work in Beta.

In this edition, we talk about Claude Cowork Plugins which bundles together multiple skills, tool connectors and specific commands into a single package to perform end to end functions.

Also, if you are looking to build your individual or organisational system with AI, you can reach out to us here.

So, let’s dive in!

Over the last few weeks, we've walked you through Skills (reusable procedures), System Building (the habit of extracting reusable infrastructure from your work), and voice profiles. If you've been reading along and thinking "this sounds like a lot of setup work" - we get it.

Here's the shortcut: Cowork Plugins.

A plugin gives you what would take weeks to build yourself - pre-assembled, ready to use from the first conversation.

One thing to know upfront: Cowork Plugins live inside Claude Cowork - not the browser version at claude.ai. You need a paid Claude plan (Pro or Team) and Claude Cowork installed on your computer. If you've only used Claude in a browser, this is what will hold you up. We'll cover setup later in this edition.

Remember the analogy from our Skills edition? A prompt is verbal instructions. A Project is a briefing folder. A Skill is training on a procedure.

A Plugin is a pre-built department.

Not a single skill. Not an extension. Not an add-on. A plugin bundles together multiple skills, tool connectors and specific commands into a single package - everything needed for a role.

Think of it this way:

When you install a plugin, three things happen immediately:

You don't build any of this. You install the plugin. The department shows up, staffed and ready.

Here are three that show the range of what's possible.

Marketing Plugin

Content briefs, campaign planning, editorial calendars, audience analysis. The /marketing:content-brief command takes a topic and produces a structured brief with target audience, key messages, distribution channels and content format recommendations. It pulls from connected context and produces a solid first draft you can work on immediately.

Sales Plugin

You have a client call in 30 minutes. You type /sales:call-prep with the company name. Claude pulls context from your connected tools such as previous notes, company background, recent interactions, and produces a structured brief with key talking points, potential objections, recent company news and suggested questions. One command, done.

HR Plugin

Every manager touches this kind of work - offer letters, onboarding plans, performance review frameworks, job descriptions. The HR plugin handles the structural, template-heavy work that eats hours every quarter. One command, the right context loaded, and you get a first draft that matches standard HR practices and your company's terminology.

The pattern across all three: these aren't tools you configure. They're roles that show up ready to work.

There are currently 17 Plugins across functions and roles than Anthropic and Partners officially provide.

Here's the exact path:

What changes immediately: new slash commands appear in your command list, skills fire automatically when you work on relevant tasks, and Claude has access to the tools that plugin connected.

The whole setup takes under 5 minutes. The first task you run through it will show you the difference.

Plugins are powerful. But they're not magic. Here's what to expect:

Plugins won't replace your judgment. The Marketing plugin produces a content brief, but you still decide whether the angle is right, the audience is accurate, the messaging fits your brand. The output is a starting point you evaluate, not a finished product you send.

Out-of-box templates are generic. The plugin knows marketing. It doesn't know your marketing - your tone, your audience segments, your internal terminology, your approval process. The real power comes when you customize: add your company context, adjust the templates, feed it your existing materials.

Here's the dichotemy: we told you "this is the system you don't have to build." That's true for the structure. But making it work for your specific company still requires your input - your terminology, your processes, your quality bar. The plugin gives you the architecture. You fill it with your context.

That's what makes the output actually useful instead of generically correct.

Skills taught Claude procedures. System Building gave you the habit of extracting reusable work. Plugins are what happens when someone packages all of that - the skills, the tool access, the commands - into something you install in 5 minutes.

You don't have to build the system from scratch. But you do have to make it yours.

Pick one plugin. Run one task. See what happens. Move forward from there.

Knowing how to prompt well is roughly 5% of what it means to actually work with AI. The other 95% - context architecture, workflow compression, thinking behaviors, tool orchestration - is where your workday actually changes. Not "I got a better first draft." More like "I built a full client proposal in one sitting that used to take my team three days."

That's what we work on with professionals and teams through Work in Beta.

If you're curious what the other 95% looks like, reach out to us here.