claudekit / guides / types-explained
[ Guide · Concept · 5 min ]

Skill vs Plugin vs MCP — how they differ

published · updated

A concept guide that explains what Skills, MCPs, and Plugins each are and how they differ. Helps you decide which type to start with when picking your first tools.

There are three main ways to extend Claude Code — Skill, MCP, and Plugin. The names sound similar but the roles differ, and they nest into each other, so a quick map helps. This guide explains what each one is and how they relate.

Skill — teach Claude one task

A Skill is a small markdown file that tells Claude “in this kind of situation, do it this way.”

For example, a file at ~/.claude/skills/explain-code/SKILL.md makes the directory name become a slash command — /explain-code (a frontmatter name overrides it). You can run /explain-code directly, or Claude will apply it automatically when a question like “how does this code work?” comes up.

Examples:

  • Bundled skills such as /simplify, /debug, and /loop ship with Claude Code
  • Turn your repeated tasks (code explanation, meeting notes, commit messages) into Skills so you don’t have to repeat the same instructions

Good to know:

  • Custom commands have been merged into skills. A file at .claude/commands/deploy.md and a skill at .claude/skills/deploy/SKILL.md both create /deploy, and existing command files keep working
  • You control who invokes a skill: disable-model-invocation: true limits it to manual /name runs, and user-invocable: false hides it from the / menu so only Claude invokes it

Remember: Skill = “a file that defines one task” + “usually, that file becomes a slash command”.

MCP — a bridge from Claude to external services

If a Skill extends what Claude does, MCP extends what Claude can reach. It’s a standard protocol that lets Claude talk to external services like Notion, Slack, or GitHub directly to read and write data.

Examples:

  • Connect the Notion MCP and “find yesterday’s meeting notes” is handled in your Notion workspace
  • Connect the Slack MCP and “summarize yesterday’s activity in #engineering” works straight from Claude

You add MCP servers with claude mcp add. Many require OAuth.

Remember: MCP = “a bridge between Claude and an external service”.

Plugin — a distribution unit that bundles multiple extensions

A single Skill or a single MCP is small. A Plugin is a directory of components that Claude Code installs and loads as one unit. One box can contain:

  • Multiple Skills (slash commands)
  • Hooks (commands Claude Code runs at points in its lifecycle)
  • Agents (subagent definitions Claude can delegate to)
  • MCP servers (tool servers Claude Code connects to while the plugin is enabled)
  • Other components such as LSP servers, executables, default settings, themes and output styles, and monitors

Plugins are distributed through marketplaces — catalogs that list plugins and where to fetch each one. One install activates everything inside at once, and you can update or remove the whole bundle with one command, which makes Plugins a good fit for sharing a setup across a team or community. A plugin’s skills are namespaced as /<plugin>:<skill> (for example, /commit-commands:commit).

Examples:

  • Superpowers — a methodology bundle for brainstorming, TDD, debugging, and code review
  • Commit Commands — automation for commit, push, and PR creation
  • Slack Plugin — the Slack MCP server + commands such as channel digests and announcement drafts + skills for developing Slack apps

Remember: Plugin = “a box that holds several kinds of extensions, distributed via a marketplace”.

Do you need a plugin?

Skills, subagents, hooks, and MCP servers all work on their own, without a plugin. A skill you save in ~/.claude/skills/, for example, is available in every project on your machine. Use a plugin when you want several of them packaged as one unit: to install a setup someone else built with one command, or to give your own setup to teammates and publish versioned releases.

How the three relate

The three aren’t separate islands — they nest:

Plugin
 ├── Skill 1  (slash command)
 ├── Skill 2  (slash command)
 ├── Hooks
 ├── Agents
 └── MCP config (external service connection)
  • Skill — the smallest unit, one slash command; can stand alone or live inside a Plugin
  • MCP — connects Claude to outside services; can stand alone or live inside a Plugin
  • Plugin — the unit that boxes all of the above for distribution and install

Official docs: Skills, MCP, Plugins overview

§ 5

Frequently Asked Questions

frequently asked
§ 5.1
What is a Skill?
A small file that teaches Claude how to do one thing. You can call it as a slash command (e.g. `/explain-code`), or Claude may apply it automatically when the situation fits.
§ 5.2
What is MCP?
A bridge that connects Claude to external services like Slack, Notion, or GitHub. Once connected, Claude can read from and write to those services directly inside the chat.
§ 5.3
What is a Plugin?
A directory of skills, agents, hooks, MCP servers, or other components that Claude Code installs and loads as one unit. Most plugins come from a marketplace.
§ 5.4
How are Skills and Plugins different?
A Skill is a single file for one task. A Plugin packages several skills, subagents, hooks, or MCP servers as one unit; a skill you save in `~/.claude/skills/` already works in every project without a plugin.
§ 5.5
Where should I start?
Install a popular plugin like Superpowers from the marketplace — that's the fastest way to feel the value. Add an MCP when you need data from an external service, and write your own Skill when you want to standardize one of your repeated tasks.