Claude Skills vs Plugins: Which One Do You Actually Need?
Both words get used as if they meant the same thing, and they do not. A skill is one file that teaches Claude a method. A plugin is a package that can contain skills along with several other things, and it is installed a different way, from a different place, by a different kind of person.
Getting this wrong is what leads people to hunt for a plugin marketplace when what they wanted was a single file they could paste into Claude, or to install a whole plugin when one skill would have done the job.
The short answer
| Skill | Plugin | |
|---|---|---|
| What it is | A SKILL.md file with instructions | A package that can bundle skills, agents, commands, hooks, MCP and LSP servers |
| Where it comes from | A file you download, paste or enable on your account | A marketplace you add, then install from |
| Where it works | Claude on the web, desktop, Cowork, Claude Code, and any tool that reads the format | Claude Code |
| Who it is for | Anyone doing the work | Mostly developers, and teams shipping a whole workflow at once |
| Time to first use | About a minute | Two commands, plus finding a marketplace you trust |
- A plugin can contain skills. A skill cannot contain a plugin.
- If you are not in Claude Code, the plugin question does not apply to you at all.
- One repeated task is a skill. A whole workflow you want to hand to a team is a plugin.
What a plugin actually bundles
A plugin is a container. That is the whole idea, and it is why the word feels vague: what is inside varies completely from one plugin to the next. According to Anthropic's own documentation, a plugin can carry any of the following:
Read that list again and the distinction becomes obvious. A skill is one of the things a plugin can contain. Asking whether to use a skill or a plugin is a bit like asking whether to use a document or a folder.
What a Claude Code plugin marketplace is
A marketplace here is not a shop. Nothing is bought and there is no checkout. It is a catalogue file that tells Claude Code where a set of plugins lives, and in practice it is a git repository containing a single manifest at a fixed path:
You point Claude Code at one, then install from it. Two commands, in this order:
- Add the marketplace:
/plugin marketplace add owner/repo, or/plugin marketplace add ./my-marketplacefor one on your own disk. - Install from it:
/plugin install plugin-name@marketplace-name.
A marketplace can be hosted on GitHub, on any other git host including GitLab, Bitbucket and self-hosted servers, at a plain HTTPS URL pointing at the manifest, or on a local path. Anthropic also publishes an official, curated directory of its own.
Because anyone can publish one, a marketplace is a distribution channel rather than a quality signal. Adding one means trusting whoever maintains that repository, and plugins can carry hooks and MCP servers that do real things on your machine. Add marketplaces you can identify, the same way you would with any other dependency.
When each one is the right call
The honest rule is about scope, not sophistication.
You repeat one kind of task and want it done consistently: a report in your format, a contract review against your checklist, copy in your house voice. You work in Claude on the web, in the desktop app or in Cowork. You want it running in about a minute, and you want the same file to keep working if you switch tools later.
You are in Claude Code, and the thing you want is not one method but a whole setup: several skills, a couple of subagents, some slash commands, maybe a hook that fires after every edit and an MCP server pointing at your issue tracker. You want to hand that entire setup to teammates as one installable unit and keep it updated from one place.
Most people asking the question are in the first group and do not know it yet, because plugin is the word that shows up in developer conversation and skill is the word that describes what they actually want.
Can you use both?
Yes, and it is common. Skills you enable on your Claude account travel with you across the web app, the desktop app and Cowork. Plugins live in Claude Code and can bring their own skills along. Nothing about installing a plugin removes or replaces the skills you already use, and nothing about using skills stops you adding a plugin later.
If you are unsure where to start, start with a skill. It is the smaller commitment, it works in more places, and if you later decide you want the whole workflow packaged for a team, the skill file you already have is one of the pieces that goes inside the plugin.
Skills and plugins: frequently asked questions
What is the difference between a Claude skill and a Claude Code plugin?
A skill is a single SKILL.md file that teaches Claude how to do one kind of task. A plugin is a package for Claude Code that can bundle skills, agents, slash commands, hooks, MCP servers and LSP servers into one installable unit. A plugin can contain skills; a skill cannot contain a plugin.
What is a Claude Code plugin marketplace?
A catalogue that tells Claude Code where a set of plugins lives. In practice it is a git repository with a manifest file at .claude-plugin/marketplace.json in its root. Nothing is bought there; it is a distribution channel, not a shop.
How do I add a plugin marketplace in Claude Code?
Run /plugin marketplace add owner/repo for one hosted on GitHub, or /plugin marketplace add ./my-marketplace for one on your own disk. Then install a plugin from it with /plugin install plugin-name@marketplace-name.
Where can a plugin marketplace be hosted?
On GitHub, on any other git host including GitLab, Bitbucket and self-hosted servers, at a plain HTTPS URL pointing at the manifest file, or on a local filesystem path. Anthropic also publishes an official curated directory of its own.
Do plugins work outside Claude Code?
No. Plugins are a Claude Code feature. Skills are not: the same skill file works in Claude on the web, in the desktop app, in Cowork, in Claude Code, and in any other tool that reads the Agent Skills format.
Is a plugin safer than a skill?
The opposite, if anything. A skill on its own is plain text, so the worst it can do is give bad instructions. A plugin can carry hooks and MCP servers, which are code that runs and connections that reach outside. That is not a reason to avoid plugins, but it is a reason to know who published one before you add their marketplace.
Should I buy a plugin or a skill?
If you repeat one kind of task and want it handled consistently, buy the skill. If you are in Claude Code and want a whole workflow packaged for a team, with commands and hooks and tool connections, that is what a plugin is for. Most people asking the question want a skill and have only heard the word plugin.
Can a plugin and a skill be used at the same time?
Yes. Skills enabled on your Claude account work across the web app, the desktop app and Cowork. Plugins live in Claude Code and can bring their own skills with them. Neither removes or disables the other.
Start with a skill
We publish skill files, not plugins, because a file is the smaller commitment and it works in more places. If you want the mechanics first, the guide to what a skill is and how to enable one covers the whole thing.
Otherwise: browse the catalogue by role, or take one of the free skills and test the workflow before paying for anything.
KissMySkills is an independent marketplace and is not affiliated with, endorsed by, or connected to Anthropic, OpenAI, or any other AI company. Claude and Claude Code are products of Anthropic.