Home › Blog › Public or Private Claude Plugins: How a Small Company Decides

Public or Private Claude Plugins: How a Small Company Decides

Short answer

The Claude plugin marketplace is the public shelf of ready-made plugins your staff can browse, and for a company under fifteen it is somewhere to evaluate options, not a standard to adopt. Strategized.ai helps a rollout lead decide which plugins become company standard and when a private or custom one earns its place.

Key facts: public, private and custom plugins
Question Answer
Public A listed plugin is built for a general need. I treat it as an option to evaluate against a job you repeat, never as a standard until someone owns it.
Private A private library is the short list of plugins your company has chosen, each with a written job and one accountable person.
Custom A custom Claude plugin is built around your own work, standards and review steps. Configuration is included, code is scoped separately.
What it never does No plugin replaces a named owner or a review step. I never treat one as a record of past work or as something Claude remembers between sessions.

If you lead a Claude rollout at a company under fifteen people, your staff have probably installed plugins on their own initiative. Nobody owns the question of whether any of them is good enough to standardise on, or whether the company needs its own. For the mechanics behind this choice, Anthropic’s marketplaces and how a private company marketplace works on Team and Enterprise, see the Claude plugin marketplace explained.

I am Michael Robichaud, and Claude is the tool this work runs on. In the first week of an engagement I list what your staff have installed, write down the job each plugin serves and tell you which gap is real. You own the resulting standard afterward.

What a Public Listing Gives a Company Under Fifteen

A listed plugin is built for a general need. That makes it a sensible starting point when a job is common and the description fits closely, but one person installing it does not make it a company standard. Nothing about a listing tells you whether it suits the way your business works.

Business owner and a colleague comparing printed pages at a desk while weighing a listed plugin against their own work
Start from the job your team repeats, then judge the listing against it.

I compare a listing’s stated purpose with a job your team actually repeats, then decide whether to adopt it, adapt the workflow around it or build something that reflects your own standards. In the rollouts I run, that comparison needs an owner and a written job, not a feature checklist.

Where the Claude Plugin Marketplace Stops and Your Own Library Starts

The line sits where a plugin starts carrying your company’s own standards and someone inside the company owns it. Until then it is a public option. After that it is a private library: the short list your company has chosen, each plugin with a written job and one accountable person. I define a private library by ownership, because it is a company decision first and a product feature second.

A private library earns its place when these conditions hold:

  • The same recurring job comes back differently from different staff.
  • Your business has language, standards or review steps that a general plugin cannot reflect.
  • Staff have installed separate plugins and you need to decide which are suitable to standardise on.
  • Someone can own the decision, gather feedback and revisit the list as the work changes.
Hub diagram of a private Claude plugin library for a small company: the chosen plugins, a named owner, a written job for each and a review step
What I keep in a private plugin library for a small company.

Strategized.ai builds the private option when those conditions hold. I scope it on a call, my developers handle anything that needs code, and configuration is included while code is scoped separately. The page on custom plugin development shows what that engagement covers, and I weigh the decision itself in my breakdown of custom versus marketplace plugins.

Public, Private and Custom Compared for a Company Under Fifteen

These three answer different questions. A public listing answers whether something ready-made exists, a private library answers what this company has decided to use, and a custom plugin answers what this company needs that no listing reflects.

Public, private and custom plugins for a company under fifteen
Question Public listing Private library Custom plugin
What it is A general plugin built for a common need The short list of plugins your company has chosen A plugin built around your own work, standards and review steps
Best when The job is common and a listing describes it closely Staff use several plugins and nobody has decided which is standard Your standard is specific enough that no listing reflects it
Who owns it Nobody until you name someone One named person inside the company One named person inside the company, with my developers available for anything that needs code
First thing I check Whether its stated purpose matches a job you repeat Whether every plugin in it still has a job and an owner Whether the job is written down well enough to build from
What it never does Fit your standards by default Run itself without an owner Replace the judgment of the person reviewing the result
Decision diagram for a small company: if a listed Claude plugin fits a repeated job, evaluate it for the team; if not, scope a private or custom plugin
The first question I ask about any listed plugin.

The three are not exclusive. A company can run a listed plugin for a common job, keep a short private library and hold one custom plugin for the work that defines the business.

The Skills Inside the Plugin

A plugin is a bundle, and the skills inside it are where your company’s own way of working lives. A skill tells Claude how the business handles one kind of job: the task, the terms you use, the finished standard and the points where a person decides. I describe what each skill does for the people using it and leave how it is assembled to my developers.

Skills are meant to be shared, not rebuilt by each person. Anthropic’s pricing page lists organization wide skills deployment among its Team plan features, which is why I write a skill once, with an owner, instead of letting several people keep several versions.

Three colleagues around a laptop and printed plans agreeing what the skills in a plugin should handle
A skill is only as good as the written job behind it.

I start from the Foundation Plugin. It interviews you about the business and writes a Business Blueprint, so every Claude conversation begins with the same standing context and every later plugin reads it first. The Foundation Plugin page shows what it contains, and my Claude plugin pages cover the rest of the range.

To see what a skill for your own work looks like, this prompt turns a repeated weekly job into a written spec from the notes you already keep.

Prompt: draft a custom Claude plugin skill from weekly work

Read the files in this folder that document how [one repeated weekly job] gets done. Using only what they show, write a one-page spec for a Claude skill that handles it: what the job produces, who receives it, the terms the company uses, what a finished result contains, and the points where a person must decide. Mark anything the files do not support as NEEDS INPUT instead of guessing. Do not invent clients, figures or tools.

What comes back is a one-page spec with gaps flagged, not filled. Check each section against the files it came from, and treat every NEEDS INPUT line as a question for the person who owns the job.

Prompt: test a custom Claude plugin standard on finished work

Read the standards document in this folder and the finished piece of work named [finished deliverable]. List every point where the work follows the standard, every point where it departs from it and every point the standard does not cover. Quote the exact lines you are comparing. Do not rewrite the work and do not guess at intent.

What comes back is a three-part comparison with quotations. The owner reads the departures first, because a departure is either a mistake in the work or a gap in the standard, and only a person can say which.

Who Owns the Decision in a Company This Size

The owner or the rollout lead should own it, even when staff bring the options. Ownership means deciding which job matters, whether an existing plugin is suitable and who reviews the choice when the work changes. Anthropic’s help article on the Team plan describes access and billing managed in a centralized place; I keep that administration separate from the question of which plugins the company stands behind.

Flow diagram of how a company goes from the plugins staff installed to a standard: list them, name each job, pick one owner, keep or retire, write the standard
How I move a company from what staff installed to one standard.

When staff have already installed plugins, I do not start by removing anything. I ask each person what they installed and what job it serves, then decide with the lead which to keep, replace or retire. I lay out that sequence in Claude Team Rollout: Plugins First, Training Second.

How I build a first library is in how I build a private plugin library, and the wider question of building versus buying across teams is in my longer guide to plugins for teams, so I will not repeat either here.

Starter standard for one company plugin

PLUGIN: [name of the plugin, in the company's own words]
OWNER: [one named person]. Every change is reviewed by the owner before it replaces this text.

THE JOB IT SERVES
[One sentence on what the job produces and who receives it.]

WHAT A FINISHED RESULT CONTAINS
[The parts every complete piece of this work has before it is sent.]

TERMS THE COMPANY USES
[Preferred words, words to avoid, formatting habits.]

WHERE A PERSON DECIDES
[Decisions that stay with a person and are never handed to Claude.]

WHEN INFORMATION IS MISSING
Say what is missing and ask. Do not guess.

Keep it short enough that a new hire could read it in a minute, and keep a plain copy outside Claude so the text survives any change of seat or workspace.

Key takeaways

  • Treat a public listing as an option to evaluate, not a standard to adopt.
  • Define a private library by ownership: chosen plugins, a written job for each, one accountable person.
  • Scope a custom plugin only when no listing reflects your standard.
  • Start from what staff already installed, and decide one plugin at a time.

Watch for

A listing is a description, not a guarantee that the plugin suits your business. Keep company standards and customer details out of anything public, and confirm the job and the owner before staff rely on a plugin.

What to Do Next

Company owner talking through a custom Claude plugin decision with two colleagues beside a notebook
One accountable owner makes the call, and the team knows who it is.

If you lead a Claude rollout and want to know which plugins your company should stand behind, the next step is a conversation. Book a strategy conversation with me at Strategized.ai, and I will list what your staff have installed, name the job each one serves and show you where a private or custom plugin would earn its place. I have developers on staff for anything custom; configuration is included and code is scoped separately.

If you are not ready to talk, the CoworkScore.com assessment is a quieter first step. If you run a smaller operation on your own, book a short call with CoworkConsultant instead.

If the answer is private, the private plugin library at Strategized.ai is the conversation to have.

Frequently Asked Questions

Does a company under fifteen need a private plugin marketplace?

Usually not at first. Strategized.ai starts with an inventory of what your staff already use, and I recommend a private library only once public plugins keep missing your company’s standard.

Which Claude plugins for business should a small team standardise on first?

The one that serves your most repeated job and has a named owner. Strategized.ai begins with the job, not the listing, so I choose the plugin after the job is written down.

What should I do with the Claude plugins my staff already installed?

List them before deciding anything. Strategized.ai makes the keep, replace or retire call with the rollout lead one plugin at a time, so nothing staff rely on is switched off by surprise.

Should a custom Claude plugin ever go on the public marketplace?

No, not in my practice. Strategized.ai keeps a custom plugin in the client’s own library, because it carries the company’s standards and terms, which are not for the public.

Can a small team run a private plugin marketplace without its own developers?

Yes. Strategized.ai has developers on staff, so your team does not need its own; configuration is included, and any code is scoped separately and quoted on its own.

Where does the Claude plugin marketplace end and a private plugin library begin?

At the point a plugin carries your company’s own standards and someone inside the company owns it. Strategized.ai draws the line there, whatever a public listing happens to offer.

Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai, a Claude consultancy for owner-led businesses. Michael leads every Claude rollout himself, designs the custom Claude plugins his developers build, and runs his own five-site publishing network on Claude.

 ·  Connect on LinkedIn →

About the Author

Michael Robichaud

Founder of Strategized.ai. 30 years across enterprise sales, digital marketing, and building businesses. Practitioner-first AI strategy consulting — done-for-you workspace builds, GEO/AEO, and fractional advisory.

Free: the Claude Foundation Plugin

A 20-minute Guided Intake. Claude learns your business once and remembers it in every chat. No account, no card.

The Strategy Stack

Strategized.ai is the strategy layer. Where to go next.

Keep Exploring

More from the blog

Strategy, GEO/AEO, consulting perspectives.

Browse the Blog →

Prefer to learn it yourself?

Free written guides, from first day to confident.

Read the free guides →

Claude plugins by profession

Ready-made Claude plugins for your role, $99 each. Or start free with the Foundation plugin.

Browse the Claude plugins →