Knowledge Work Plugins is Anthropic's open collection of plugins for Claude Cowork and Claude Code, each aimed at a job function. Install the sales plugin and Claude gets slash commands for call prep and pipeline review; the finance one knows how to prepare journal entries and reconciliations; others cover legal, customer support, product management, marketing, data, design, engineering, HR, operations, small business and life-sciences research.
Each plugin is just Markdown and JSON: skills that hold the domain know-how and step-by-step workflows, slash commands you trigger yourself, and an .mcp.json listing the connectors, such as Slack, HubSpot, Jira, Notion or Snowflake, that the plugin expects. That makes them easy to read and easy to adapt, which is the point: the README pitches them as starting points to customise with your own tools, terms and processes.
The marketplace file now lists more than 120 plugins, most of them contributed by other companies and pulled from their own repositories. Only Anthropic's own plugins and a handful of partner ones live in this repository; the rest were not part of this scan.
- Repository: github.com/anthropics/knowledge-work-plugins
- Licence: Apache-2.0 (Apache License 2.0)
- Language: Python. Stars: 33.1K. Forks: 3,647. Last push: Oct 26, 2026.
- Scan: safe, Oct 26, 2026, commit 33d3dea
Who it is for
Claude Cowork and Claude Code users who want role-specific workflows ready to go, and teams that want a template for writing their own company plugins.
Getting started
1. In Claude Code, add the marketplace
claude plugin marketplace add anthropics/knowledge-work-plugins2. Install a plugin, for example sales
claude plugin install sales@knowledge-work-pluginsIn Claude Cowork, install them from claude.com/plugins instead. Connectors listed in a plugin still need you to sign in to each service.
Safety scan
We cloned anthropics/knowledge-work-plugins at commit 33d3dea on Oct 26, 2026 and ran the checks described on the GitHub Tools page: credential patterns, decode-and-execute code, install-time scripts, committed binaries, risky CI workflows, every host the code talks to, known vulnerabilities in pinned dependencies, and project hygiene. A person read every hit. This is what we found.
- No secrets, no committed binaries, no install hooks and no bare-IP URLs. There are no known advisories; the only lockfile is a four-package requirements.txt in one bio-research skill.
- The one pattern hit is bio-research/skills/nextflow-development/scripts/check_environment.py, which suggests the official Nextflow curl | bash installer as a fix when Nextflow is missing. It prints the command; it does not run it.
- Two workflows use pull_request_target, close-external-prs.yml and external-pr-scope-guard.yml. Both check out the base repository only, never the pull request, so contributed code is not run with the repository's secrets.
- The plugin marketplace lists 123 plugins, and most third-party ones are fetched from their makers' repositories. Those were not scanned here; read a partner plugin's skills and .mcp.json before installing it.
- Six workflows in total; both third-party actions are pinned to a commit. Apache 2.0 licence present; no security policy, Dependabot or CodeQL.
What the scanner counted
| Check | Result |
|---|---|
| Secrets | None found. |
| Suspicious code | 1 pattern hit found and read; every one is listed under the raw findings. |
| Install-time code | None: nothing runs at install beyond the package manager itself. |
| Committed binaries | None. |
| CI workflows | 6 workflows. 2 use pull_request_target, none check out the pull request head. 0 of 2 third-party actions pinned to a tag rather than a commit. |
| Network hosts | 10 distinct hosts referenced from source; most often eutils.ncbi.nlm.nih.gov, gitlab.com, purl.allotrope.org, www.ebi.ac.uk. No URLs to bare IP addresses. |
| Known vulnerabilities | 0 advisories across 4 pinned packages: 0 critical, 0 high, 0 moderate, 0 low. bio-research/skills/instrument-data-to-allotrope/requirements.txt: 4 packages, 0 advisories. |
| Project hygiene | Has licence file. Missing security policy, automated dependency updates, CodeQL, contributing guide. |
| OpenSSF Scorecard | Not scored: the project is not in Scorecard's weekly index. |
The raw findings
Every hit the scanner wrote out, with a link to the exact line at the scanned commit. Secrets candidates are redacted.
Pattern hits (1)
| Where | Rule | Match |
|---|---|---|
| bio-research/skills/nextflow-development/scripts/check_environment.py:120 | download-piped-to-shell | fix="curl -s https://get.nextflow.io | bash && mv nextflow ~/bin/ && export PATH=$HOME/bin:$PATH" |
Workflows worth a look
- .github/workflows/close-external-prs.yml: pull_request_target
- .github/workflows/external-pr-scope-guard.yml: pull_request_target
By the numbers
| Stars | 33.1K |
|---|---|
| Forks | 3,647 |
| Contributors | 32 |
| Commits | 1,124 |
| Open issues | 88 |
| Open pull requests | 54 |
| Releases | 0 |
| Latest release | none tagged |
| Licence | Apache-2.0 |
| Main language | Python |
| Project age | 9 months |
| Last push | Oct 26, 2026 |
| Tracked files | 1,285 |
| Lines of code | 201.7K |
| Checkout size | 8 MB |
Lines by language: Markdown 183.8K, Python 9,767, HTML 3,429, JSON 2,741, YAML 1,771, JavaScript 154.
Questions
Are the Knowledge Work Plugins free?
Yes. The repository is Apache 2.0, so you can use, modify and share the plugins. You need a Claude plan that includes Cowork or Claude Code to run them, and some connectors need accounts with those services.
Do I need to code to use or customise them?
No. Every plugin is Markdown and JSON. Editing a skill file changes how Claude does that job, and editing .mcp.json changes which tools it connects to. The cowork-plugin-management plugin helps you build new ones.
Do these plugins work in Claude Code?
Yes. They are built for Claude Cowork and also install in Claude Code through the plugin marketplace commands, after which their slash commands, such as /sales:call-prep, appear in your session.
This post is part of GitHub Tools, where every repository is cloned and scanned before it is written up. The scan is a snapshot of one commit on one day; the repository has moved on since, so check it before you install.