Skip to main content
Knowledge Work Plugins turn Claude into a specialist for your role, team, and company. Each plugin bundles the skills, connectors, slash commands, and sub-agents needed for a specific job function.

​
Plugin architecture

Every plugin follows the same file-based structure. No code, no infrastructure, no build steps — just markdown and JSON. 
plugin-name/
├── .claude-plugin/
│   └── plugin.json          # Plugin manifest
├── .mcp.json                # MCP server connections
├── commands/                # Slash commands
│   ├── command-1.md
│   └── command-2.md
└── skills/                  # Domain expertise
    ├── skill-1/
    │   ├── SKILL.md
    │   └── references/      # Optional supporting docs
    └── skill-2/
        └── SKILL.md

​
Plugin manifest

The plugin.json file defines your plugin’s metadata:
.claude-plugin/plugin.json
{
  "name": "sales",
  "version": "1.1.0",
  "description": "Prospect, craft outreach, and build deal strategy faster. Prep for calls, manage your pipeline, and write personalized messaging that moves deals forward.",
  "author": {
    "name": "Anthropic"
  }
}
The plugin name must match the directory name and should use lowercase with hyphens (kebab-case).

​
MCP configuration

The .mcp.json file connects your plugin to external tools via Model Context Protocol servers:
.mcp.json
{
  "mcpServers": {
    "hubspot": {
      "type": "http",
      "url": "https://mcp.hubspot.com/anthropic"
    },
    "slack": {
      "type": "http",
      "url": "https://mcp.slack.com/mcp"
    },
    "notion": {
      "type": "http",
      "url": "https://mcp.notion.com/mcp"
    }
  }
}
See MCP integration for details on how Claude uses these connections.

​
How plugins activate

Once installed, plugins work automatically:
1

Skills activate contextually

When you describe a task that matches a skill’s domain, Claude automatically draws on that skill’s expertise and workflows.
2

Commands are explicitly invoked

Use slash commands to trigger specific workflows: /sales:call-prep, /pipeline-review, /forecast
3

Connectors provide data

When configured, MCP servers give Claude access to your CRM, project management tools, data warehouses, and more.

​
Component types

​
Skills

Skills encode domain expertise, best practices, and step-by-step workflows. Claude draws on them automatically when relevant. Example: The call-prep skill activates when you say “prep me for my call with Acme Corp” — no command needed. Learn more: Skills

​
Commands

Commands are explicit actions you trigger with slash syntax. They’re perfect for repeatable workflows you want to invoke on demand. Example: /call-summary <notes> processes call notes into action items and follow-up emails. Learn more: Commands

​
Connectors

Connectors wire Claude to external tools via MCP servers. They provide read/write access to your company’s systems. Example: The HubSpot connector lets Claude pull account history, update deal stages, and create tasks. Learn more: Connectors

​
Standalone vs supercharged

Plugins are designed to work with or without external tool connections:

Standalone mode

Works with manual input and web research. You provide context, Claude provides expertise.

Supercharged mode

When you connect your tools via MCP, Claude can pull data automatically and update systems for you.

​
Example: Call prep skill

  • You tell Claude: company name, meeting type, attendees
  • Claude does web research: recent news, funding, leadership
  • Output: prep brief with agenda and suggested questions
  • CRM: account history, contacts, opportunities, activities
  • Email: recent threads, open questions, commitments
  • Chat: internal discussions, colleague insights
  • Transcripts: prior call recordings, key moments
  • Calendar: auto-find meeting, pull attendees

​
Customization philosophy

The marketplace plugins are generic starting points. They become powerful when you customize them for your company:
1

Swap connectors

Edit .mcp.json to point at your specific tool stack
2

Add company context

Drop your terminology, org structure, and processes into skill files
3

Adjust workflows

Modify skill instructions to match how your team actually works
4

Create new components

Add skills and commands for workflows unique to your company

​
File-based simplicity

Because plugins are just markdown and JSON:
  • Easy to version control — Track changes with git
  • Easy to share — Fork, modify, and distribute to your team
  • Easy to customize — Edit in any text editor
  • Easy to understand — No code to decipher

​
Next steps

Skills

Learn how skills encode domain expertise

Commands

Understand slash commands and workflows

Connectors

Connect Claude to your tools

MCP integration

Deep dive on Model Context Protocol

Build docs developers (and LLMs) love

Get started for freeTalk to us