Claude Code Plugins: Packaging and Distribution

I've spent two whole chapters on Skills and MCP servers, one on building a capability yourself and one on connecting a capability somebody else already built and packaged as a separate server. So where does a Plugin fit? Short answer: it's the packaging layer. A Plugin is something you find and install. A Skill is something you build. An MCP server is something you connect.

What a Plugin is, next to a Skill and an MCP server

Nobody in the course ever gives Plugins one neat, one-line definition the way Skills and MCP got. I saw it through examples instead. An already-installed plugin, claude-mem@thedotmack, a memory tool, sits at the top of a Manage Plugins screen, with more plugins to browse and install right below it.

Once I lined all three up side by side, the difference held up cleanly: a Skill is something you build yourself and it lives inside your own project, while an MCP server is a separate program someone else built that Claude calls the way it calls its own built-in tools. A Plugin is different again. It's a packaged, ready-to-install unit, handed out through a marketplace made for exactly that job, and it can hold a Skill, a set of instructions, or other Claude Code features inside it. You install it with one command. No hand-copying files, no writing config yourself.

FIGURE 40 — Skill, MCP, or Plugin? Three different answers to the same question: who built this capability, and how does it reach your session?

The one plugin I actually opened, Frontend Design, turns out to be built by Anthropic itself, not some random community entry. Its own page credits two Anthropic authors by name. It builds "distinctive, production-grade frontend interfaces": bold visual choices, distinctive type and color, big animations, and code that fits the specific context it's used in rather than falling back on generic, cookie-cutter patterns. The listed examples range from a music-streaming dashboard to a landing page for an AI security startup. That Anthropic authorship tells you about this one plugin, not about plugins as a whole. Plenty come from the community too. The same directory that lists Frontend Design draws a clear line between what Anthropic built and what the community submitted.

Finding and installing one

My own path went from one plugin's screen, to the directory that lists many, to a site that lists several such directories. That's the same widening search I already used once before to track down an MCP server, just aimed at a different kind of thing this time. Same habit, new target.

The official claude-plugins-official GitHub repository is the main example. Its README draws a clean line: /plugins holds plugins Anthropic itself builds and maintains. /external_plugins holds third-party plugins from partners and the wider community. Installing one takes two commands: add the marketplace, then install the plugin by name. The narration never told me this, but the README states it plainly: install only from plugin makers you actually trust. Why? Because a plugin's Skills, hooks, and other pieces can fire automatically once it's installed. I already gave you this same warning about third-party MCP servers. It applies here for the same reason: code that runs on its own, without you watching every step, deserves the same caution regardless of how it reached your machine in the first place.

Beyond that one official directory sits a wider site called "Claude Code Marketplaces," which lists several plugin collections side by side, some from Anthropic and most from the community, searchable and filterable by category. Treat a plugin marketplace the way I already told you to treat MCP-server discovery. It's a search habit. Not a fixed list you memorize once. And the same trust check applies no matter which marketplace a plugin came from.

Try this with AI "I want to extend Claude Code with [describe a capability you want]. Help me figure out whether that already exists as a Plugin, an MCP server, or something I'd need to build myself as a Skill, and if it's a Plugin, help me check who actually built and maintains it before I install it."