Claude plugins save you the setup work, not the judgment calls

A plugin bundles skills, connectors, and workflows for one job

A Claude skill is written instructions for one task, like drafting a collections email in your tone. A connector is a login: OAuth access to a tool you already run, like QuickBooks or Gmail.

A plugin is the package that ties both together with ready-made commands on top, so instead of building a skill, wiring a connector, and writing a workflow one piece at a time, you install one thing and it all shows up at once.

The clearest example is the Claude for Small Business plugin, which Anthropic shipped on May 13, 2026. It bundles 15 skills (cash-flow snapshots, invoice chasing, margin analysis, lead triage, contract review, and more) and 15 ready-to-run workflow commands, things like /plan-payroll, /close-month, and /monday-brief.

Its core 3 connections are QuickBooks, PayPal, and HubSpot, with Canva, DocuSign, Google Workspace, Microsoft 365, Slack, Stripe, and Square as optional add-ons.

Type a plain request like "can I make payroll" and a router picks the right workflow for you.

You never have to see the underlying skill or connector configuration unless you go looking for it.

Installing one takes a few clicks, not a developer

On Claude's desktop app, plugins live in the Customize menu in the left sidebar. Open the Plugins tab, click "Browse plugins," and click "Install" on the one you want. That is the entire action for the plugin itself.

The setup after install is where the work actually happens, and it still is not code. Each connector asks you to sign in through that tool's own OAuth screen, the same "Allow access" prompt you would see connecting any app to your Google account.

The small-business plugin adds a short onboarding command that walks you through connecting the core 3 tools, running one demo task, and telling Claude the basics of your business in plain language.

Slash commands from a plugin can also open as a short form instead of a blank prompt, so running something like /close-month feels like filling out a brief, not writing a paragraph of instructions.

Compare that with building the equivalent by hand: 15 skills plus 7 connectors, even at a brisk 20 min each to write and wire up, is 22 x 20 min = 440 min, about 7.3 hrs of setup. The plugin turns that into one install and a handful of OAuth approvals.

What's actually out there to install, as of mid-2026

Anthropic's plugin push has come in 3 waves so far. Verify against the sources below before you act, since this moves fast.

For a solo owner, the small-business plugin is the one actually built for you. The department-specific waves (legal, sales, marketing, finance, HR, engineering, design, operations) are aimed at bigger companies, though nothing stops you from installing one if a single skill inside fits your business better than what is in the small-business bundle.

What it costs: usually nothing extra, if you already pay for Claude

Plugins carry no separate price of their own. They are included with every paid plan: Pro ($17/mo billed annually, $20 monthly), Max ($100 or $200/mo), and Team ($20/seat standard, $100/seat premium, annual billing, 5-150 seats).

Anthropic's own launch post and coverage in The Register both confirm the small-business plugin is free to add on Pro, Max, and Team, no plugin fee on top of your subscription.

What is not free: the tools on the other end of a connector. QuickBooks, HubSpot, PayPal, and Canva keep billing you exactly as they do today. A plugin does not replace those subscriptions. It reads and writes to them once you connect them.

One nuance worth flagging, since it is about your data rather than your money. Anthropic's launch post says it does not train its models on data from Team and Enterprise plan customers.

The small-business plugin is marketed to Pro and Max users as well, and their standard consumer privacy policy allows chat data to be used to improve future models unless you turn that setting off.

If you run this plugin on Pro or Max and real business numbers pass through it, check your privacy settings before you connect anything, not after.

Where a plugin still needs you

• Generic workflows need your real numbers first. The /plan-payroll workflow runs a cash forecast, but it forecasts off whatever books it can read. Feed it a QuickBooks file that is 2 months stale and it hands back a confident, wrong number. A plugin's workflows are a shape, not an answer, until you connect current data and tell it your actual policies: your refund window, your payment terms, your tone. See what Claude actually does for a small business owner for the grounding argument in full.
• A marketplace means variable quality. Anthropic's own plugins are curated in-house. Its community marketplace only runs automated validation and safety screening on third-party submissions, not a full manual review of what the code does. Anthropic says this directly in its own documentation: it does not control the MCP servers, files, or other software a plugin includes and cannot verify that a plugin works as intended, or that it will keep working that way after an update.
• Permissions are the decision that matters, not the click. A plugin runs with your access. Approve one that reaches your email and your payment processor, and you have handed a standing grant to both, bounded only by whatever your OAuth approval allows. Widen scopes on purpose, not by default, and take read-only access wherever a connector offers it.
• Customer-facing and money-moving steps still need a human. The small-business plugin's own documentation states plainly that it does not give financial, tax, legal, or HR advice, and its workflows are built so you approve every step that touches money or a customer. Keep that approval step. It is the difference between a plugin drafting an overdue-invoice email and a plugin sending one with the wrong amount, a case our guide to AI on customer comms, safely covers in more detail.

A vetting checklist before you install a third-party plugin

Anthropic's own plugins, small business, legal, sales, finance, marketing, and the rest, carry the most scrutiny, since Anthropic wrote and curated them itself. Anything from the community marketplace or an outside repository needs a few minutes of checking first.

• Read what it will install before you click. The plugin detail screen lists every skill, connector, and command it adds. Read the list. If a marketing plugin wants access to your email and your bank connector, ask why.
• Check who built it and how recently it was updated. A plugin with no listed author, no homepage, and a stale update date is a plugin nobody is maintaining, which means nobody is patching it either.
• Start with read-only connector scopes. Most connectors offer a narrower grant than full access. Take the narrow one first and widen it only after watching the plugin behave for a few days.
• Keep human approval on anything touching money or customers. True even for Anthropic's own plugins. It matters more for a third-party one you cannot fully vet.
• Uninstall what you do not use. Every installed plugin is a standing grant of access. If you tried it once and moved on, remove it.

Bottom line: a plugin buys you the setup, not the judgment. It is a fast, usually free way to get skills, connectors, and workflows in place instead of building them one at a time, and the small-business bundle is a genuinely useful starting kit for an owner-operator.

What it cannot do is know your numbers, your policies, or your risk tolerance. That part is the same job it always was: write down your rules, connect your live data, and keep a human on the approve button.

See choosing AI tools for a small business for how to decide what is worth adding at all.