Source: Anthropic launch announcement — Jan 30 2026 + earlier ai-research (web research, 2026-04-11); operator walkthrough (2026-10-28): raw/Claude_Cowork_Plugins_Explained_How_to_use_them.md, raw/Build_Agent_Teams_within_Claude_Cowork_in_17_min.md, raw/CLAUDE_COWORK_FULL_COURSE_2+_Hours.md (Ben AI)

The 11 open-sourced launch plugins (from the Jan 30 blog, repo anthropics/knowledge-work-plugins): Productivity, Enterprise Search, Plugin Create/Customize, Sales, Finance, Data, Legal, Marketing, Customer Support, Product Management, Biology Research. The Feb 24 2026 upgrade added 10 new department-specific plugins, 12 new MCP connectors, and the private marketplace for admins.

Claude Cowork (the collaborative workspace product, distinct from Claude Code) has its own plugin ecosystem designed for business teams. Plugins bundle skills, connectors, and sub-agents into single packages that extend Cowork’s capabilities across departments. Available on all paid plans (Pro, Max, Team, Enterprise), these plugins turn Cowork into a department-specific automation platform.

Initial Launch

  • Launched with 11 open-source plugins at initial release
  • Each plugin bundles skills + connectors + sub-agents into a single installable package
  • Designed for non-technical business users — no coding required to install or configure

February 24, 2026 Upgrade

The February upgrade significantly expanded the Cowork plugin ecosystem:

  • Private plugin marketplaces — companies can create and share proprietary plugins internally
  • 10 new department-specific plugins (see categories below)
  • 12 new MCP connectors — expanding the range of external systems Cowork can access
  • Cross-app workflows — e.g., Excel data flowing directly into PowerPoint presentations
  • Total plugin count grew from 11 to 21+ official plugins

Department-Specific Plugin Categories

Cowork plugins are organized by business function:

  • Marketing ops — campaign automation, content calendars, performance dashboards
  • Sales — pipeline management, lead scoring, outreach sequences
  • Finance — expense tracking, reporting, budget forecasting
  • Legal — contract review, compliance checking, document management
  • Product management — roadmap planning, feature prioritization, user research synthesis
  • HR — recruiting workflows, onboarding, employee engagement
  • Engineering — code review, deployment pipelines, incident management
  • Design — asset management, design review, handoff workflows
  • Operations — process automation, logistics, vendor management
  • Data analysis — data pipelines, visualization, insight generation
  • Bio research — literature review, experiment tracking, protocol management

Customize Admin System

  • New admin control system called “Customize” introduced with the Feb 2026 upgrade
  • Controls which workflows and plugins are available organization-wide
  • Admins can:
    • Enable/disable specific plugins per department or team
    • Set default plugin configurations
    • Monitor plugin usage and adoption metrics
    • Create custom plugin bundles tailored to specific roles

Availability

  • Available to all paid plans: Pro, Max, Team, Enterprise
  • Companies can create and share their own private plugins
  • Private plugin marketplaces enable internal distribution without publishing publicly

Building and sharing your own plugins (Ben AI, added 2026-10-28)

Sources: raw/Claude_Cowork_Plugins_Explained_How_to_use_them.md (Creator: Ben AI · URL: https://www.youtube.com/watch?v=sgSrcSUck7U · Duration: 12:14 · Platform: YouTube · Uploaded: 2026-02-14); the plugins and agents chapters of raw/CLAUDE_COWORK_FULL_COURSE_2+_Hours.md (https://www.youtube.com/watch?v=2HyBA-wkWsA, uploaded 2026-04-04) repeat that video and raw/Build_Agent_Teams_within_Claude_Cowork_in_17_min.md (https://www.youtube.com/watch?v=A6RbawFHC80, uploaded 2026-03-04) nearly word for word.

  • What’s inside. Ben describes a plugin as “a USB stick” of expertise: skills, connectors, commands and agent instruction files. Commands are the part he stresses: a markdown file that runs several skills in sequence. His marketing plugin’s /repurpose command calls the LinkedIn-post, GIF-creator and newsletter skills from one YouTube link; his sales plugin’s “outbound pipeline” command runs lead qualification, lead intelligence and personalised outreach, each skill pointing to an agent.md that tells its parallel sub-agents what to do. Full build prompts in Cowork Sales Skills and Bulk Sub-Agents.
  • Why connectors sit in plugins. His reading: companies will want a support team to reach support tools but not the sales CRM, so connectors ship per department rather than company-wide (his interpretation, not Anthropic’s stated reason).
  • Using a plugin skill. Type / → Plugins → department → skill, or just describe the task (“I want to prepare for a sales call”) and Claude picks the skill.
  • Customising Anthropic’s plugins. Open a skill and ask Claude to adapt it (“adjust the draft outreach skill and add some examples of your outreach templates”), or click Customize on a whole plugin and describe your company’s way of working.
  • His build order: skills first; bundle them into a plugin once you have a set; add commands when you want multi-skill workflows. Ask “can you create a plugin for me?” listing the skills, connectors and commands, then click Add to plugins.
  • Sharing (as of February-April 2026). Plugins and skills you create are saved to your own account only. Ben’s routes: ask Claude for a zip and have teammates upload it (Plugins → + → Upload plugin; also the fallback when the Install button fails), or put it on GitHub for a versioned link, which he says needs a marketplace set up with Claude Code. In the February video he says Anthropic had confirmed organisation-wide sharing and private marketplaces were “coming soon”; this article’s February 24 section records private marketplaces shipping ten days later. The April course replays the February segment unchanged, so its “zip or GitHub only” advice was already dated when published.
  • Three plugin sources he expects: Anthropic’s department plugins, third-party plugins (including SaaS vendors packaging their own workflows, which he sees as a possible survival route for SaaS), and custom company plugins. He notes that Salesforce, ServiceNow and Adobe shares fell when plugins launched; the wiki has not checked that claim.

Key Takeaways

  • Cowork plugins are designed for business users, not developers — they extend Cowork’s AI capabilities into specific departments
  • The Feb 2026 upgrade was a major expansion: private marketplaces, 10 new department plugins, 12 new MCP connectors, cross-app workflows
  • The “Customize” admin system gives orgs fine-grained control over which plugins are available to which teams
  • Cross-app workflows (e.g., Excel to PowerPoint) eliminate manual data transfer between tools
  • All paid plans have access — this is not gated to Enterprise

Try It

  1. Open Claude Cowork and navigate to the plugin marketplace to browse available department plugins
  2. Install the plugin most relevant to your team’s function (e.g., Marketing Ops for campaign automation)
  3. Use the “Customize” admin panel (Team/Enterprise) to control which plugins your org has access to
  4. If your company has proprietary workflows, explore creating a private plugin marketplace for internal distribution
  5. Test cross-app workflows — try pushing data from a spreadsheet analysis directly into a presentation

Open Questions

  • How do Cowork plugins differ architecturally from Claude Code plugins? Can one be used in the other?
  • What is the approval/review process for private marketplace plugins?
  • Are the 12 new MCP connectors available independently or only through Cowork plugins?
  • Do plugin command.md files still behave as Ben shows after the September 2026 chat/Cowork merge?