If you explain your workflow to Claude at the start of every project, you're doing extra work for no reason. There's an open directory of ready-made skills, built by Anthropic and thousands of other people, that you install once and reuse forever. Think of them like little apps you plug in.
Takes 20 minutes. You need: Claude. You end with: the setup you keep re-explaining, saved permanently.
What a skill is (in plain terms)
A skill is a saved capability. Instead of pasting the same long instructions every time, you install the skill once and Claude just knows how to do that thing.
The everyday version: you have a way you like your client emails written — the structure, the sign-off, what you never say. Right now you explain that every time, or paste an example and hope. A skill is that explanation, saved, applied automatically whenever the job comes up.
Step 1. Open the directory
There's a single command to browse and install skills. You'll find it and the current list on the official skills page.
Step 2. Search for what you actually do
Don't install everything. Search for the handful that match your real work: writing, design, research, planning, coding.
Step 3. Install with one command
Pick a skill, run the install command, and it's ready. No copying prompts between chats ever again.
A safe first five to look at
- A writing skill that keeps drafts sounding human, not robotic.
- A design or layout skill so built things stop looking generic.
- A research skill for pulling and organizing information.
- A planning skill for breaking big tasks into steps.
- Whatever matches the one job you do most.
The power move: turn your own SOP into a skill
Installing other people's skills is the easy half. The half that changes your business is packaging your own way of doing something so it happens the same way every time, whether you're the one asking or not.
If you've already narrated a task into an SOP (see the SOP guide), you're most of the way there:
That last clause is where your actual expertise lives. You know a client email is off before you can explain the rule. Getting that into writing once is worth more than any tool you'll install this year.
Start with the task you'd be most annoyed to see done badly. That's the one where your standards are clearest.
What this is worth after six months
The compounding is the point:
Month 1 You install two skills, and save one of
your own - the client email one.
Month 3 Three of yours: emails, proposals, and the
weekly update nobody used to have time for.
Month 6 A new hire uses your skills on day one and
produces work shaped like yours, because
your standards are written down instead of
living in your head.That last line is the actual prize, and it's the same reason the SOP guide exists. Every skill you save is one fewer thing that only works when you're the one doing it.
One honest note
Only install skills from sources you trust, the same way you'd think twice before installing a random app. Stick to official and well-used ones to start.
A skill is instructions your AI follows, which means a careless or badly written one changes how your work comes out — and you might not notice for a while. Read what a skill actually says before you install it, prefer official and widely used ones, and if something feels over-promised, skip it.
When it goes sideways
"It's not using the skill." Usually the description doesn't match how you phrase the request. Make the "when to use this" line sound like the words you'd actually type.
"Two skills are fighting." One says be concise, another says be thorough, and you get an odd middle. Keep the one that matches the job and remove the other — overlapping skills are worse than none.
"The output got worse after I installed things." Take them all off and add back one at a time, a few days apart. Same as any other kind of plugin.
"I installed ten and use one." The tool-collecting instinct again. The one you built yourself will beat the nine you downloaded.
"Setup instructions don't match my app." This area moves fast and the specifics change. If the commands don't line up, check the official page rather than following an older walkthrough — including this one.
Make it yours
- Client service: your email standards first. Highest volume, most recognizably you.
- Studio or shop: the weekly schedule or the four questions you answer constantly.
- Solo: whatever you do worst when tired. A skill doesn't have bad days.
- Small team: whatever you correct most often when reviewing their work. That correction is a standard you've never written down.
Do this next
Install one skill today. Then pick the task you'd hate to see done badly and spend twenty minutes turning it into your own.
How to use this: Set it up once. From then on, you install the exact capability you need instead of re-explaining yourself. That's the difference between using AI and building a system around it.
Next guide: Turn Any Task Into an SOP by Narrating It — the fastest way to get the raw material for a skill of your own.