If you use Claude for the same kinds of tasks again and again, you have probably noticed something. You keep typing the same instructions. Write it in this tone. Use this format. Don’t do that thing you did last time.
Claude Skills solve this problem. A skill is a saved set of instructions that Claude loads automatically whenever it is needed. You explain the job once, and Claude remembers how to do it every time after that.
The tricky part is creating the skill in the first place. Most people start with a vague request like “make me a skill for writing emails,” and then spend the next twenty minutes answering follow-up questions.
In this post, I’m sharing a single prompt template that gives Claude everything it needs to build a complete skill in one go. You will also get three ready-to-use example prompts that you can copy, paste, and try right now.
What Is a Claude Skill?
A Claude Skill is a small package of instructions, and sometimes helper files, that teaches Claude how to do a specific task your way. Think of it as a recipe card that Claude pulls out whenever you ask for that dish.
Every skill has a name and a short description. Claude reads the description to decide when the skill should be used. When your request matches, Claude opens the full instructions and follows them.
This means you can say something as simple as “summarize this meeting” and get a perfectly formatted summary, without explaining the format every single time.
Why One Template Works for Every Skill
Claude has a built-in skill called skill-creator that helps you build new skills. When you ask it to create something, it normally interviews you first. It wants to know what the skill does, when it should run, what the output looks like, and what rules it should follow.
Those questions are useful, but they slow you down. If you answer all of them upfront in a single message, Claude can skip the interview and go straight to building, testing, and packaging your skill.
That is exactly what this template does. It is organized around the same questions Claude would ask you anyway, so nothing important gets missed.
The Universal Skill Prompt Template
Copy this template, fill in the brackets, and paste it into a new Claude chat.
Use the skill-creator skill to build a new Claude skill for me. Do not ask me interview questions unless something critical is missing; use the details below and make reasonable assumptions for anything else.
SKILL NAME: [short-name-with-hyphens]
WHAT IT DOES: [One or two sentences on the job this skill performs.]
WHEN IT SHOULD TRIGGER: [List the phrases and situations, e.g. “when I paste a prompt and say explain this”, “when I ask for blog ideas for site X”. Make the description pushy so it triggers even if I don’t name the skill.]
WHEN IT SHOULD NOT TRIGGER: [Similar requests that should NOT use this skill.]
INPUT I WILL GIVE: [What I usually paste or say: a topic, a prompt, a URL, a file, etc.]
OUTPUT I WANT: [Format (.md file, chat reply, HTML), length, structure, sections, title rules.]
STYLE AND RULES: [Tone, person (first person etc.), paragraph length, words or symbols to avoid, SEO needs, audience.]
STEPS IT SHOULD FOLLOW: [The workflow in order, e.g. 1. research, 2. outline, 3. write, 4. save as a file.]
EXAMPLE OF A GOOD RESULT: [Paste one real example you liked, or describe it.]
COMMON MISTAKES TO AVOID: [Things Claude got wrong before.]
When done, test the skill on 2 or 3 realistic prompts, show me the outputs, fix any problems, then package it as a .skill file I can install.
What Each Part of the Template Does
Every section has a clear purpose. Here is a quick look at why each one matters.
Skill Name
This is the skill’s identifier. Keep it short, lowercase, and use hyphens between words, like “meeting-notes-summarizer.” A clear name also makes it easy to find the skill later.
What It Does
One or two plain sentences describing the job. If you cannot explain the skill in two sentences, it is probably trying to do too much. Consider splitting it into two smaller skills.
When It Should Trigger
This is the most important section of the whole template. Claude decides whether to use a skill based only on its description, so this is where you list the exact phrases you normally type.
Claude also tends to be a little shy about using skills. Asking for a “pushy” description encourages Claude to write a description that triggers reliably, even when you forget to mention the skill by name.
When It Should Not Trigger
This keeps your skill from jumping in where it does not belong. For example, an email skill should not take over when you ask for a cover letter. Listing similar but different requests helps Claude draw a clean line.
Input I Will Give
Tell Claude what you will usually provide. It might be a topic, pasted text, a file, or a link. This helps the skill know what to expect and how to handle it.
Output I Want
Describe the final result in detail. Should it be a chat reply or a downloadable file? How long should it be? Which sections should it include? The more specific you are here, the more consistent your results will be.
Style and Rules
This is where your personal preferences live. Tone, reading level, paragraph length, words to avoid, and formatting habits all go here. These are the instructions you are tired of repeating.
Steps It Should Follow
List the workflow in order. Numbered steps help Claude work through the task the same way every time, which leads to fewer surprises.
Example of a Good Result
This is the second most powerful part of the template. One real example teaches tone, structure, and quality far better than paragraphs of rules. If you have a past result you loved, paste it here.
Common Mistakes to Avoid
Every time Claude gets something wrong, add it to this list. Over time, this section becomes a collection of your hard-earned fixes, and your skill keeps getting better.
The Final Instruction
The last line asks Claude to test the skill on a few realistic prompts, show you the results, fix any problems, and package everything into a .skill file. This turns a rough draft into a tested, installable skill.
How to Use This Template in Claude
Using the template takes only a few minutes.
First, make sure code execution and skills are turned on in your Claude settings, since the skill-creator needs them to build and package files.
Next, open a new chat, paste your filled-in template, and send it. Claude will draft the skill, run a few test prompts, and show you the outputs.
Review those outputs carefully. If something looks off, tell Claude what to change. It will update the skill and test it again.
Finally, Claude will give you a .skill file. Open it and use the save option to add it to your account. From then on, Claude will use the skill automatically whenever your request matches.
Example Prompt: Professional Email Writer
This skill turns rough notes into polished, ready-to-send emails. It is perfect if you write a lot of work emails and want them to sound clear and confident every time.
Use the skill-creator skill to build a new Claude skill for me. Do not ask me interview questions unless something critical is missing; use the details below and make reasonable assumptions for anything else.
SKILL NAME: professional-email-writer
WHAT IT DOES: Turns rough notes or a short description of a situation into a clear, polished, ready-to-send professional email with the right tone for the recipient.
WHEN IT SHOULD TRIGGER: When I say “write an email”, “draft an email”, “reply to this email”, “make this email sound professional”, “follow-up email”, or paste rough notes and ask to turn them into an email. Make the description pushy so it triggers for any email writing or rewriting request, even if I don’t name the skill.
WHEN IT SHOULD NOT TRIGGER: Text messages, social media posts, cover letters, or long formal letters and reports.
INPUT I WILL GIVE: Who the email is for, what I want to say or achieve, and sometimes an email I received that I need to reply to.
OUTPUT I WANT: A chat reply with a subject line and the full email body, followed by one shorter alternative version. Keep emails between 80 and 200 words unless I ask for more.
STYLE AND RULES: Clear, polite, and confident. Start with the main point in the first two sentences. One idea per paragraph. Use plain words instead of corporate jargon. End with a clear next step or request. Match formality to the recipient (manager, client, colleague, or stranger). Never invent facts, dates, or numbers I did not give.
STEPS IT SHOULD FOLLOW: 1. Identify the recipient and the goal of the email. 2. Choose the right tone. 3. Write a specific subject line. 4. Write the email with the main point first. 5. Add a clear call to action. 6. Write a shorter alternative. 7. Check for missing details and list any placeholders like [date] that I need to fill in.
EXAMPLE OF A GOOD RESULT: Subject: “Request to move Thursday’s meeting to Friday”. The email opens by stating the request, gives one sentence of reason, suggests two time options, and ends with “Let me know which works best for you.”
COMMON MISTAKES TO AVOID: Long, rambling openings like “I hope this email finds you well” before getting to the point. Overly formal or robotic wording. Vague subject lines. Making up details. Emails that are too long.
When done, test the skill on 2 or 3 realistic prompts, show me the outputs, fix any problems, then package it as a .skill file I can install.
Example Prompt: Meeting Notes Summarizer
This skill turns messy notes or transcripts into a clean summary with decisions and action items. It is a lifesaver if you sit through a lot of calls and never have time to write proper recaps.
Use the skill-creator skill to build a new Claude skill for me. Do not ask me interview questions unless something critical is missing; use the details below and make reasonable assumptions for anything else.
SKILL NAME: meeting-notes-summarizer
WHAT IT DOES: Turns messy meeting notes or transcripts into a clean, organized summary with key decisions, action items, owners, and deadlines.
WHEN IT SHOULD TRIGGER: When I say “summarize this meeting”, “clean up my meeting notes”, “action items from this call”, “meeting recap”, or paste a transcript or rough notes from a meeting or call. Make the description pushy so it triggers whenever I share meeting content, even if I don’t name the skill.
WHEN IT SHOULD NOT TRIGGER: Summarizing articles, books, videos, or research papers. Writing meeting agendas before a meeting happens.
INPUT I WILL GIVE: Raw meeting notes, a pasted transcript, or an uploaded transcript file, and sometimes the meeting name and date.
OUTPUT I WANT: A chat reply with these sections: Meeting overview (2 to 3 sentences), Key decisions, Action items (each with task, owner, and deadline), Open questions, and Next meeting (if mentioned). Keep the whole summary under 400 words.
STYLE AND RULES: Neutral, factual, and easy to scan. Use short sentences. Write action items starting with a verb. If an owner or deadline is not mentioned, write “Not assigned” or “No deadline set” instead of guessing. Never add opinions or information that was not in the notes.
STEPS IT SHOULD FOLLOW: 1. Read the full notes or transcript. 2. Identify the meeting purpose. 3. Pull out every decision made. 4. Pull out every task with its owner and deadline. 5. List unresolved questions. 6. Write the overview last. 7. Check that nothing important was left out.
EXAMPLE OF A GOOD RESULT: Overview: “The team reviewed the website redesign and agreed on a launch timeline.” Key decision: “Launch moved to the end of next month.” Action item: “Finalize homepage design. Owner: Priya. Deadline: Friday.”
COMMON MISTAKES TO AVOID: Guessing owners or deadlines. Mixing decisions with general discussion. Copying the transcript instead of summarizing it. Missing action items buried in the middle of the conversation. Making the summary too long.
When done, test the skill on 2 or 3 realistic prompts, show me the outputs, fix any problems, then package it as a .skill file I can install.
Example Prompt: Social Media Caption Generator
This skill writes scroll-stopping captions tailored to each platform. It works well for small business owners, creators, and anyone who posts regularly but struggles to come up with fresh words.
Use the skill-creator skill to build a new Claude skill for me. Do not ask me interview questions unless something critical is missing; use the details below and make reasonable assumptions for anything else.
SKILL NAME: social-caption-generator
WHAT IT DOES: Writes engaging, platform-ready social media captions with hooks, calls to action, and relevant hashtags for Instagram, LinkedIn, Facebook, and X.
WHEN IT SHOULD TRIGGER: When I say “write a caption”, “Instagram caption”, “LinkedIn post”, “caption for this photo”, “social media post for”, or describe a product, event, or photo I want to post about. Make the description pushy so it triggers for any social media caption or short post request, even if I don’t name the skill.
WHEN IT SHOULD NOT TRIGGER: Long blog posts, emails, ad scripts for video, or full social media content calendars.
INPUT I WILL GIVE: What the post is about, the platform, and sometimes the brand voice, target audience, or a photo description.
OUTPUT I WANT: A chat reply with 3 caption options, each in a different style (short and punchy, storytelling, and question-based). Include 5 to 10 relevant hashtags for Instagram, 3 to 5 for LinkedIn and X, and none for Facebook unless I ask.
STYLE AND RULES: Start every caption with a strong hook in the first line. Match the platform: casual and visual for Instagram, professional and insightful for LinkedIn, short and sharp for X (under 280 characters), conversational for Facebook. Use emojis only where they fit the platform and tone. End with a clear call to action like a question, a save prompt, or a link mention. Avoid generic phrases like “Check this out!”
STEPS IT SHOULD FOLLOW: 1. Identify the platform, audience, and goal. 2. Write a strong hook for each option. 3. Write the caption body in three different styles. 4. Add a call to action. 5. Add platform-appropriate hashtags. 6. Check length limits for each platform.
EXAMPLE OF A GOOD RESULT: For a new coffee shop on Instagram: “Your Monday just got a lot less Monday. ☕ Our new cinnamon oat latte is here, and it tastes like a warm hug in a cup. Tag the friend who owes you a coffee! #coffeelover #latteart #newmenu”
COMMON MISTAKES TO AVOID: Weak openings that don’t grab attention. Using the same tone for every platform. Too many hashtags or irrelevant ones. Going over character limits. Captions with no call to action.
When done, test the skill on 2 or 3 realistic prompts, show me the outputs, fix any problems, then package it as a .skill file I can install.
Tips for Getting Better Skills
A few small habits make a big difference in how well your skills perform.
Spend the most time on the trigger section. List the real phrases you actually type, not polished versions. If you usually say “clean this up,” include those exact words.
Always add a real example. Even one short sample of a result you liked will shape the tone and structure more than any list of rules.
Keep each skill focused on one job. A skill that writes emails, captions, and reports all at once will do none of them very well. Build three small skills instead.
Update the mistakes section over time. Whenever Claude gets something wrong, open the skill-creator again, ask it to update your skill, and add the fix to the list.
Short on time? The bare minimum version of the template is the skill name, what it does, trigger phrases, output format, rules, and one example. Everything else improves quality but is not required.
Claude Skills are one of the easiest ways to stop repeating yourself and start getting consistent results. The hardest part has always been explaining what you want clearly enough, and this template takes care of that.
Start with one of the three example prompts above to see how the process works. Once you are comfortable, fill in the template for the task that eats up most of your time. Within a few minutes, you will have a custom skill that handles it for you, the same way, every single time.