What Is a Plugin? An Engineer's Guide to Installing a Whole Claude Workflow at Once
You know browser extensions and AutoCAD add-ins. A Claude Plugin is the same idea: one package that adds a work procedure, access to your tools and ready-made commands. Install it once, and the whole team works the same way.
01First: what a plugin means in general
A plugin (add-on) is something you add to an existing program to extend what it can do, without changing the program itself. A browser extension that blocks ads, a WordPress plugin that adds a contact form, an AutoCAD or Revit add-in that adds drawing commands.
In Claude, a Plugin is a package that bundles several parts together: Skills (work procedures), Connectors (access to apps through MCP), slash commands, sub-agents and sometimes Hooks, scripts that run automatically at set points in a session.
Plugins work mainly in Cowork and Claude Code. Some parts (Skills, commands and Connectors) are also available in regular Claude chat. Availability depends on your plan and your organization's settings.
02Think of a ready-packed toolbox
A field technician does not gather a screwdriver, a drill, a laser meter and an inspection sheet one by one every morning. He grabs one box already packed for the job: an anchoring box, a surveying box. A Plugin is that box for Claude: the procedure (Skill), the keys to your apps (Connectors) and the quick commands arrive together, ready to use.
03What is inside a Plugin
Skills
Work procedures Claude loads when a task matches, such as the layout of a site inspection report. See the Skills guide (Procedures for AI).
Connectors (MCP)
Access to an outside service: Google Drive, Gmail, calendar, a CRM. See the Connectors guide (Claude meets your tools).
Commands
Named actions you trigger by typing, such as /plugin-name:command. Like a keyboard shortcut.
Sub-agents
Specialists Claude can hand part of a task to, such as an agent that checks a report before it goes out.
Hooks
Scripts that run automatically at fixed points in a session. Very powerful, so they require trust in the source.
04How it works: from catalog to command
- 1MarketplaceA catalog of Plugins: Anthropic's official one, a community one or your company's private one
- 2Pick and installChoose a Plugin, read what it contains and click install
- 3Set up ConnectorsIf it includes a Connector, sign in to that service once with your own account
- 4Use itType a command or simply describe the task, and Claude loads the matching Skill
05Where Plugins come from
Anthropic's official marketplace
The catalog you see by default. Plugins in Anthropic's directory get automated validation and a security scan before they are listed.
Role-based Plugins
Anthropic published Plugins for knowledge work, including productivity, sales, finance, legal, marketing, data, customer-support and product-management.
Your company's marketplace
A Git repository (for example on GitHub) that your company maintains. That is how a team shares internal Plugins without publishing them.
Plugins from your organization
On Team and Enterprise plans an Owner can install a Plugin for every member, or even make it required.
File or folder
You can upload a Plugin you received as a zip file. Only from a source you trust.
06Example: an engineering office Plugin
07Example: a Plugin for CAD conversion
08Example: one quote template for the whole team
09Which Plugin fits which role
| Role | Recommended Plugin type | What it gives you |
|---|---|---|
| Engineer | Internal office Plugin (reports, calculations, standards) | Inspection reports, a calculation checklist and consistent document formats |
| Project manager | productivity or product-management | Task and calendar management, meeting summaries and stakeholder updates |
| Office manager | Team Plugin for quotes and letters | Shared templates, an up-to-date price list and links to Drive and email |
| Developer | Claude Code Plugins from the official marketplace | Commands for code review, commits and GitHub work |
| Marketing | marketing | Content drafts, campaign planning and brand voice |
| Sales | sales | Prospect research, call prep and outreach drafts |
| Finance | finance | Account reconciliation, variance analysis and financial statements |
10How to start in 5 minutes
- 1
Open the Plugins page
In Claude (web or desktop app) go to Customize, then Plugins. The catalog is there.
- 2
Pick one Plugin
Start with something close to your work, such as productivity. Read what it contains before installing.
- 3
Install and connect
Click install. If it includes a Connector, sign in to that service from the Plugin's Connectors tab.
- 4
Try a real task
Type / to see its commands, or just describe the task and Claude will load the matching Skill.
- 5
In Claude Code
Type /plugin in the terminal and pick a Plugin from the Discover tab.
- 6
Not helpful? Turn it off
Any Plugin can be disabled or removed. A few useful Plugins beat ten you never touch.
11Skill, Connector or Plugin?
A single Skill or Connector
- Skill: one work procedure ("how to write the report")
- Connector: access to one service ("a key to Drive")
- Good when you need one specific thing
- You set up each one separately
Plugin
- A package bundling several Skills, Connectors, commands and agents
- One install gives you a complete workflow
- Easy to share with the whole team and update from one place
- Good when you want everyone working the same way
12FAQ
Is a Plugin software installed on my computer?
Mostly not. Most of a Plugin is instructions and connections saved to your Claude account. But in Cowork and Claude Code some parts, such as Hooks and agents, can run commands on your computer.
Is it safe?
A Plugin can run code with your permissions. Install only from a trusted marketplace: Anthropic's official one or your organization's. Before installing, check which Connectors and permissions it asks for.
Does it cost money?
Plugins in Anthropic's directory are available on paid plans (Pro, Max, Team, Enterprise). An outside service that a Connector reaches may need its own account or subscription.
Can we make our own Plugin?
Yes. The Plugins page has an option to create one, including building it together with Claude. On Team and Enterprise plans you can share it with specific people or publish it to the whole organization.
Why not install lots of Plugins?
Every active Plugin adds descriptions Claude has to keep in mind in every session. That takes up context space and usage, and too many can confuse it. Keep active only what you really use.