Claude Skills: When a Skill Beats a Saved Prompt
5 min read
You have a prompt that works. It lives in a notes file, you paste it at the start of a task, and each time you tweak it slightly and forget which version was best. Skills are Anthropic's answer to that habit: a way to package how you want a repeatable job done so Claude can load it when it is relevant instead of waiting for you to paste it.
This article explains what a skill actually is, the kinds that exist, and how to decide between a skill, a project and a saved prompt. The Complete Beginner's Guide to Claude introduces skills in one line; this is the longer version.
What a skill is
Anthropic describes skills as folders of instructions, scripts and resources that Claude loads to improve its performance on specialized tasks. The instructions are written in Markdown. Scripts are optional, and mostly matter for custom skills that need more advanced functionality.
The part that matters in practice is how Claude uses them. When you give it a task, Claude reviews the skills available, loads the relevant ones and applies their instructions. Anthropic calls the design "progressive disclosure": Claude loads only the information a task needs, which prevents the context window from being crowded with instructions that do not apply. Skills made by Anthropic are invoked automatically when relevant.
That is the difference from a pasted prompt. A pasted prompt is always in the conversation, whether it helps or not. A skill waits until it is needed.
The four kinds you will meet
Ready-made
- Anthropic skills: maintained by Anthropic, such as enhanced document creation for Excel, Word, PowerPoint and PDF
- Partner skills: built by partners such as Notion, Figma and Atlassian to work with their connectors
- Available in the Skills directory
Made for you or your team
- Custom skills: written by you or your organization for specialized workflows
- Organization-provisioned skills: custom skills that Team and Enterprise owners distribute, enabled or disabled by default
- Yours to edit as the work changes
To browse, click "Customize" in your account, go to "Skills," then click "+" and "Browse skills." Skills are available on Free, Pro, Max, Team and Enterprise plans, and they require code execution to be enabled. They also work in Claude Code.
The decision: skill, project instructions or a pasted prompt
Anthropic's personalization page separates three tools clearly. Profile instructions are account-wide and affect every conversation. Project instructions apply only to chats in one project. Skills customize how responses are formatted and delivered, and can be repeatable behaviors you activate on demand. They can be used independently or together.
A practical way to choose:
| Situation | Best fit |
|---|---|
| A fact about you that is always true: your role, your units, your reading level | Profile instructions |
| Background and rules for one client, course or launch | Project instructions and project files |
| A repeatable method you want applied across projects: a review checklist, a house report format | A skill |
| A one-off request with a clear endpoint | A pasted prompt |
If you are still deciding how these fit together, Where Claude's Instructions Live: Preferences, Projects and Skills maps all three in more detail.
A good first skill is boring
The best first skill is a task you do often, that has a stable method, and that you currently re-explain. Not your most creative work. Examples that fit:
- A weekly status report with a fixed structure.
- A checklist you apply when reviewing someone else's draft.
- A house style for turning meeting notes into action items.
- A way of formatting a recurring document the same way every time.
Each of these has a method that does not change, so writing it down once pays back every time.
- 1
Write the method as if for a new colleague
Short steps, in order, with what good looks like. If you cannot write it in plain steps, the method is not stable enough to be a skill yet.
- 2
Include one example of finished work
A real before and after teaches more than a paragraph of description.
- 3
Say what to do when information is missing
"If the date is not in the notes, leave it blank and flag it." This single rule prevents a lot of invented details.
- 4
Test on a real task and watch what it ignores
Whatever Claude skips is either unclear in the skill or unnecessary. Fix or remove it.
Anthropic's help page refers to separate articles for the steps to create and use custom skills, so follow those for the current screens and file requirements.
Trust what you install
A skill can contain instructions and scripts that run when Claude uses it. That is why installing one deserves the same care as installing software. On Enterprise plans, organizations can turn on skill scanning to check uploaded skills and plugins for malicious content. As an individual, stick to skills from sources you recognize, and read what a skill does before you enable it.
Common mistake
Enabling many skills at once "to see what happens." You will not be able to tell which one changed the result, and you have given each of them a chance to influence work that matters. Add one at a time and test.
Skills across assistants
Other tools have their own version of the idea. Building a Custom Grok Skill and Gemini Gems vs. a Saved Prompt cover those, and the question to ask is the same everywhere: is this method stable enough, and repeated often enough, to be worth packaging?
Official sources
- What are skills? | Claude Help Center
- Understanding Claude's personalization features | Claude Help Center
Checked on October 24, 2026. Features, plans and names change often, so the vendor's own pages are the final word.