Skills aimed at roles, not repositories
Most of the skills repositories trending on GitHub are built for engineers. This one is the opposite, and that is the reason to know it exists. Knowledge Work Plugins turn Claude into a specialist for a job function: sales, legal, finance, marketing, support, and more. They are built for Claude Cowork, where you set a goal and Claude delivers finished work, and they are also compatible with Claude Code. Each plugin bundles the skills, connectors, slash commands, and sub-agents for one role, so Claude starts with a strong sense of how that job is done.
The framing the README is honest about is that out of the box, a plugin is a strong starting point, and the real power comes from customizing it to your company: your tools, your terminology, your processes. Treat these as templates for a role, not finished products for your specific team.
The eleven plugins, and what they connect to
The collection covers a working organization end to end, and the connector lists are the tell that these are meant to plug into real SaaS, not operate in a vacuum:
- productivity (Slack, Notion, Asana, Linear, Jira, Microsoft 365), sales (HubSpot, Close, Clay, ZoomInfo), and customer-support (Intercom, HubSpot, Guru) for the front office.
- product-management (Linear, Figma, Amplitude, Pendo), marketing (Canva, Figma, Ahrefs, Klaviyo), legal (Box, Egnyte), and finance (Snowflake, Databricks, BigQuery) for specialist functions.
- data (Snowflake, Databricks, Hex), enterprise-search (one query across Slack, Notion, Guru, Jira), and the notably specialized bio-research (PubMed, bioRxiv, ChEMBL, Open Targets, Benchling) for analysis-heavy work.
- cowork-plugin-management, which exists to help you create or customize the others for your organization.
Install
From Claude Code, add the marketplace then install a specific role plugin:
claude plugin marketplace add anthropics/knowledge-work-plugins
claude plugin install sales@knowledge-work-pluginsFrom Claude Cowork, install them directly at claude.com/plugins. Either way, you then connect the SaaS tools the plugin expects and, ideally, customize it for your team. It is Apache-2.0 licensed.
The part to plan for: connectors and customization
The honest caveat is that the value scales with setup. A role plugin’s connectors list the integrations it can use, which means realizing its potential involves wiring Claude into your company’s systems, with the data-access and permission decisions that implies. The finance plugin reaching Snowflake or the sales plugin reaching HubSpot is powerful precisely because it touches live company data, so adoption is as much an IT and governance question as a download. Budget for the customization the README points to, rather than expecting the out-of-box plugin to match your team’s workflow exactly. With 145 open issues as of 2026-06, the collection is young and actively evolving.
Customization is a workflow, not an afterthought
The repository treats customization as first-class, which is why one of the eleven plugins, cowork-plugin-management, exists solely to help you create new plugins or adapt the existing ones for your organization. That is the tell for how these are meant to be used: you start from a role plugin, then teach it your company’s terminology, your specific tools, and the way your team actually runs a given workflow, so the output stops being generic and starts looking like it was built in-house. The payoff is consistency: when everyone in a function shares a customized plugin, Claude produces work that matches the team’s conventions instead of each person re-explaining context every time. The cost is the upfront effort to encode that context, and the governance of which data and tools the plugin is allowed to reach. Plan the rollout as you would any internal tool, with an owner for each plugin rather than letting them drift.
knowledge-work-plugins versus anthropics/skills
| knowledge-work-plugins | anthropics/skills | |
|---|---|---|
| Stars | 20,002 | 148,807 |
| Audience | knowledge workers by role | developers and general |
| Unit | role plugin with connectors | individual skill |
| Home | Claude Cowork, also Claude Code | Claude Code, Claude.ai, API |
Counts are from GitHub as of June 2026. anthropics/skills is the developer-facing reference collection and the spec. This repository is its counterpart for the rest of the company: bundled by job function, wired to business SaaS, and built for Cowork. If your user is an account executive or a financial analyst rather than an engineer, this is the relevant Anthropic repository.
Related
For the developer-facing reference and the skills spec, see anthropics/skills. To manage plugins across Claude tools, see cc-switch. For what else is climbing, see LLM tooling, the daily digest, and the weekly report.
FAQ
Who are these plugins for? Knowledge workers by role, sales, legal, finance, marketing, support, product, data, and more, rather than engineers. They are built for Claude Cowork and also work in Claude Code.
Do they need my company’s tools connected? To reach their potential, yes. Each plugin lists connectors such as Slack, HubSpot, or Snowflake, so realizing the value involves integration and the access decisions that come with it.
Are they ready to use as-is? They are a strong starting point. The README is clear that the real power comes from customizing them to your tools, terminology, and processes.
What license are they? Apache-2.0.