A prompt is a request you type for one result. A Claude skill is a saved set of instructions that Claude loads when a task calls for it, an MCP server connects Claude to an outside service or its data, and a plugin is a package that installs skills, MCP servers and other parts together.
The four are layers that work together, so the useful question is which layer your task is missing. This guide defines each one from the documentation of the companies that make them, checked on 18 November 2026, and then shows all four at work in one real product.
What each one is
Prompt. A prompt is the text you type or paste into a conversation. It works once, in that conversation, and you supply the facts each time. A saved prompt is still a prompt: you fetch it and paste it yourself.
Skill. A skill is a folder with a SKILL.md file that holds a name, a description and instructions. It can also hold scripts, reference documents and templates. Claude sees only the name and the description until a task matches, and then it reads the full instructions. You can also call a skill by name, with /skill-name in Claude Code. The format is an open standard, so the same folder works in Codex and Antigravity CLI.
MCP server. MCP stands for Model Context Protocol, an open standard for connecting AI applications to outside systems. An MCP server gives the AI tools it can call and data it can read, such as your calendar, a database or an issue tracker. The server handles the connection and the sign-in. In the Claude apps an MCP server is called a connector.
Plugin. A plugin is a package. Anthropic's documentation describes it as a way to add skills, MCP connectors, commands and agents to Claude as one unit. In Claude Code a plugin can also carry hooks, which are commands that run at set moments, such as after each file edit. A plugin adds no new kind of ability. It delivers the other kinds, with one install and with updates from the place you got it.
Comparison table
| Prompt | Skill | MCP server | Plugin | |
|---|---|---|---|---|
| What it is | Text you type | A folder with SKILL.md |
A program or service that speaks MCP | A package with a manifest |
| What it gives the AI | One request | A method: steps, rules, references | Access: tools and data from another system | Whatever it contains |
| When it loads | When you send it | Name and description always, the rest on demand | Its tools are available while it is connected | When the plugin is enabled |
| What you install | Nothing | A folder, or a ZIP file in the Claude apps | A connection, usually with a sign-in | One install from a marketplace |
| Can it run code on your computer | No | Yes, if it includes scripts | Yes, if the server runs locally | Yes, through hooks, scripts and local servers |
| Works outside Claude | Yes | Yes, in tools that follow the Agent Skills standard | Yes, in tools that support MCP | The format is Claude's own; other tools have their own plugins |
| Use it when | The task is occasional | You repeat the same procedure | The AI needs something it cannot see or do | You want several parts at once, or want to share a setup |
When to use which
Anthropic's documentation for Claude Code ties each one to a moment you can recognize. In plain terms:
- You are typing the same request for the third time. Save it as a skill. A skill costs almost nothing until it is used, because only its description stays in the conversation.
- You keep copying information out of another program and pasting it into the chat. Connect that program as an MCP server, so the AI can read it directly.
- The AI can reach a service but uses it badly. Add a skill that explains your way of using it. Anthropic states the division this way: MCP gives Claude the tools, and a skill gives Claude the knowledge of how to use them well.
- A second project, or a second person, needs the same setup. Package it as a plugin.
- The task comes up twice a year. Write a clear prompt and stop there.
Two rules of thumb follow. If the answer to "what is missing?" is knowledge, you need a skill. If the answer is access, you need an MCP server. A plugin is never the answer to that question, because it only decides how the other two reach you.
Prompt vs skill vs workflow covers the earlier choice, between a prompt, a skill and a written process, with a five-question test.
A real run of Prompt Writing Guide
Prompt Writing Guide was run on 18 November 2026 in rit_grade.py and rit.py (the product's own scripts), Python 3.14. The input, the steps and the output are given as they were recorded.
The input
A weak prompt of four lines: "You are a helpful marketing expert. We sell olive oil. Write a great product description that really sells." with one boastful example.
The steps
- Ran rit_grade.py weak-prompt.txt to grade the prompt part by part.
- Wrote a proper brief for the same job and ran rit.py brief.json; it wrote a 248-word prompt and checked it. The check found one fault in the new prompt as well.
The output
Total: 17/100
Role 0/25 names a discipline 0/10, names a level 0/9, no praise adjective 0/6
Input 0/25 states the situation 0/9, names a constraint 0/8, names the gap or supplies material 0/8
Task 0/25 names a deliverable 0/8, sets a length or bound 0/6, sets a register 0/5, says what it is usable for 0/6
Example 17/25 is present 10/10, is an example, not a description 0/8, agrees with the task 7/7Weakest part: Role (0/25).
Highest-value repair: 10 points, Role. Name the discipline with a role noun, for example 'a pricing analyst' or 'a building surveyor'.
…
wrote prompt.txt (248 words)
FAIL score 92/100 errors 1 skipped 0
[ERR ] R04 The input states the situation.
One product, all four layers
Knacco uses each of the four, which makes it a convenient example of where the lines fall.
- The skill. The free Prompt Writing Guide is a skill folder named
kit-prompt-writing-system. ItsSKILL.mddescribes when to use it, and the folder holds a guide, references and two local tools. It adds a method to your AI tool. - The MCP server. Knacco runs a server at
https://knacco.com/api/v1/agent/mcp, listed in the Official MCP Registry ascom.knacco/knacco. Once you sign in, a connected tool can list the products you own, search them, read a product's guide and get a download link that lasts 30 seconds. It cannot buy anything. It adds access to your library. - The plugin. The Knacco plugin for Claude Code is a small package: a manifest, and one file that holds the address of that MCP server. It contains no skills. It exists so that Claude Code users can add the connection with one install and receive updates.
- The prompt. After all of that, you still type a request: "Search my Knacco library for a workflow for product photos."
The same division holds for any product. The skill is the knowledge, the MCP server is the door, the plugin is the box they arrive in and the prompt is what you ask for.
The Knacco plugin page gives the connection steps for each AI tool, and the AI tools help page lists the tools that are supported.
How each one is installed
- Prompt. Nothing to install.
- Skill. Copy the folder into your tool's skills folder, or upload a ZIP file in the Claude apps. How to install Claude skills has every path and command.
- MCP server. In the Claude apps, open Customize > Connectors, choose a service and sign in. In Claude Code, run
claude mcp add --transport httpfollowed by a name and the server's address. - Plugin. In the Claude apps, open Customize > Plugins. In Claude Code, run
/pluginand choose one from the Discover tab.
Where to find Claude skills lists the sources for skills and plugins and the checks to make before you install one.
What each one costs you
None of the four needs a payment by its nature, but each has a cost in attention or risk.
- Room in the conversation. Every installed skill adds its name and description to each conversation, and a plugin adds the same for every skill and agent inside it. Anthropic's documentation notes that an enabled plugin is part of every session, including the sessions where you never use it.
- Things that run. A skill's scripts, a plugin's hooks and a locally run MCP server all run as you, with your files within reach. Read them first.
- Accounts. An MCP server reaches a service with the account you connect. That service may need its own subscription.
- Upkeep. A prompt never breaks. A skill is a text file and rarely breaks. A plugin or an MCP server depends on software that changes, so it needs updates.
Start with the smallest layer that solves the problem. Knacco's free skills, prompt packs and workflows are a way to try a skill on a real task at no cost, and the full skills category shows what each one requires.
Mistakes that come from mixing them up
- Installing a plugin to get one skill. If the skill is all you need, copy its folder. A plugin may bring hooks and servers you did not ask for.
- Expecting a skill to reach a service. A skill can describe how to use your calendar. It cannot open the calendar without a connector.
- Expecting an MCP server to know your process. A connected database does not tell the AI which tables matter. That knowledge belongs in a skill.
- Calling everything a plugin. Ask what is inside the package. The answer is always some mix of the other parts.
- Rewriting a prompt that should be a skill. If you paste the same background every time, the background belongs in a skill.
Before you choose
- You can say in one sentence what is missing: knowledge, access or packaging.
- You have checked what the thing runs on your computer.
- You know which accounts it will use.
- You have chosen the smallest layer that covers the gap.
Common questions
What is the difference between a Claude skill and a plugin?
A skill is one folder of instructions that Claude loads when a task calls for it. A plugin is a package that can install several skills together with MCP servers, commands, agents and hooks. A skill adds a method. A plugin is a way of delivering skills and other parts in one install.
What is the difference between a Claude skill and an MCP server?
A skill gives Claude knowledge: written steps, rules and reference material for a task. An MCP server gives Claude access: tools it can call and data it can read in another system, such as a calendar or a database. Many tasks need both, an MCP server to reach the service and a skill to explain how you use it.
Do I need a plugin to use a Claude skill?
No. A skill works on its own. Copy its folder into the skills folder of Claude Code, or upload it as a ZIP file in the Claude apps. A plugin is useful when you want several skills, connections and settings installed together, or when you want to share one setup with other people.
Are Claude connectors the same as MCP servers?
In practice, yes. Connector is the name the Claude apps use for a connection to an outside service, and Anthropic's documentation for building a connector is its guide to building an MCP server. In Claude Code the same kind of connection is called an MCP server and is added with the claude mcp add command.
What is the difference between a Claude skill and a project?
A project holds background knowledge that is always loaded in the chats inside that project. A skill holds a procedure that Claude loads only when a task calls for it, and it works across your conversations. Use a project for the facts about one piece of work, and a skill for a method you repeat.
Is a slash command the same as a skill in Claude Code?
In Claude Code, custom commands have been merged into skills. A file in the commands folder and a skill folder with SKILL.md both create a command that you call with a slash, and existing command files keep working. A skill can also hold supporting files, such as scripts and reference documents.
Sources and further reading (11)
- Claude Code documentation: Extend Claude Code
- Claude Code documentation: Extend Claude with skills
- Claude Code documentation: Plugins overview
- Claude Code documentation: Connect Claude Code to tools via MCP
- Claude documentation: Skills overview
- Claude documentation: Plugins
- Claude documentation: Get started with connectors
- Model Context Protocol: What is the Model Context Protocol (MCP)?
- Agent Skills specification
- Knacco Prompt Writing Guide: requirements and contents
- Knacco plugin for Claude Code: public repository


