In partnership with
You have prompts you type again and again.
The way you like your emails drafted. The format you want meeting notes in. The exact brief that turns rough thoughts into a post.
Every time, you paste the whole thing from scratch. Or worse, you try to remember it and it comes out a little different each time.
There's a fix, and it's one of Claude's best-kept secrets. It's called a Skill.
Now a word from today's sponsor:
The GTM Playbook HubSpot Had to Acquire
Warmly ran pipeline, outreach, and lead scoring on autopilot for hundreds of startups — before a single sales hire.
HubSpot acquired them for it. Now the cofounders are walking you through the exact system, live, before they disappear into product. Join the Builder Session on August 12.
Leave with an agentic GTM stack you can replicate this week. Plus HubSpot Credits when you join HubSpot for Startups.
Okay, what a Skill is.
A Skill is a task you teach Claude once, so it can do it the same way every time, on command.
Think of it as a saved recipe. Instead of re-explaining how you want something done, you just call the Skill and it runs.
Your inbox-triage prompt. Your post-writer. Your meeting-notes formatter. Each becomes a one-click move instead of a wall of text you paste every time.
How to build one, in plain steps.
First, find a prompt you use over and over. That repetition is the signal. It's your best first Skill.
Then create the Skill and give it three things:
A name. What you'll call it, plain and obvious.
The instructions. Exactly how you want the task done, every time. Your standards, your format, your voice. Be specific. This is the part you were retyping.
When to use it. A line describing the trigger, so Claude knows when this Skill applies.
Here's a template you can adapt for your first one:
I want to save this as a reusable Skill.
Name it: [short, clear name, e.g. "Meeting Notes Formatter"].
What it does: whenever I give you [the input, e.g. raw meeting notes], produce [the exact output I want, in the exact format].
The rules, every time:
- [your standard 1, e.g. a five-line summary first]
- [your standard 2, e.g. action items with an owner each]
- [your standard 3, e.g. a short follow-up email in my plain, warm tone]
Keep it consistent. Same shape, every time I use it.Once it's saved, you stop pasting. You just call the Skill and hand it the raw material.
Two things worth knowing.
Skills live in Claude on paid plans, and you can build a small library of them, one for each task you repeat.
And they stack with everything else. A Skill plus a connector plus a schedule is how a repeated chore turns into something that runs without you.
Here's the shift. Every prompt you save as a Skill is a task you never have to explain again. Do this a handful of times and Claude changes. It stops being a chatbot you re-brief daily. It becomes a set of buttons that do your recurring work.
Building your own library of Skills is one of the most useful things I teach in Claude Mastery. It's how your repeated work starts running on rails.
Step by step, no tech background needed.
Quick one.
What's the prompt you retype the most? That's your first Skill. Hit reply and tell me.
Talk soon,
Zephyr
