prompts vs skills vs plugins vs mcps.
four words get thrown around like they mean the same thing: prompt, skill, plugin, mcp. they do not. and the difference is not trivia. it is the difference between collecting AI tricks and building a system that runs your work. here is the whole framework in plain english, with a table you can keep.
the fastest way to hold it: three of these are about how the AI does the work, getting more packaged as you go (prompt, then skill, then plugin). the fourth, mcp, is about access, how the AI reaches your real tools and data. instructions on one side, wiring on the other.
the comparison, at a glance
| what it is | lifespan | what it gives the AI | when to use it | |
|---|---|---|---|---|
| prompt | a single instruction you type in the moment | one-off, disposable | direction for this one answer | thinking, exploring, a task you do once |
| skill | a folder of instructions (plus optional examples, assets, scripts) the AI loads on its own | build once, reused automatically | a repeatable method, done your way | a task you redo and want the same quality every time |
| plugin | a bundle of several skills plus the connectors and subagents they need | installed, shareable | a whole workflow as one package | a multi-step job you want to run, or hand to a team |
| mcp | the open standard that connects the AI to external tools and data | a live connection | access to your real apps and data | any time the AI needs to read or act in your actual tools |
prompt: the instruction
a prompt is one instruction you type and retype. powerful, but it lives in your clipboard and resets every time you open a new chat. it is the rawest unit, and it is where everyone starts. a prompt is not a skill goes deeper on why the next step up matters.
skill: the reusable instruction
a skill is a folder the AI loads automatically when a task matches it. inside: a SKILL.md instruction file, and optionally reference examples, brand assets, and small scripts for the parts that must run the same way every time. you build it once and it keeps working, so quality stops depending on how well you phrased the prompt that day. more in claude skills, explained.
plugin: the bundle
a plugin packages several skills, plus the connectors and subagents they depend on, around one job. a monthly-close plugin might hold a skill for pulling the actuals, one for the variance table, one for the board memo. install it and you get the whole process the way your team does it. more in claude plugins, explained.
mcp: the access layer
mcp, the model context protocol, is the odd one out, and the one people conflate the most. it is not an instruction. it is the open standard that lets the AI plug into your real tools and data, often described as usb-c for AI: one consistent connection, and any tool that speaks it works. connectors run on mcp. it is how the AI reads your stripe, your notion, your inbox, instead of guessing. more in connect claude to your tools.
the mental model that makes it click
skills and plugins are the playbook: how the work should be done. mcp and connectors are the wiring: what the work can reach. a brilliant playbook with no wiring still guesses, because it cannot see your real data. great wiring with no playbook has access but no method. a system that actually runs your work needs both, and that is the whole point: good instructions plus real access beat a clever prompt every time.
the ladder for a small business
you do not adopt all four on day one. you climb:
- start with a prompt for whatever is in front of you.
- the prompt you keep retyping becomes a skill.
- a few skills that serve one workflow become a plugin.
- wire mcp connectors so any of it can touch your real data.
that is the path from typing instructions into a box to owning a system that does the work. if you would rather have that path mapped and built for your business, that is what the diagnostic is for.
want this built into your business?
the systems diagnostic is $500, the price is on the page. you get a map of which prompts to promote into skills, which to bundle, and which tools to wire in, with the plan to build it. you decide on your own schedule.
get the $500 diagnostic