If you use Cowork or Claude Code and you've ever wondered what plugins are worth installing — the first answer is almost always anthropics/knowledge-work-plugins. It's the first-party repo, it's Apache-licensed, and as of mid-July 2026 it sits at 22,728 stars and 2,697 forks. Anthropic opens it, Anthropic maintains it, and the last commit before this post went up was earlier today.
This isn't a hands-on install review — the AgentThread standard for that is separate and coming — but the repo is publicly readable, opinionated in its own right, and worth a straight read. Here's what actually ships in it, and how to think about it if you're the reader who was going to install one this week.
What knowledge-work-plugins actually is
The repo describes itself in one line: "Plugins that turn Claude into a specialist for your role, team, and company." That framing is important. Base Cowork is a generalist agent — it can do most things adequately. A plugin narrows the surface: it bundles skills the agent draws on automatically, slash commands the operator invokes explicitly, MCP connectors that hook into the tools the role actually uses, and sub-agents for specific sub-tasks.
The unit isn't "one skill." It's a whole-role bundle. Install the sales plugin and Claude has slash commands like /sales:call-prep, skills tuned for pipeline review, and MCP connections to HubSpot, Close, Clay, ZoomInfo, Fireflies, and the rest of the sales stack. You don't wire this up plugin by plugin. You install one thing, one time, and the agent behaves like it belongs to a sales team.
The marketplace launched with 11 plugins in January 2026 (covered at the time by TechCrunch and The New Stack). Six months in, the repo now ships ~18 plugin categories — the original 11 plus design, engineering, human-resources, operations, partner-built, pdf-viewer, and small-business added since. That growth rate is itself a signal: this is a live product line, not a one-time launch.
What ships in the repo
The 18 categories, grouped by who installs them:
Front-office roles
sales— prospect research, call prep, pipeline review, outreach drafting, competitive battlecards. Connectors: HubSpot, Close, Clay, ZoomInfo, Slack, Fireflies, Microsoft 365.customer-support— ticket triage, response drafting, escalation packaging, KB article generation. Connectors: Intercom, HubSpot, Guru, Jira.marketing— content drafting, campaign planning, brand-voice enforcement, competitive briefs, channel reporting. Connectors: Canva, Figma, HubSpot, Amplitude, Ahrefs, SimilarWeb, Klaviyo.
Product + engineering-adjacent
product-management— specs, roadmaps, user-research synthesis, stakeholder updates, competitive tracking. Connectors: Linear, Asana, Jira, Notion, Figma, Amplitude, Pendo, Intercom.design,engineering— added post-launch; role-specific bundles.
Ops + back-office
legal— contract review, NDA triage, compliance navigation, risk assessment, templated responses. Connectors: Slack, Box, Egnyte, Jira, Microsoft 365.finance— journal entries, account reconciliation, financial statements, variance analysis, close management, audit support. Connectors: Snowflake, Databricks, BigQuery.human-resources,operations— added post-launch.data— SQL, statistical analysis, dashboards, pre-share validation. Connectors: Snowflake, Databricks, BigQuery, Definite, Hex, Amplitude.
Utility + meta
productivity— tasks, calendars, daily workflows, personal context management. Connectors: Slack, Notion, Asana, Linear, Jira, Monday, ClickUp.enterprise-search— one query across email, chat, docs, wikis. Connectors: Slack, Notion, Guru, Jira, Asana, Microsoft 365.bio-research— preclinical R&D specific. Connectors: PubMed, BioRender, bioRxiv, ClinicalTrials.gov, ChEMBL, Synapse, Benchling.cowork-plugin-management— create or customize plugins for your org.small-business,pdf-viewer,partner-built— added post-launch.
The structure of every plugin is the same: .claude-plugin/plugin.json manifest, .mcp.json for tool connections, commands/ for slash commands, skills/ for the domain knowledge Claude pulls on automatically.
Why this matters for knowledge workers
Two things about this repo make it the anchor answer to "what should a non-coder install first."
First, the connector list is the actual value. Every plugin's .mcp.json is a pre-wired set of MCP server connections into the vendor tools the role uses daily. The non-coder doesn't wire Slack to their agent. They don't configure a HubSpot MCP server. They install the plugin, and those connections come attached. This is the specific labor-cost avoidance that separates "installable plugin" from "read the docs and set it up yourself" — and it's why 22,728 people have starred the repo without necessarily being developers.
Second, this is what "OSS for non-coders" looks like in practice. The plugins are Apache-2.0 and forkable — a legal-ops lead at a specific company can fork the legal plugin, edit the templates to match their playbook, add a connector to their internal DMS, and use it privately or contribute back. That's a workflow open-source has always promised but rarely delivered for non-technical users. Cowork's plugin system, and specifically this repo, is the first time it works cleanly at scale for a knowledge-worker persona.
The install path is one line: from the Cowork UI at claude.com/plugins for non-technical users, or claude plugin install sales@knowledge-work-plugins in Claude Code for anyone comfortable with a terminal.
Where it fits
knowledge-work-plugins is the baseline every reader should consider before looking elsewhere. Adjacent options worth naming:
- Community mega-marketplaces like
jeremylongshore/claude-code-plugins-plus-skills(425 plugins, 2,810 skills, 200 agents) — vastly wider selection, uneven quality, no first-party maintenance. Where you go once you've exhausted the Anthropic set. - The
partner-built/subdirectory insideknowledge-work-pluginsitself — plugins from Anthropic partners that meet the same structural bar as first-party ones. Worth reading before jumping to third-party marketplaces. microsoft/skills— Microsoft's counterpart of official skills + MCP servers + custom agents. Ecosystem-adjacent; useful if the reader is already inside Microsoft 365.- The Cowork Plugin Hub aggregators (claudepluginhub.com, crossaitools.com) — index thousands more, useful for discovery but no editorial signal.
The rule of thumb: start with the Anthropic repo, add community plugins only when the first-party doesn't cover the role.
Verdict
Install. No serious caveat.
For non-technical Cowork users: browse claude.com/plugins, install the plugin(s) matching your role, and let the agent behave like a specialist from the first session. If your role is one of the 18 categories, this is the correct first move — do not skip past it looking for something more sophisticated.
For Claude Code users: the marketplace add + install commands work identically, and the plugins carry over cleanly. Especially useful for the ops / support / data plugins if your Claude Code sessions touch those tools.
The only reason to skip a specific plugin is if you already have a heavily-customized internal setup that would conflict — in which case fork the plugin and edit it, rather than installing on top of it.
Hands-on install-review of the top 3 plugins (sales, legal, data) is queued for a future post — that's where AgentThread will report what breaks and what the docs miss under real workflows. This post is a straight read of the repo. Both formats matter; the reader deserves both.