the only 5 claude cowork plugins you need (and how to actually use them)
Anthropic open-sourced 11 plugins for Claude Cowork in January, then added more in February.
Anthropic open-sourced 11 plugins for Claude Cowork in January, then added more in February.
Most people install one, play with it for an afternoon, and forget about it.
That's a mistake.
The right plugins, properly configured, turn Cowork from "kind of cool" into "I can't imagine working without this."
Here are the 5 that deliver real, measurable value.
PS: If you're non-technical and want to learn how to build custom agents, automations, and Skills you'll love our Build With AI community.
Join the waitlist here:
http://return-my-time.kit.com/1bd2720397
---------------------------------------------
1. Data Analysis
This is the single most impressive plugin in the entire library.
What it does:
Drop a CSV into your Cowork folder. Type /data:explore.
Claude reads the full dataset, summarizes every column, flags anomalies, detects data quality issues, and suggests three analyses worth running, all before you've told it what you're looking for.
Then type /data:write-query and describe what you want in plain English. It writes the SQL, validates the query, and explains what it's doing and why.
Connectors: Snowflake, Databricks, BigQuery, Hex, Amplitude, Jira
Real example:
One user ran a client's quarterly revenue data through it, 45,000 rows across three product lines. Within 8 minutes, Claude identified a pricing anomaly in their mid-tier plan that was costing roughly $14,000 per month in undercharged renewals.
The client's own data team had missed it for two quarters.
Who needs it:
Anyone who works with data but isn't a data engineer. If you've ever spent an hour trying to figure out why numbers don't add up, or wished you could just ask "what's wrong with this spreadsheet?", this plugin pays for your entire Claude subscription.
Key commands:
- /data:explore - Automatic dataset analysis
- /data:write-query - Natural language to SQL
- /data:visualize - Generate charts and graphs
2. Productivity
This is the plugin everyone should install first, regardless of role.
What it does:
Manages tasks, calendars, daily workflows, and personal context.
Type /productivity:start and Claude reviews your day, organizes priorities, and sets up your task list based on what's actually on your calendar and in your project management tools.
Connectors: Slack, Notion, Asana, Linear, Jira, Monday, ClickUp, Microsoft 365
Why it's different:
Most productivity tools tell you what to do. This one actually does the organizing for you.
What makes it genuinely useful isn't any single feature. It's that it compounds. After a week of use, the Productivity plugin paired with good context files makes Claude feel like a chief of staff who actually knows your schedule, your priorities, and your working style.
Real example:
Start every morning with /productivity:start. Before you check email, before you open Slack, Claude has already pulled your calendar, reviewed your task list, identified what's urgent vs. important, and drafted your daily plan.
The context from yesterday carries forward.
Who needs it:
Everyone. This is the foundation plugin. Install it first, use it daily, then add role-specific plugins on top.
Key commands:
- /productivity:start - Morning planning session
- /productivity:review - End-of-day wrap-up
- /productivity:plan-week - Weekly planning
3. Sales
If you do any prospecting, account management, or outreach, this plugin is absurdly good.
What it does:
/sales:call-prep pulls context from your CRM (via HubSpot, Close, or Clay connectors), researches the prospect's company, identifies recent news and triggers, and produces a structured briefing doc.
The output includes talking points, potential objections, competitive positioning, and suggested next steps.
Connectors: Slack, HubSpot, Close, Clay, ZoomInfo, Notion, Jira, Fireflies, Microsoft 365
The battlecard feature:
/sales:battlecard is particularly strong. Feed it your product info and a competitor, and it builds a side-by-side comparison with specific rebuttal language.
Not generic "we're better because" talking points, actual responses mapped to specific competitor claims.
Real example:
One sales manager shared that it replaced what used to take his team 90 minutes of pre-call prep. He now does it in under 10 minutes.
The research quality is higher because Claude pulls from multiple sources and synthesizes them, instead of someone skimming a LinkedIn profile 5 minutes before the call.
Who needs it:
Sales reps, account executives, founders doing their own sales, anyone who needs to show up prepared for calls.
The ROI is immediate: better prep = higher close rates.
Key commands:
- /sales:call-prep - Pre-call research and briefing
- /sales:battlecard - Competitive comparison docs
- /sales:pipeline-review - Deal analysis and next steps
4. Product Management
This is the plugin I didn't expect to love.
What it does:
/product-management:write-spec takes a vague product idea and turns it into a structured specification with user stories, acceptance criteria, and technical requirements.
It asks clarifying questions first (using the AskUserQuestion tool), which means the output is grounded in your actual constraints, not generic templates.
Connectors: Slack, Linear, Asana, Monday, ClickUp, Jira, Notion, Figma, Amplitude, Pendo, Intercom, Fireflies
The roadmap feature:
The roadmap command synthesizes your backlog, stakeholder input, and competitive context into a prioritized roadmap.
The competitive analysis feature pulls from connected tools and produces a structured brief that would take a PM 2-3 hours to assemble manually.
Real example:
A product manager described using it to turn a Slack thread with 47 messages of stakeholder feedback into a coherent PRD in 20 minutes.
The spec included acceptance criteria, edge cases, and technical considerations that would normally require multiple rounds of review.
Who needs it:
Product managers, founders building products, anyone who needs to turn vague requirements into concrete specs.
The connector list is the most extensive in the library, which means it can pull context from design tools, analytics, customer feedback, and project management simultaneously.
Key commands:
- /product-management:write-spec - Requirements to PRD
- /product-management:roadmap - Backlog to prioritized plan
- /product-management:competitive-analysis - Market research brief
5. Marketing
Content drafting, campaign planning, brand voice enforcement, competitor briefings, and performance reporting. The Marketing plugin covers the full content lifecycle.
What it does:
/marketing:draft-content is the standout command.
Point it at your brand-voice.md file (from your context folder), specify audience and goal, and it produces content that actually sounds like your brand. Not "AI voice." Your voice.
Connectors: Slack, Canva, Figma, HubSpot, Amplitude, Notion, Ahrefs, SimilarWeb, Klaviyo
Campaign planning:
The campaign planning workflow helps you build multi-channel plans with specific messaging, timing, and metrics for each channel.
The competitive briefing command pulls insights from connected tools and structures them for quick decision-making.
Real example:
A marketing director used it to draft a month's worth of LinkedIn content in one session. She loaded her brand voice file, her content pillars document, and her top-performing posts from the last quarter.
Claude produced 20 drafts that needed minimal editing because they matched her established style.
Who needs it:
Content marketers, social media managers, marketing directors, founders doing their own marketing. The brand voice enforcement alone is worth it, you stop explaining your style every time you need content.
Key commands:
- /marketing:draft-content - On-brand content creation
- /marketing:campaign-plan - Multi-channel campaign structure
- /marketing:competitive-brief - Market intelligence summary
How to Get Started
- Install Productivity first. Use it for a week. Get comfortable with the daily rhythm.
- Add one role-specific plugin. Pick the one that matches 80% of your work: Data, Sales, Product Management, or Marketing.
- Connect your tools. Go to Settings → Connectors. Start with Slack and whatever you use most (Notion, HubSpot, Google Drive).
- Customize the skills. Click "Customize" on any installed plugin. Add your company's terminology, your processes, your quality standards. This is where generic becomes powerful.
- Build the compound effect. Every time Claude's output misses the mark, update your context files or plugin skills. Permanent fix, not a one-time prompt adjustment.
The Pattern
The plugins that matter share one trait: they encode domain expertise, not just prompts.
When you install the Sales plugin, you're not just getting a "write me a sales email" template.
You're loading an entire sales methodology into Claude's working memory.
Start with these five. Customize them for your workflow. Then watch what happens to your output quality.
And if you're non-technical and want to learn how to build custom agents, automations, and Skills you'll love our Build With AI community.
Join the waitlist here: