claude plugins, explained.

elisabeth hitz · june 18, 2026 · 6 min read

if a skill is one playbook, a plugin is the whole binder. it is the next packaging layer up, and it is the one that turns the way you work into something a teammate can install in a click instead of learning over six months.

i wrote about skill files on their own in claude skills, explained. this is what happens when you bundle several of them around a single job.

what a plugin actually bundles

a plugin is a packaged set of skills built around a job, plus the connectors those skills need and any subagents they call. a subagent is just a purpose-built helper a skill spins up to handle one part of the work in its own context: a research helper for the research step, a drafting helper for the drafting step.

so the layers stack like this. a skill is one repeatable instruction. a connector is live access to a tool. a plugin is the bundle that carries both, built around a real workflow. install it and the expertise travels with the install, not the person who wrote it.

the two shapes a plugin takes

both are common, both are useful.

shape one, an end-to-end process. when the work has sequential steps, you bundle a skill for each step so the whole thing runs as one. a monthly-close plugin might hold separate skills for pulling the actuals, building the variance table, and drafting the board memo. one install, the entire process, done your way.

shape two, a team's most-used skills. for a set of recurring jobs that are not dependent on each other, you bundle the ones you reach for most. a finance plugin might hold variance analysis, financial modeling, investment-memo drafting, and quarterly reports. a new teammate installs one thing and has the whole toolkit.

the test in either case: a plugin is a package built around a workflow. "renewal prep for customer success" is a plugin. "the monthly board cycle" is a plugin. "the way we scope and pitch a project" is a plugin.

install, customize, or build

anthropic publishes plugins for the common roles, finance, legal, sales, marketing, support, product. you install one off the shelf from the customize menu, approve the connectors it uses, and the skills are available immediately.

but an off-the-shelf plugin is a strong default, not a final answer. the skills inside use a generic version of the workflow, and your team has its own templates and definitions. you shape it by handing claude your real examples: "here are our last three red-lined ndas, update the triage skill so the format and tone match these." claude adapts the plugin in place. the more of your actual work it sees, the more leverage it produces.

and if nothing fits, you build your own by working with claude. most teams start small: one skill for the most repetitive task, then another, and by three or four skills plus the connectors that matter, it is a plugin worth sharing.

why this matters for a small team

the quiet problem in every small business is that the best version of a process lives in one person's head. when they are out, the work gets worse. when they leave, it walks out the door. a plugin is the fix that is finally practical: the process becomes an install, so the quality does not depend on who is at the desk that day.

it is the same legible, owned-files idea from the start of this series, scaled up. the instructions are still plain files you can open and read, claude still drafts while a human approves, and now the whole workflow ships as one unit. if you are still deciding which process to package first, that is exactly what the setup guide walks through.