Claude Skills vs Plugins vs MCP
Three words get mixed together because they arrived at the same time. They operate at different layers:
- Skill — the instructions for doing a job
- Plugin — a package that can ship skills, commands, agents, hooks and MCP configuration together
- MCP — the connection to an external system
Think of a plugin as the box, a skill as the manual inside, and MCP as the power cable.
The layer map
| Layer | Question it answers | Example |
|---|---|---|
| Plugin | How is this distributed and installed? | A team plugin that adds three commands, two skills and a review agent |
| Skill | How should this job be done? | "Build an OG image at 1200×630 with our type scale" |
| MCP | Where does the data come from? | A server that reads your CMS |
Why the distinction matters
If you only need a repeatable output, a Skill is enough and it's portable across Claude Code, Codex, Cursor, Gemini CLI and Copilot. Packaging it as a plugin limits it to one ecosystem.
If you need slash commands, hooks or bundled MCP servers, a plugin is the right container.
Decision table
| You want… | Build |
|---|---|
| The same deck style every week | Skill |
| One-command install for a team | Plugin that contains skills |
| Read/write to Jira | MCP server (+ a Skill for how to use it) |
| A workflow that spans both | Plugin: Skill + MCP config |
| Use it in four different agents | Skill in .agents/skills |
What's actually inside a plugin
Depending on the ecosystem, a plugin can bundle:
- skills (including
SKILL.md) - slash commands
- subagents
- hooks
- MCP server definitions
That's why "plugin vs skill" is a category error: the plugin may contain skills.
Migration advice
Start with a Skill. If you find yourself adding three commands and a hook around it, promote it to a plugin. Don't start with the packaging.
FAQ
Can I use a plugin's skill without the plugin? Usually yes, if it's a plain folder — copy it into your skills directory. Check the license.
Do plugins cost more tokens? They can, if they inject commands and context. Skills only load their metadata until activated.
Which is more future-proof? The SKILL.md folder. It's a file format, not a platform.