Anthropic Knowledge Work Plugins — Summary

Anthropic's Knowledge Work Plugins is the official collection of role-specialized plugin bundles built for Claude Cowork (and compatible with Claude Code), each targeting a specific job function (Engineering, Sales, Finance, Legal, Marketing, etc.) by bundling domain skills, slash commands, and MCP connector configurations into a single installable unit.

Problem it solves: Knowledge workers in specific roles (engineer, salesperson, legal professional, etc.) need domain-specific workflows, terminology, and tool integrations pre-loaded for Claude to function as a true role specialist; generic skill packs don't know whether they're helping a finance analyst or an engineer.

Distinctive trait: Every plugin follows a four-part structure (skills + commands + .mcp.json connectors + plugin.json manifest), and the .mcp.json files wire Claude directly to real enterprise tools (Slack, Linear, HubSpot, Asana, Jira, Notion, Snowflake, BigQuery) via HTTP MCP servers — making these the only official skill packs in the corpus that ship production MCP connector configurations.

Target audience: Enterprises deploying Claude Cowork for specific role teams; also usable individually via Claude Code with /plugin install.

Scope: 11+ first-party role plugins (plus 30+ partner-built plugins in the marketplace.json), covering engineering, sales, finance, legal, marketing, data, HR, design, operations, product management, customer support, and bio-research.

Differs from seeds: Unlike superpowers or agent-skills (Archetype 1 — methodology enforcement), knowledge-work-plugins are domain-specific reference packs combining skills + commands + live MCP connector configs. The MCP connector pattern makes them closer to taskmaster-ai (Archetype 3) but the value is domain expertise, not task decomposition.

Anthropic Knowledge Work Plugins — Overview

Origin

Official Anthropic repository. Apache-2.0 license. Stars: 16,165 with 23 contributors. Active as of 2026-05-26 (same-day push). Built for Claude Cowork product.

Purpose

From the README:

"Plugins that turn Claude into a specialist for your role, team, and company. Built for Claude Cowork, also compatible with Claude Code." "Each plugin bundles the skills, connectors, slash commands, and sub-agents for a specific job function. Out of the box, they give Claude a strong starting point for helping anyone in that role. The real power comes when you customize them for your company — your tools, your terminology, your processes — so Claude works like it was built for your team."

Design Philosophy

"Every component is file-based — markdown and JSON, no code, no infrastructure, no build steps."

"These plugins are generic starting points. They become much more useful when you customize them for how your company actually works:

• Swap connectors — Edit .mcp.json to point at your specific tool stack.
• Add company context — Drop your terminology, org structure, and processes into skill files.
• Adjust workflows — Modify skill instructions to match how your team actually does things."

Plugin Structure Standard

Every plugin follows:

plugin-name/
├── .claude-plugin/plugin.json   # Manifest
├── .mcp.json                    # Tool connections (HTTP MCP servers)
├── commands/                    # Slash commands you invoke explicitly
└── skills/                      # Domain knowledge Claude draws on automatically

Partner Plugin Ecosystem

The marketplace.json lists 30+ third-party partner plugins (Figma, Zapier, Zoom, Box, Prisma, CockroachDB, Mintlify, Postiz, Intercom, Cloudinary, etc.) alongside the first-party plugins — making this the most expansive plugin marketplace in the batch.

Cowork vs Code

Built primarily for Claude Cowork (team/enterprise product) but Claude Code users can install via:

claude plugin marketplace add anthropics/knowledge-work-plugins
claude plugin install sales@knowledge-work-plugins

Anthropic Knowledge Work Plugins — Architecture

Distribution

• Type: Claude Code plugin marketplace (Claude Cowork primary; Claude Code secondary)
• Claude Code install:

  claude plugin marketplace add anthropics/knowledge-work-plugins
  claude plugin install sales@knowledge-work-plugins
  claude plugin install engineering@knowledge-work-plugins
  

• Claude Cowork: Install from claude.com/plugins/

Required Runtime

None — pure markdown and JSON files. MCP connectors reference external HTTP services (Slack MCP at mcp.slack.com, Linear at mcp.linear.app, etc.) that require network access and OAuth credentials.

Repository Structure

anthropics/knowledge-work-plugins/
├── .claude-plugin/
│   └── marketplace.json         # 20+ first-party + 30+ partner plugins
├── engineering/
│   ├── .claude-plugin/plugin.json
│   ├── .mcp.json                # Slack, Linear, Asana, Jira, Notion, GitHub
│   ├── CONNECTORS.md
│   ├── README.md
│   └── skills/
│       ├── architecture/
│       ├── code-review/
│       ├── debug/
│       ├── deploy-checklist/
│       ├── documentation/
│       ├── incident-response/
│       ├── standup/
│       ├── system-design/
│       ├── tech-debt/
│       └── testing-strategy/
├── sales/
│   ├── .claude-plugin/plugin.json
│   ├── .mcp.json                # Slack, HubSpot, Close, Clay, ZoomInfo, etc.
│   ├── skills/
│   │   ├── account-research/
│   │   ├── call-prep/
│   │   ├── call-summary/
│   │   ├── competitive-intelligence/
│   │   ├── create-an-asset/
│   │   ├── daily-briefing/
│   │   ├── draft-outreach/
│   │   ├── forecast/
│   │   └── pipeline-review/
├── finance/
├── legal/
├── marketing/
├── data/
├── product-management/
├── customer-support/
├── productivity/
├── enterprise-search/
├── bio-research/
├── human-resources/
├── design/
├── operations/
├── small-business/
├── cowork-plugin-management/
├── pdf-viewer/
└── partner-built/
    ├── slack/ (Salesforce)
    ├── apollo/ (Apollo.io)
    ├── common-room/
    └── brand-voice/ (Tribe AI)

Engineering Plugin .mcp.json (representative)

{
  "mcpServers": {
    "slack": {"type": "http", "url": "https://mcp.slack.com/mcp", "oauth": {...}},
    "linear": {"type": "http", "url": "https://mcp.linear.app/mcp"},
    "asana": {"type": "http", "url": "https://mcp.asana.com/v2/mcp"},
    "atlassian": {"type": "http", "url": "https://mcp.atlassian.com/v1/mcp"},
    "notion": {"type": "http", "url": "https://mcp.notion.com/mcp"},
    "github": {"type": "http", "url": "https://api.githubcopilot.com/mcp/"}
  }
}

All MCP connections are HTTP (streamable-http / SSE), not stdio.

Plugin Manifest Structure

Each plugin has its own .claude-plugin/plugin.json:

{
  "name": "engineering",
  "version": "1.2.0",
  "description": "...",
  "author": {"name": "Anthropic"}
}

CONNECTORS.md

Each plugin includes CONNECTORS.md listing available integrations with instructions for connecting each tool.

Anthropic Knowledge Work Plugins — Components

Commands (per plugin)

Commands are slash commands you invoke explicitly. Representative set from engineering plugin:

Exact command counts per plugin: not fully enumerable without listing each plugin's commands/ directory, but the README confirms commands exist for each plugin.

Skills (per plugin, representative)

Engineering Plugin (10 skills)

Sales Plugin (9 skills)

Other plugins follow similar 8-12 skill counts per domain.

MCP Connectors (per plugin)

This is the unique component. Each plugin's .mcp.json configures HTTP MCP servers for real enterprise tools:

Partner Plugins in Marketplace (30+)

Representative partner plugins (from marketplace.json): Figma, Zapier, Zoom, Box, Prisma, CockroachDB, Mintlify, Postiz, Intercom, Cloudinary, Nimble, Bright Data, SearchFit SEO, Atlan, Miro, PlanetScale, LSEG, S&P Global, Slack (Salesforce), Apollo.io, Common Room, ZoomInfo, Vanta, Sanity, and more.

Subagents

None defined explicitly; plugin descriptions mention "sub-agents" in the cowork-plugin-management plugin description but no persona files found.

Hooks

None.

Anthropic Knowledge Work Plugins — Uniqueness

Differs from Seeds

No seed framework parallels this role-specialized plugin design with live MCP connector bundles:

• Unlike superpowers and agent-skills (Archetype 1 — development methodology), knowledge-work-plugins are role-specific domain plugins with no development workflow enforcement.
• Unlike anthropics/skills (reference gallery for developers), knowledge-work-plugins target knowledge workers — sales reps, legal teams, finance analysts, engineers — in enterprise contexts.
• The MCP connector pattern (.mcp.json with HTTP MCP servers for Slack, HubSpot, Snowflake, etc.) is closest to ccmemory's Archetype 3 (MCP-anchored toolserver), but knowledge-work-plugins don't ship their own MCP server — they configure connections to external hosted MCP services.
• The marketplace.json with 50+ plugins (first-party + partner) is the largest curated plugin marketplace in the batch.

Positioning

The enterprise-grade, role-specialized counterpart to the more developer-centric skill packs. Designed for non-developer knowledge workers who need Claude to understand their domain, tools, and workflows without configuration.

Most Interesting Component

The .mcp.json HTTP connector pattern — particularly the OAuth-gated Slack connector at mcp.slack.com/mcp — represents production-level infrastructure that doesn't require the user to configure MCP servers themselves. This is "batteries included" for enterprise MCP.

The partner ecosystem marketplace (Figma, Zapier, Zoom, Box, LSEG, S&P Global, Vanta, etc.) converts the repository into a verified plugin registry for enterprises.

Observable Failure Modes

1. Connector dependency — "Supercharged" features require OAuth setup for each tool. Without connected tools, the skills degrade to standalone text-based workflows.
2. No session enforcement — skills activate by description matching only; no guarantee the right skill fires for a given enterprise workflow.
3. Generic starting points — the README acknowledges plugins need customization for each organization. Teams that don't customize get generic domain skills without company-specific context.
4. Claude Cowork lock — optimal experience requires the Cowork product; Claude Code install works but some Cowork-specific features may not transfer.
5. Partner plugin SHA pinning — partner plugins are pinned to specific commits in marketplace.json; there's no automatic update mechanism visible in the repo.

Explicit Antipatterns

From README: "The real power comes when you customize them for your company" — implies using without customization is an antipattern.