Back to Resources

Claude Skills and Plugins, Explained in Plain English

Tom CassidyJuly 17, 2026
Claude CodeAI Basics
Modular blocks docking into a central spine, representing Claude skills and plugins composing onto a core
On this page

A Claude skill is a set of written instructions that teaches Claude how to do a specific job your way — like an SOP you'd hand a new employee. A plugin is the binder: a bundle of skills, commands, and tool connections you install once so Claude shows up already trained for your business.

If you've ever explained the same task to an AI chat window for the fourth time, this is the fix. Here's what each piece is, what it does for a business, and what to watch out for.

What is a Claude skill?

A Claude skill is a document that teaches Claude how to do one job to your standard — your steps, your rules, your tone. Think of the SOP or checklist you'd hand a new hire: "here's how we chase overdue invoices, here's the tone, here's when to escalate." Write that once as a skill, and Claude follows it every time without being re-told.

Concrete example: a skill that writes your invoice-chase emails the way you would — friendly on day 7, firm on day 30, and it never threatens a customer you flagged as a keeper. You wrote the rules once. Now the routine runs itself.

The point isn't the technology. It's that the fourth, fortieth, and four-hundredth time the task comes up, the work is already trained.

What is a plugin?

A plugin is the binder that holds it all: a package of related skills, ready-made commands, and connections to outside tools, installed in one step. If a skill is one SOP, a plugin is the full operations manual for one area of your business — plus the keys to the filing cabinets it needs.

Open the binder and you'll find three compartments:

Skillsthe SOPs Claude follows automatically when the work calls for them.
Commandsshortcuts you invoke on purpose, like /seo-audit, that kick off a defined job.
Tool connectionsthe wiring (called MCP servers) that lets Claude pull live data from real tools instead of guessing.

[VISUAL: "Anatomy of a plugin" diagram — one binder-shaped box with three labeled compartments: Skills (SOPs), Commands (shortcuts), Tool connections (MCP). Simple, brand palette.]

Skills vs. plugins vs. MCP servers — what's the difference?

Skills are the instructions, MCP servers are the tool access, and plugins are the package that bundles both. Here's the clean version:

SkillPluginMCP server
What it isWritten instructions for one jobA bundle: skills + commands + connectionsA connector to one real tool (CRM, calendar, data source)
Plain-English versionAn SOPThe binder of SOPs, plus the keysThe standard plug into a filing cabinet
What it gives ClaudeKnow-howEverything for one area, in one installLive data and the ability to act in that tool
How you get itWritten, or installed inside a pluginInstalled once from a marketplaceUsually comes wired into a plugin

If you want the full story on that third column, it gets its own explainer: What is an MCP server?

What can a business actually do with them?

A plugin turns Claude from a general assistant into a specialist that already knows your playbook. Real examples from our own marketplace:

  • SEO audits on live data. The seo-aeo-geo plugin runs site crawls, keyword research, and AI-visibility checks using current search data — not a chatbot's memory of the internet. One command, a real report.
  • A second brain that answers back. The obsidian-second-brain plugin connects Claude to your notes, so "what did we decide about that client in March?" gets answered from your own records.
  • Projects that start planned. The project-launcher plugin takes a rough idea and turns it into a researched, stress-tested spec before anything gets built.
  • Consistent client work. Skills that carry your brand voice, your onboarding steps, your delivery checklists — so the output sounds like you on the intern's laptop too.

The pattern across all of them: hours back on work you were doing by hand, and a standard that holds when you're not looking.

Go deeper: Rhize plugins for Claude Code — the complete guide — Jim walks through all six plugins in the marketplace, what each one does, and how they fit together.

Are they safe to install?

Mostly yes — but treat a skill like what it is: a stranger's instructions that your AI will follow. You wouldn't hand a new contractor the keys and an unread set of orders from someone you've never met. Same logic here. A badly written skill wastes time; a malicious one could tell your AI to do things you'd never approve.

The fix isn't fear — it's a vetting step. Install from sources you trust, read what a skill actually does before it runs, and quarantine anything third-party until it's been checked. We built tooling for exactly this: Skill Forge scans and quarantines outside skills before they're promoted into use.

Go deeper: Skill Forge: a security gate for agent skills — how the quarantine-scan-promote pipeline works.

Go deeper: The rhize-meta plugin — the governance layer that vets external skills and sharpens internal ones.

Where do you get them?

From plugin marketplaces — public catalogs you connect to Claude Code, then install from with a single command. Rhize runs one: six free plugins covering SEO, note systems, project planning, engineering standards, team ops, and skill safety.

Installing takes about a minute. You add the marketplace once — /plugin marketplace add https://github.com/Rhize-Media/rhize-plugins — then install whichever plugins you want, individually. They work in both Claude Code and Cowork, and everything in ours is free. If you're not sure what Claude Code is in the first place, start here.

Frequently Asked Questions

Are Claude skills free?
Many are, including everything in the Rhize marketplace. Skills are just written instructions, so anyone can create and share them — some are free, some are sold, and the best one for your business is often the one you write yourself from your own SOPs. You pay for your Claude subscription either way; skills ride on top of it.
Do skills work in the Claude app, or just Claude Code?
Skills work across Claude's products — the pattern is the same set of written instructions wherever Claude runs. Plugins with tool connections are built for Claude Code and Cowork, where Claude can actually reach files and outside tools. Check what each product currently supports at install time; the details shift as the products evolve.
Can Claude write its own skills?
Yes — and it's the fastest way to build one. Describe the job, walk Claude through how you do it, and have it draft the skill; then you review and correct it like you'd review a new hire's first attempt at your SOP. The skill is only as good as the process you feed it, which is why written-down processes beat tribal knowledge here.
What happens if two skills conflict?
Claude picks the skill that best matches the task at hand, and more specific instructions generally beat vague ones. Genuine conflicts usually mean two skills claim the same job — the fix is to tighten each skill's description so it's clear which one owns what. Same as two employees with overlapping job descriptions: clarify the roles and the collisions stop.

Ready to see what a trained-up Claude looks like? Browse the Rhize plugin marketplace — six free plugins, install in a minute, keep whatever's useful. And if you'd rather talk through what to install for your business first, book the 15-minute call. No pitch — you leave with a plan.

Want this working in your business — not just on paper?

Book a 30-min call and we'll map exactly where your business depends on you, and what to fix first. No pitch — you leave with a plan either way.

Book a 30-min call

Get insights like this in your inbox

Join our newsletter for actionable SEO, marketing, and growth strategies — no fluff, just results.

No spam. Unsubscribe anytime.

See exactly where your business
runs through you.

The next step is a 30-minute call.

Book a 30-minute call and we'll map where the business depends on you — and what it looks like once a system you own runs the routine. You leave with a plan, whether you hire us or not.

No pitch — you leave with a plan. We'll tell you exactly what we'd do, whether you hire us or not.