Skills: the game-changing concept
Skills are the concept that changes everything: the difference between explaining to Claude how to work every single time and having Claude already trained to work your way. In this lesson you'll see what a skill is, why it beats a long prompt, and how to trigger one.
What you'll get: a clear picture of what a skill is and why it beats any long prompt, the two ways to trigger one and where skills come from — plus a real invocation example ready to adapt.
What a skill is
A skill is a small text file (SKILL.md) that teaches Claude one job really well — like a recipe card, or an instruction manual. When you have it installed and invoke it, Claude follows that manual to the letter — so the result comes out just as good every time, without you writing a huge prompt. And when your task matches what the skill knows how to do, Claude pulls in the recipe automatically.
Think of it like leveling up a character: base Claude is good in general; each skill makes it a specialist in something concrete (reviewing contracts, writing in your voice, generating thumbnails, auditing accessibility).
Skill vs. long prompt
Without a skill, every time you want a LinkedIn post in your style you have to explain the whole style again. With a "LinkedIn post" skill, you just type /linkedin-post and give the topic — the skill already holds all your rules.
The before and after, in short:
Every time, from scratch
- You explain the whole process and format every time
- Results vary wildly
- You forget best-practice steps
- 300-word prompts
One command, one proven workflow
- One command runs a proven workflow, already saved
- Consistent, high-quality output
- Expert steps built in
- A short command
How to trigger a skill
Two ways:
By command
Type / and the list of installed skills appears. Pick the one you want (e.g. /blog-post or /grill-me) and give your instruction. It's the most precise way.
In natural language
Name it in your request — "Use the grill-me skill to..." — or simply ask "write me a blog post about X" and Claude recognizes it should use the blog skill. When the task matches, Claude pulls the skill in on its own.
A real example
Here's what invoking the LinkedIn skill from the example looks like on a concrete task — the command plus your instruction, in one line. Swap the brackets for your own details:
/linkedin-post Topic: how [your company] helps [your audience, e.g. freelance designers] save hours every week with AI. Include one concrete example from my week: [what happened]. End with a question that invites comments.
Notice what you did not have to write: the tone, the format, the length, the style rules. All of that already lives inside the skill.
Where skills come from
Official
Ready to install, covering common tasks (documents, presentations, and complete suites by profession).
From the community
Developers publish skills on GitHub. Useful, but you decide whether they're safe (we cover this in the APIs & MCP module).
Your own
You can build a skill from scratch. Claude ships with a skill-creator — just tell it "create a skill for [your task]" and it interviews you to build it.
The most important rule
Make each skill do ONE thing well. Don't try for a super-skill that does everything. A focused skill (review NDAs, write newsletters, generate thumbnails) gives better results than one that tries to cover it all. Once you have several, you combine them — but each one, a specialist.
Next lesson: how to install skills and keep them organized.
10-minute practice. Pick one task you repeat every week and jot down what makes the result good (format, tone, steps that can't be skipped). Then open Claude and type / to see your installed skills: if one matches your task, invoke it with a short instruction in the style of the example above. If none matches, tell Claude "create a skill for [your task]" and let the skill-creator interview you with your notes at hand.