Before this: Set Up Claude
Skill
Save a Prompt as a Skill
Take one prompt you already rewrite every time and turn it into a saved skill you call by name.
Loading progress…

Overview
Turn a prompt that worked into something you can reuse by name, instead of hunting for it in an old chat.
When to use this
The second time you write the same prompt. Once is a one off, twice is a pattern worth saving.
Who it is for: Anyone who has caught themselves scrolling back through old chats to find the prompt that worked last time.
Before you begin
- One prompt that has already worked well for you, ideally used two or three times
- Ten minutes and a real example of its output
What you will learn
- A weekly report you write the same way every time
- A review you run against the same criteria
- A brief you fill in with different details each time
- A voice or formatting rule you keep repeating
Step by step
- 1Find a prompt you have written more than once and paste the best version you have.
- 2Separate the parts that never change from the parts you fill in each time.
- 3Replace the changing parts with clearly named placeholders in square brackets.
- 4Write one sentence at the top saying when this skill should be used.
- 5Add a short example of good output, so the shape is obvious rather than described.
- 6State what it must never do, and what to do when information is missing.
- 7Save it, give it a short name you will actually remember, and note where you saved it.
- 8Run it once on a real job, and fix whatever you find rather than assuming it is finished.
SKILL TEMPLATE
Name: [short, memorable, how you will ask for it]
Use this when: [one sentence. If you cannot write this, stop here.]
What I need from you before starting: [list exactly what you must be given. Say to ask for anything missing rather than inventing it.]
The job: [the instructions that never change, written as you would explain them to a capable new person on their first week.]
How it should come back: [structure, length, tone. Name the format.]
Never: [the mistakes you have already had to correct. This section is the one that earns its place over time, so add to it whenever you correct the output.]
Example of good output: [paste a real one. A shown example beats a described one every time.]
Do Not Make Too Many
A skill earns its place by being used. Three skills you run weekly are worth more than fifteen you built once.
Before building one, ask whether you have done this task at least twice by hand. If not, do it by hand again. The second time teaches you what the skill has to hold, and the first version of a skill written before you have done the job is always wrong.
Once a quarter, look at what you have. Delete anything you have not run since you made it. A skill you do not use is not neutral, it sits in the list making it harder to find the ones that work.
Checkpoint
You have done this when one prompt you used to rewrite every time now runs by name.
Check Your Understanding
Progress is saved when signed in.
Example output
Example only
Worked example, a weekly numbers summary Name: Weekly numbers Use this when: I paste raw weekly figures and want the short written summary that goes out to the team on Monday. What I need from you before starting: The figures for the week, and the same week last month for comparison. If either is missing, ask me for it. Do not estimate and do not use a number I have not given you. The job: Write a summary of what changed and why it might have changed. Lead with the number that moved most. Say plainly when you do not know the cause rather than offering a plausible one. How it should come back: Under 200 words. One short paragraph per figure. No bullet points, no headings, no opening restatement of what I asked for. Never: Never describe a change as significant without the figure beside it. Never round in a way that flatters the result. Never end with a summary of the summary. Example of good output: Signups came in at 312, up from 268 four weeks ago, and almost all of the difference came in the two days after the workshop. Revenue held flat at 18,400 despite the extra signups, which suggests the new arrivals are landing on the free tier and staying there for now. Churn moved from 3.1 to 3.4 percent, a small enough shift that I would not read anything into it yet.
Quality check
- Check every fact, figure, and quote against a real source.
- Review the finished work before using or sharing it.
- Remove confidential information that is not needed.
Privacy and safety
Do not include customer records, contracts, credentials, employee information, or confidential material without approval. A qualified person should review decisions involving people, money, health, or legal obligations.
Worth knowing
A skill is a prompt with the variable parts pulled out and a name attached. If you cannot say in one sentence when to reach for it, it is not a skill yet, it is a prompt you happened to like.
Where this goes wrong
Building a skill for a job you have only done once. Do it by hand twice first, or the skill holds your guesses rather than your method.
Next lesson
01
Your First Routine
Build one low-stakes routine in Claude Code so the mechanics are familiar before you automate anything important.
