A Claude Skill is a packaged, reusable way of doing one specific task: a set of instructions, and optionally supporting resources, that Claude can load when a request calls for it. You should create a Skill when you find yourself pasting the same detailed instructions again and again, and the task has a clear method that other people on your team should follow in the same way.
What a Skill actually is
Think of a Skill as a written procedure for a task, stored in a form Claude can pick up when it is relevant. Instead of re-explaining "how we write a client proposal" in every conversation, you write the method once. Claude then applies it whenever someone asks for a proposal.
A Skill typically bundles:
- Instructions. The steps, rules and quality bar for the task.
- Supporting material. Templates, examples or reference notes the method depends on.
- A clear description. A plain statement of what the Skill does and when it applies, so Claude can tell when to use it.
The exact packaging and where Skills can be used change as the product evolves, so check Anthropic's current documentation before building one. The concept, however, is stable. For a short definition, see the Claude certification glossary.
Skill, Project or prompt: which one do you need?
These three tools overlap, and choosing the wrong one is the most common mistake. A rough decision guide:
| Situation | Best fit |
|---|---|
| One-off request, no need to repeat it | A good prompt |
| Same background and reference files needed across many conversations on one topic | A Project |
| A repeatable method for a specific task that should work the same way every time, for many people | A Skill |
A Project answers "what does Claude need to know for this body of work?" A Skill answers "how should Claude perform this particular task?" They work well together: a team Project can hold company knowledge, while Skills hold the procedures. If you are still learning to write requests well, start with how to write a good prompt for Claude, and see what a Claude Project is for the workspace side.
Signs a prompt should become a Skill
- You have reused it several times. If a prompt has been copied and pasted more than a few times, it is already a procedure.
- The result must be consistent. Reports, summaries or emails that should follow the same structure each time.
- More than one person needs it. A good method locked in one person's notes does not scale.
- The task has steps and checks. "First do this, then check that, then format like this" is Skill material.
- The instructions are long. Long, detailed instructions are tedious to paste and easy to get wrong.
If none of these apply, a Skill is probably overkill. A simple prompt is cheaper to write and easier to change.
Examples for business teams
These are illustrations of the kind of task that suits a Skill, not descriptions of any specific customer's setup:
- Meeting minutes. Turn a transcript into minutes with decisions, owners and deadlines in your house format.
- Proposal first drafts. Follow your standard sections, tone and the checks a manager would apply.
- Contract summaries. Pull out parties, dates, obligations and unusual clauses for a human to review.
- Customer reply drafting. Apply your tone guide and escalation rules.
- Monthly report commentary. Take a standard data table and draft the narrative in a fixed structure.
In every case a person still reviews the output. A Skill makes the first draft more consistent; it does not remove the need to check accuracy.
How to write a good Skill
- Start from a prompt that already works. Run the task manually several times and keep the version that gives the best results.
- Describe one task only. A Skill that tries to cover "all of marketing" will be vague. Narrow, specific Skills work better.
- State when it applies. The description should say what the task is, so Claude can tell when to use it.
- Include a good example. One strong sample output teaches more than a paragraph of adjectives.
- List the checks. Spell out what Claude should verify before it hands back a draft.
- Test with real inputs. Try messy, realistic material, not only tidy samples, and refine.
- Name an owner. Someone should maintain it when your template or policy changes.
What to keep out of a Skill
Do not put passwords, API keys, personal data or confidential client information inside a Skill. Treat it like any shared document: assume other people can read it. If you handle personal data, confirm your approach with your data protection or compliance team; our guide to AI governance and PDPA in Malaysia gives general information only and is not legal advice.
Skills in the Claude certifications
Skills appear in the configuration and knowledge-management material for the Claude Certified Associate (CCAO-F) exam, alongside Projects and connectors. Our study notes on Configuration & Knowledge Management cover this domain, and the CCAR-F cheat sheet is useful if you are heading toward the architect exam. Agmo Studio, a Select Partner of the Anthropic Claude Partner Network, runs exam-preparation workshops; see the Claude Certified Associate program for details. For team-wide capability building, see AI training in Malaysia.