Claude Code Plugins vs Skills: the box, and what's in the box.

Ryan “RyMac” McKinney · USMC · 26 August 2026 · 4 minute read

Plugins and skills get said in the same breath, and if you're an agency owner trying to make Claude Code useful, the 2 words sound like 1 more decision you didn't ask for. It isn't. A skill is a folder of instructions. A plugin is the box the folder can arrive in. One of them belongs at the start of your setup, and it's not the one with the marketplace.

The short answer

A skill is a folder of instructions for 1 job. A plugin is the box that carries skills, plus other helpers and connections, in 1 install. Anthropic's own docs call plugins the packaging layer. The skill does the work. The plugin is how somebody hands it to you.

What a skill is, one more time

Instructions for 1 job, written in a text file, sitting in a folder. When the job comes up, the folder gets opened. You can write one yourself in plain language, no code, the way you'd write for a new hire.

A skill lives in your own folder next to the map file. Nothing has to be installed for it to work. That part matters, because it means skills are yours the way your documents are yours.

What a plugin adds

A plugin bundles things. 1 install can carry several skills, plus pieces you may hear called hooks, subagents and MCP servers. Those words mean extra helpers and outside connections, the parts with technical names that a developer would configure.

The bundle is the point. When somebody has built a pack of 12 things that work together, a plugin hands you all 12 in 1 line instead of 12 copy jobs.

You may also hear about the plugin marketplace. It means the shelf where those boxes are listed, and anybody can put a box on the shelf. Which is exactly why the next section exists.

The question under the question

Nobody typing this search actually cares about packaging. The real question is: what do I install to make this thing useful?

Here's the honest answer. For a business owner, the order is filing first, skills second, plugins last.

2 text files and a small set of folders do more for your results than anything you can install, because the thing making your AI useless isn't a missing tool. It's that nothing tells it what your business is. A 6 person digital agency with clean filing and 3 skills will outrun a solo operator with 40 plugins, every day of the week.

When a plugin is the right call

When somebody you already trust packed one. If a person whose work you know ships their pack as a plugin, taking the box beats rebuilding the contents by hand.

Treat it like a new hire on day 1, though. A plugin arrives with instructions your AI will follow, so read what came in the box before you let it near client work. The advantage of it all being text is that you can. My own pack ships as plain folders on GitHub for exactly that reason: you can read every line before you copy it in.

And if the choice ever feels heavy, go watch the simple explanation of the folder system and notice how little is actually required. A desk. A map. A filing cabinet. The boxes are optional.