The short answer
Today's request stays in the prompt: facts, files, goal. How the work should be done belongs in a Skill: the steps, output format, worked examples and checks. Prompts get shorter, and results stop wandering from run to run.
Skills and prompts compared
A prompt belongs to one chat and holds the details of this job. A Skill sits in a folder and holds the method, which means each run, and anyone on your team, starts from an identical base.
The method
- Shared by every run and teammate
- Versioned like any other folder
- Can ship scripts, templates and samples
- Loads only when the task needs it
This run
- Typed once, for one job
- Stays in one conversation
- Carries your facts and attachments
- Lost once the chat closes
Three everyday outputs show where each part goes:
| Output | Goes in the prompt | Goes in the Skill |
|---|---|---|
| Slides | “Ten-slide launch deck for our notes app” | Story structure, word cap per slide, final checks |
| Web page | Your text, logo and prices | Layout rules, section order, a phone-width check |
| Video | Script and running time | Scene lengths, the look of captions, export settings |
The paste test: does this prompt need to become a Skill?
Most prompts are fine as they are. If one of these points rings true, though, the prompt has quietly become a method, and a method deserves its own folder.
Turn it into a Skill when…
- You have pasted the same instructions three times or more.
- A teammate has asked you to send over “your prompt”.
- The prompt stays the same, yet the results change from run to run.
- It only works with a template or a script sitting beside it.
Turning a prompt into a Skill, step by step
- 1
Cut the prompt in two. Whatever you would repeat next time becomes the Skill; the facts of this one job stay out.
- 2
Save the repeatable part as
SKILL.mdin a folder named after the Skill.release-deck/SKILL.md --- name: release-deck description: Turns a product brief into a ten-slide release deck. Use it when someone wants slides that announce a launch. --- 1. Get the product, the audience and three supporting facts. 2. One idea per slide, 25 words at most. 3. Check each figure against the brief. - 3
Drop the folder where your agent looks for Skills, then call it by name and add today's details.
You can skip the blank page. Codex ships $skill-creator, which writes a draft for you, and Cursor offers /create-skill for the same job. The Claude Code docs recommend keeping SKILL.md below 500 lines, with longer material in separate files.
Common questions
Isn't a Skill just a prompt saved to a file?
Not quite. A Skill also carries a description that tells the agent when it is worth loading, and its folder can hold scripts and reference files as well. Claude Code still honours command files in .claude/commands/; if a Skill shares a name with one, the Skill wins.
Will I still write prompts once I use Skills?
Yes. Each run's goal and facts still come from the prompt. The Skill only supplies the method.
Sources
Did this guide help?
