Claude skill examples, ready to download
Six complete skills you can download as a ZIP and use as-is, or open in the creator to customize. Each one follows best practices: a description that triggers, clear instructions and an output format.
What each skill in the gallery does
Email writer
Writes and improves professional emails with the right tone. It triggers when you ask for a request, a complaint, a follow-up or a formal reply, and returns the email with subject, greeting, body and sign-off. What people usually change when adapting it: the level of formality and the signature.
CSV data analyst
Summarizes tables, computes metrics and spots trends. Its value is the fixed output format —summary, key metrics, findings and recommended next step— which makes two analyses done weeks apart comparable. It includes the rule of never guessing what an ambiguous column means: ask instead.
Code reviewer
Catches errors and suggests improvements using your criteria, not the model's generic ones. This is the most rewarding one to customise: it is where you write your team's rules (naming conventions, what counts as technical debt, what never passes review) and stop repeating them in every conversation.
Context translator
Translates while keeping tone, terminology and formatting. Built for text where a literal translation ruins the result: documentation with terms that stay in English, marketing copy with a specific register, or UI strings where length matters.
Meeting summarizer
Turns scattered notes into minutes with decisions and tasks. It separates what was decided from what was merely discussed, and pulls out action items with an owner. If your team follows a minutes template, this is the example that pays off fastest.
SEO assistant
Writes copy around your keywords without falling into mechanical repetition. It includes the heading structure and the reminder to write for the person reading, which is what actually ranks.
How to adapt them
Downloading one and using it as-is works, but the real jump comes when you make it yours. Three changes that are almost always worth it:
- Sharpen the description. It is the only part Claude always reads, and it decides whether the skill fires or stays asleep. Add the specific situations where you would use it, in your own words.
- Write rules with their reason. “Don't make up data” works worse than “don't make up data: an invented figure in a client email is a real problem”.
- Add your own examples. One input-and-output pair from your actual work beats three paragraphs of instructions.
Once you have your version, check the description with the quality meter and go over the best practices before downloading it.
How to use these examples
Download the ZIP of the skill you like, unzip it and copy the folder into ~/.claude/skills/. Full guide in how to install a skill. Want to change something? Build your own from scratch in the creator.