Claude Skills vs Plugins: What They Actually Are and Which One Your Team Needs

I used to open a new Claude chat and retype AI Operator's brand voice rules from scratch every time: how we format a LinkedIn post, our file structure, the reminder to skip em dashes. Now those rules live in a reusable Skill. That's what Skills and Plugins are built to fix, and most people building with Claude still mix the two up.

They're not the same thing. A skill is a file of instructions. A plugin is a package of capabilities. Anyone can create either one, but they solve different problems, and knowing which one you need saves you from building something that already exists or installing something generic when you needed five minutes of writing.

What a Claude Skill Actually Is

A skill is a folder Claude reads before it starts a task. Inside is a SKILL.md file with instructions, and often templates, reference files, or small scripts alongside it.

Say a company has a specific way of writing LinkedIn posts: first person for personal accounts, "we" only when it's genuinely a team effort, no em dashes, always tied to something happening in the news that week. Instead of typing that out every time, the company writes it once as a Skill. Claude reads it, follows it, and produces the same quality output no matter who prompts it.

How to Create Your Own Skill

You don't need to code. A skill is a folder with a Markdown file in it. Here's the whole process in Claude Code:

Step 1: Create the folder. Where you put it decides who can use it:

• ~/.claude/skills/your-skill-name/ makes it a personal skill, available in all your projects
• .claude/skills/your-skill-name/ inside a project makes it available to everyone working in that project

Step 2: Write the SKILL.md file inside that folder. It has two parts. At the top, between --- markers, a short description that tells Claude when to use the skill. Below that, the actual instructions in plain language. For example:

---
description: Writes LinkedIn posts in our brand voice. Use when asked to draft or review a LinkedIn post.
---

When writing a LinkedIn post:
- First person, conversational, no corporate tone
- No em dashes, use commas or periods
- Tie the post to a real news event from this week
- End with a question, not a sales pitch

Step 3: Use it. The folder name becomes the command, so this one runs when you type /your-skill-name. Claude also invokes it on its own when your request matches the description. Changes you make to an existing skill file apply immediately, no restart needed. The one exception: if you just created your skills folder for the very first time, restart Claude Code once so it knows to watch it.

That's genuinely all of it. You can add templates, example outputs, or scripts to the folder as the skill grows, and reference them from the SKILL.md so Claude knows when to load them.

The Fastest Way to Build a Skill: Just Ask Claude

You don't have to create the folder or write the file by hand. The quickest route is to describe what you want and let Claude build the skill for you inside Claude Code.

Type a request like this:

Create a skill called linkedin-post that writes LinkedIn posts in our voice: first person, conversational, no em dashes, always tied to a real news event from this week, and ending with a question instead of a sales pitch. Save it to my personal skills folder so I can use it in every project.

Claude creates the folder, writes the SKILL.md, fills in a description so the skill triggers at the right moment, and tells you the command to run. You review it, tweak anything you want, and it's live.

Two ways to get a sharper result:

• Ask Claude to interview you first. Add “ask me a few questions before you write it” and the instructions come from your answers instead of its guesses.
• For skills that matter, install Anthropic's skill-creator, a plugin built specifically to help you write, test, and improve skills:

/plugin marketplace add anthropics/claude-plugins-official
/plugin install skill-creator@claude-plugins-official

Then say something like “help me build a skill for summarizing sales calls” or “evaluate my linkedin-post skill.” It walks you through real test cases, runs them, and shows you whether the skill actually improves the output before you rely on it.

What a Claude Plugin Actually Is

A plugin is a package of capabilities you install in one step. Open one up and you'll usually find a bundle of skills, sometimes an MCP server that connects Claude to an outside tool like Slack or Notion, sometimes background automations called hooks, sometimes a specialized subagent for a specific job. One install, and the whole set is available. Your teammate runs the same install and gets an identical setup.

Most plugins you'll use were built by someone else, because the value of a plugin is that the integration work (auth, packaging, updates) is already done. But nothing stops you from building your own and sharing it with your team, and if an installed plugin doesn't do quite what you want, you can fork it and edit your own copy. The tradeoff is that your fork stops receiving the original author's updates.

How to Install a Plugin

The easiest way is visual, no commands needed.

• In the Claude app, open the Customize menu in the left sidebar (in Cowork, open the Cowork tab first). It brings your plugins, skills, and connectors together in one place.
• Open the Plugins tab and click Browse plugins. This opens Anthropic's directory, where there are lots to choose from.
• Click Install on the one you want. Done.
• Prefer a browser? The same catalog lives at claude.com/plugins.

A few from the official directory worth a look:

• github connects Claude to your repositories, issues, and pull requests.
• atlassian wires up Jira and Confluence for issues, docs, and sprints.
• security-guidance reviews your code for security issues as you work.

Prefer the terminal? In Claude Code it's two commands:

Step 1: Add a marketplace. A marketplace is just a GitHub repo that lists plugins. Anthropic runs the official one:

/plugin marketplace add anthropics/claude-plugins-official

Any public GitHub repo set up as a marketplace works the same way with /plugin marketplace add owner/repo.

Step 2: Install the plugin you want:

/plugin install plugin-name@claude-plugins-official

Or skip the commands entirely: type /plugin, open Discover, and browse what's available. Installed plugin skills show up namespaced as plugin-name:skill-name, which means they can never accidentally overwrite a skill you wrote yourself.

Where to Find Good Skills and Plugins

• The official marketplace at github.com/anthropics/claude-plugins-official is Anthropic's curated directory and the safest starting point.
• agentskills.io documents the open Agent Skills standard that skills follow, with guides on writing and evaluating them. Skills built to this standard work across Claude Code and other compatible tools.
• Community marketplaces on GitHub. Many companies publish their skills publicly (Sentry's engineering skills repo is a good example of a well-structured one). Add any of them with /plugin marketplace add owner/repo. One caution: plugins run code on your machine, so stick to repos from teams you trust.

When to Write a Skill vs When to Install a Plugin

Write a Skill when the task involves knowledge only your business has: your onboarding checklist, your reporting format, or the exact way a sales call should be summarized before it goes into your CRM. Nobody has packaged that, because nobody else works the way your business does.

Install a Plugin when Claude needs to reach something outside its native capabilities and someone already built the bridge: web search, database access, Slack, Google Drive, or another external system. Building that yourself means writing an MCP server from scratch, which almost nobody needs to do when a well-maintained option already exists.

Most teams end up using both. Plugins handle the infrastructure. Skills handle the “here's how we specifically do this” layer on top of it.

Four Things Most Explainers Get Wrong

Most explainers make Skills sound either too simple or too technical. The useful truth sits in the middle. These four details are what make Skills practical for real teams.

1. Skills barely cost anything until they're used. Only the skill's name and short description sit in context by default. The full instructions load only when you or Claude invoke the skill. That means you can keep dozens of skills available without quietly eating up the context window.

2. You can control who triggers a skill. Set disable-model-invocation: true in the SKILL.md frontmatter and only you can run it, never Claude on its own. That matters for anything with real consequences, like sending a message or deploying something. You can also use user-invocable: false when a skill should work in the background without showing up as a manual command.

3. Skills can bring in live data before Claude starts. A skill can run a shell command first and place the real output into the prompt. That means it can hand Claude today's numbers, files, or project state instead of forcing Claude to guess or hunt for context after the task starts.

4. Skills stack across different levels. Skills can live at the enterprise, personal, and project level, plus inside plugins. Claude Code has clear priority rules when names overlap: enterprise beats personal, and personal beats project. Plugin skills are namespaced, like plugin-name:skill-name, so installing someone else's plugin won't overwrite your own skill.

Power Moves Worth Knowing

Once a team has written a Skill or two, these options turn it from a saved prompt into a real operating layer for repeatable work.

1. Pass details on the fly. A skill can take input right after the command. Write $ARGUMENTS or $1, $2 for specific values in your instructions, then run something like /fix-issue 123. Claude drops 123 straight into the task.

2. Auto-trigger only for the right files. Add a paths line to the frontmatter and the skill loads automatically only when you're working on matching files. It stays available when needed and stays out of the way the rest of the time.

3. Pre-approve the safe tools. List trusted tools under allowed-tools so Claude can use them without stopping to ask permission every time. This is useful when the skill has a clear, repeatable workflow and the allowed actions are low-risk.

4. Run heavy work separately. Add context: fork and the skill runs in its own isolated space before reporting back. This keeps the main conversation clean, especially for research, reviews, or longer checks.

5. Adjust the model and effort. A skill can override the model or reasoning effort with model and effort. Use more thinking power for careful reviews, and keep quick formatting or cleanup skills lightweight.

6. Keep the main file lean. Put the essentials in SKILL.md, aim for under 500 lines, and move long reference material into separate files in the same folder. Claude loads extra files only when it needs them, so the skill stays fast and focused.

How We Use This at AI Operator

At AI Operator, we build our own Skills in-house rather than relying only on what's available off the shelf, because the value of a Skill is how specific it is to how a team actually operates. One enforces our exact brand voice down to which words are banned. Another checks drafts for AI writing patterns line by line before they go near a client or a LinkedIn post. Each one exists because repeated instructions should become reusable systems.

That's the same approach we walk teams through in the Operationalize phase of the ADOPT Method™, where the goal is to move from scattered AI usage to tools the whole team can run the same way, every time.

FAQ

1. What is a Claude Skill?

A skill is a set of instructions, usually a Markdown file plus supporting templates or scripts, that teaches Claude to handle a specific, repeatable task the way you want it done. You write it in plain language, no coding required.

2. What is a Claude Plugin?

A plugin is a packaged bundle of capabilities installed in one step. It can include one or more skills, MCP servers, hooks, and subagents. Anyone can build one, but most people install plugins others have already published.

3. How do I create a skill?

Create a folder at ~/.claude/skills/your-skill-name/, add a SKILL.md file with a short description and your instructions, and it's live. The folder name becomes the /command.

4. Can I just ask Claude to create the skill for me?

Yes, and it's usually the fastest way. In Claude Code, describe the skill you want and where to save it, and Claude writes the SKILL.md for you. For skills that matter, install the skill-creator plugin to test and refine them before you rely on them.

5. How do I install a plugin?

Add a marketplace with /plugin marketplace add anthropics/claude-plugins-official, then run /plugin install plugin-name@claude-plugins-official. Or browse everything through the /plugin menu.

6. Can I use skills and plugins together?

Yes, and most serious setups do. Plugins handle the external tools and shared infrastructure. Skills handle the workflow logic on top of it, specific to how your team operates.

7. Does having a lot of skills slow Claude down or eat up context?

Not much. By default, only each skill's name and description are kept in context so Claude knows it exists. The full instructions only load when a skill is actually invoked.

The Takeaway

Skills are what you write because nobody else knows your business the way your team does. Plugins are what you install because someone already solved the general problem. Confusing the two either wastes hours building something that already exists, or leaves you stuck re-explaining yourself to Claude every single day.

If you want help figuring out what your team should build versus install, that's exactly what we walk through in AI Operator live sessions and inside the ADOPT Method™.

Explore the ADOPT Method →