Knowledge Work Plugins

Knowledge Work Plugins is a collection of file-based plugins that extend Claude with role-specific skills, slash commands, and tool connectors. It's built for Claude Cowork and also works with Claude Code, and it's meant for teams and individuals who want Claude to behave like a specialist in their function (sales, finance, legal, product, data, and more) rather than a generic assistant. Anyone customizing internal AI workflows for a company or team is the target user here.

Each plugin bundles domain knowledge into skills, exposes explicit actions via slash commands, and wires up external tools (CRMs, project trackers, data warehouses, design tools) through MCP servers. Everything is markdown and JSON: no code, no build steps, no infrastructure to run.

Key features

• 11 pre-built plugins: covers productivity, sales, customer-support, product-management, marketing, legal, finance, data, enterprise-search, bio-research, and a plugin-management plugin for building your own.
• Skills: encode domain expertise and step-by-step workflows that Claude draws on automatically when relevant, without you invoking anything.
• Slash commands: explicit actions like /sales:call-prep or /finance:reconciliation that you trigger directly in a session.
• Connectors via MCP: each plugin ships an .mcp.json wiring Claude to tools such as Slack, Notion, Jira, HubSpot, Snowflake, Databricks, BigQuery, Figma, and dozens more depending on the role.
• Consistent plugin structure: every plugin follows the same layout (plugin.json manifest, .mcp.json, commands/, skills/), making them easy to read, fork, and modify.
• Customization-first design: plugins are meant to be edited, swap connectors, add company terminology, adjust workflows, or build entirely new plugins with the cowork-plugin-management plugin.

Ideal use cases

• A sales, support, finance, legal, or product team wants Claude to follow their specific workflows and terminology instead of generic advice, and is willing to edit skill files and .mcp.json to reflect their actual tool stack.
• An admin or team lead wants to standardize how AI is used across a function, so slash commands and skills get shared and everyone works from the same playbook.
• A life sciences team wants preclinical research connectors (PubMed, ClinicalTrials.gov, ChEMBL, Benchling) already wired up via the bio-research plugin.
• A developer or ops person wants to build a net-new plugin for a role not covered here, using the existing plugins as a template.
• This is not a fit if you're looking for a hosted SaaS product with a UI, a general-purpose chatbot, or something that works without Claude Cowork or Claude Code. It's also not useful if your team has no interest in customizing connectors or skill files, since the out-of-the-box plugins are generic starting points, not finished company-specific tools.

Installation

For Cowork, install plugins directly from the marketplace:

Install from claude.com/plugins

For Claude Code, add the marketplace and install a plugin:

# Add the marketplace first
claude plugin marketplace add anthropics/knowledge-work-plugins

# Then install a specific plugin
claude plugin install sales@knowledge-work-plugins

Once installed, plugins activate automatically: skills fire when relevant, and slash commands become available in your session, e.g. /sales:call-prep or /data:write-query.

To customize a plugin, edit its files directly:

• Edit .mcp.json to swap connectors for your own tool stack.
• Add company terminology and processes into the skills/ files.
• Modify skill instructions so they match how your team actually works.
• Use the cowork-plugin-management plugin, or copy the standard plugin structure, to build new plugins for roles not yet covered.

Contributing is straightforward since plugins are just markdown and JSON files: fork the repo, make changes, and submit a PR.