● Official
anthropics
⚡ Instant
Knowledge Work Plugins
by anthropics · anthropics/knowledge-work-plugins
Anthropic-curated plugin/skill bundle aimed at knowledge workers using Claude Cowork — docs, comms, analysis, and PM flows.
Knowledge Work Plugins is a Claude skill maintained by anthropics. Anthropic-curated plugin/skill bundle aimed at knowledge workers using Claude Cowork — docs, comms, analysis, and PM flows. See README for installation and configuration: https://github.com/anthropics/knowledge-work-plugins
Why use it
Key features
- Anthropic-curated plugin/skill bundle aimed at knowledge workers using Claude Cowork — docs, comms, analysis, and PM flows.
- Language: Python
- 12075+ GitHub stars at verification time
- Official project
Live Demo
What it looks like in practice
knowledge-work-plugins.replay
▶ ready
Use Cases
Real-world ways to use Knowledge Work Plugins
When to use: See repo README for canonical use cases.
Prerequisites
- Repo cloned or installed — See https://github.com/anthropics/knowledge-work-plugins
Flow
-
Install
Install Knowledge Work Plugins per README.✓ Copied
→ Tool registered with client
-
Configure
Provide credentials/config as instructed.✓ Copied
→ Successful auth/init
-
Use
Run a sample task with Knowledge Work Plugins.✓ Copied
→ Expected output
Outcome: You can drive the documented workflow end-to-end.
Pitfalls
- Skipping README — Read the repo README and CHANGELOG before shipping to prod.
Cost & Limits
What this costs to run
- API quota
- None of its own; bounded by upstream provider quotas if any
- Tokens per call
- Depends on usage
- Monetary
- Open source — check repo LICENSE
- Tip
- Review upstream API costs (if any) before automating.
Security
Permissions, secrets, blast radius
Minimum scopes: Whatever the upstream provider requires
Credential storage: Env vars or local config — never commit secrets
Data egress: Forwards data per its README
Never grant: Full admin to untrusted prompts
- Project moves fast — pin a version in production.
Troubleshooting
Common errors and fixes
Auth fails
Verify credentials and required scopes match README.
Verify: Re-read repo README auth section.
Tool not found by client
Ensure MCP client config points to correct command/path.
Verify: Restart the client after editing config.