Claude plugins vs skills
A skill teaches Claude one task. A plugin is a package that can hold several skills plus agents, hooks and MCP servers.
A skill is a folder with a SKILL.md file that tells Claude how to do one kind of task. A plugin is a package that can hold skills and other parts, such as subagents, hooks and MCP servers, installed as one unit.
You do not need a plugin to use a skill. Skills, subagents, hooks and MCP servers all work on their own. A plugin is for when you want several of them together, or want to share them with a team. The one thing to know first: an enabled plugin loads in every session, so it adds to your context even when you do not use it. For the skill format itself, see what agent skills are.
Good for
- Claude Code users deciding whether to install a plugin or write a skill
- Teams that want to hand the same setup to everyone
- Developers packaging their own Claude setup
- Claude and Cowork users who see both words in the app
Side by side
Our advice: start with a single skill for one routine. Reach for a plugin when you want several parts installed together or shared with a team.
| Option | Plugin | Skill |
|---|---|---|
| What it is | A package of components | One SKILL.md folder |
| Can hold | Skills, agents, hooks, MCP servers | Instructions, supporting files and optional hooks |
| Works without the other | Yes | Yes |
| How you get it | Install from a marketplace | Save to a skills folder |
| Share with a team | Marketplace, versioned releases | Commit the folder to the repo |
| Context cost | Name and description of each skill on every turn, plus running servers | Description only until used |
Which to pick
Our advice: write or install a skill for one routine, such as a review checklist. Install a plugin for a ready-made bundle or a shared team setup, and enable only what you use. See also [MCP vs skills](/compare/mcp-vs-skills).
The limit on each side: a plugin adds context and running processes to every session where it is enabled, and a skill covers one routine, so it does not replace a package of several parts.
Best for
- Skill: one routine you repeat, such as a report format or release checklist
- Skill: something you want in one project by committing it to the repo
- Plugin: a setup someone else built, installed with one command
- Plugin: giving teammates the same skills, agents and MCP servers
- Plugin: publishing versioned releases through a marketplace
Skip it if
- Plugin: you only need one skill, since a plugin adds its parts to every session
- Skill: you also need subagents or an MCP server in the same package
Questions
What is the difference between a plugin and a skill?
A skill is one SKILL.md folder that tells Claude how to do a task. A plugin is a directory that packages skills with other components such as agents, hooks and MCP servers.
Do I need a plugin to use skills?
No. Anthropic says skills, subagents, hooks and MCP servers all work on their own, without a plugin. A skill saved in your skills folder works in every project on your machine.
Can a plugin contain skills?
Yes. Skills are one of the components a plugin can hold, next to agents, hooks and MCP servers. Skills from a plugin run with the plugin name in front, as /plugin-name:skill-name.
When should I make a plugin instead of a skill?
Make a plugin when you want to give your setup to teammates, install it in many projects, or publish versioned releases. For a single routine in one project, a skill is enough.
Do plugins slow Claude down or use more of my limit?
They can. An enabled plugin is part of every session, and the name and description of each skill, agent and command Claude can invoke sit in context on every turn. You can disable a plugin without uninstalling it.
Are plugins safe to install?
Review them first. Anthropic says a plugin you install can run code with your user privileges, whichever marketplace it comes from. Install plugins you trust and read what is in them.
Do plugins work in Cowork and claude.ai?
Plugins do, with a different set of components loading there. Anthropic says the same plugin format installs on claude.ai and in Cowork, and a Cowork plugin bundles skills, connectors and sub-agents. See Claude Cowork for skills and plugins there.
Do ChatGPT and Codex have plugins and skills too?
Yes. OpenAI says plugins bundle capabilities into reusable workflows in ChatGPT and Codex, and they can include skills and MCP servers.
How is a plugin different from an MCP server?
An MCP server is one connection to a tool or service. A plugin can include MCP servers along with skills and other parts. See what MCP is, MCP tools and MCP vs skills.
Sources
Docs, issue trackers and discussions this page is built from.
Show all 4Hide
- Plugins overview · code.claude.com
- Extend Claude with skills · code.claude.com
- Get started with Claude Cowork · support.claude.com
- Plugins · learn.chatgpt.com