Knowledge Work Plugins

Eleven Markdown-and-JSON Claude plugins that turn a general agent into a job-specific coworker

Category
AI agents & assistants
Audience
Everyone

Updated

Knowledge Work Plugins is Anthropic's open-source repository of eleven ready-made Claude plugins that turn a general assistant into a specialist for one office job function: sales, legal, finance, support and more. It is aimed at knowledge workers who already use Claude and want it to follow their own department's process instead of giving generic advice, and at the person on a team who has to set that up for everyone else.

What it does

The repository ships eleven official plugins: Productivity, Sales, Customer Support, Product Management, Marketing, Legal, Finance, Data, Enterprise Search, Bio Research, and Cowork Plugin Management, the last being a meta plugin for building new plugins. The count of eleven is the repository's own, from the README.

Each plugin bundles three things: domain skills (written instructions for how a task in that field is done), slash commands you can call by name, and MCP connectors to the tools the job actually runs on. The README names Slack, Notion, HubSpot, Salesforce, Snowflake, Jira, Asana and Box among the connectors.

Anthropic's description of the sales plugin is the clearest example of the intent: it connects to your CRM, learns your sales process, and drafts your follow-ups. That is the vendor's claim about its own plugin, not an independent measurement, and the material here carries no benchmark, accuracy figure or user count for any of the eleven.

How it works

A plugin is just a folder. Inside it sit .claude-plugin/plugin.json (the manifest), .mcp.json (which outside tools it may connect to), a commands/ directory and a skills/ directory. That is the whole mechanism: pure Markdown and JSON, with no code, no infrastructure and no build step.

A non-engineer can open a plugin on GitHub, read the exact instructions Claude will follow, and rewrite them in plain English. Nothing is compiled, nothing is hidden behind a settings panel. The repository is Apache 2.0 licensed, so forking a plugin and keeping your edited version is allowed outright.

Underneath, this is the plugin and marketplace mechanism from Claude Code, repointed from software engineers to office roles.

Getting started

The plugins do nothing on their own. You need either Claude Code, the terminal agent, or Claude Cowork, Anthropic's agentic desktop tool for non-technical knowledge workers, which the README positions as "Claude Code for the rest of your work". Cowork is the primary target; the same plugins also install into Claude Code.

Installation is two terminal commands in Claude Code (add the marketplace, then install the plugin you want; the repository README carries the exact lines) or a single click inside Cowork. The address is github.com/anthropics/knowledge-work-plugins, and a plain clone is enough to read and edit the files.

On cost: the repository is free under Apache 2.0 and contains no paid component, but the intelligence is not free. These files are instructions for Anthropic's hosted Claude, and there is no local-model path here. Nothing above states which Claude plan or API access Cowork and Claude Code require, so check Anthropic's own pricing before planning a team rollout. The connectors need your existing accounts and credentials for Salesforce, Slack, Snowflake and the rest, which carry their own licences.

The project does not list hardware requirements: no operating system, chip, memory or VRAM figures appear in the material.

When to use it / when not

The main catch, stated plainly: plugins stay local for now, so there is no built-in way to publish one tuned plugin out to a whole department, and Cowork, the product these are built for, has already had security bugs reported. Giving an agent connector access to your CRM and document store is a decision worth making with that in mind.

Use it instead of just asking Claude in a chat window when the task repeats every week and the right answer depends on your own process: your pipeline stages, your contract clauses, your month-end checklist. Writing that down once as a skill beats pasting the same context into every conversation.

Don't use it if you only need one-off answers, if you cannot install Claude Code or the Cowork app, or if the legal and finance documents in question cannot be sent to a hosted model at all.

Alternatives

  • Claude Code with your own hand-written skills and commands: the same capability, without the starting library. This repository is a set of worked examples, not a new feature.
  • Custom GPTs and the assistant marketplaces inside other chat products: a similar idea, but those configurations are closed and locked in an app, while these are plain files you can read, diff and fork.
  • The Cowork Plugin Management plugin in this same repository, if none of the eleven roles matches the job you have in mind and you would rather build one.

Anyone running a team that already pays for Claude should read this repository even before installing anything, because it is the clearest available statement of what Anthropic thinks a job-specific agent consists of, and it is short enough to read in an afternoon. The honest expectation is a head start on writing your own instructions, not a finished department-ready specialist: the plugins are generic by necessity, sharing is still manual, and the security questions around Cowork are open. For a sales or support lead willing to edit Markdown, that head start is worth real time.

More in AI agents & assistants

All of AI agents & assistants →