Claude AI Skills: 29 Copy-Paste Prompts That Save You Hours

Most people use Claude like a search box. They type a question, get an answer, close the tab, and type the same kind of question again tomorrow. Claude AI skills fix that waste. A skill is a saved set of instructions that turns a repeated task into a one-line request, so the work that used to take fifteen minutes of prompt writing now takes seconds.

This post hands you 29 ready-made Claude AI skills. Every one of them comes with a copy block you can paste straight into the skill creator without editing a single word. You will also learn how the three fields work, and which skills are worth building on day one.

Table of contents

1. What are Claude AI skills?
2. How to create a skill in Claude, step by step
3. Writing skills you will use every week
4. Learning skills that shorten the study loop
5. Business and marketing skills
6. Coding skills for developers
7. Career and personal development skills
8. Research and analysis skills
9. Productivity skills for the working week
10. Creative skills worth keeping around
11. Which skills to build first
12. Mistakes that make a skill useless
13. Final thoughts

What are Claude AI skills?

A skill is a reusable instruction pack with a name, a short description, and a body of instructions. Once it is saved, Claude reads those instructions automatically whenever your request matches the description.

A prompt is something you type once. A skill is something you teach once and then trigger forever.

The difference matters more than it sounds. A good prompt lives in your clipboard or your memory, and both of those leak. A skill lives inside Claude, keeps its quality on the tenth run, and works the same way for every person on your team.

Why skills beat saved prompts

• Consistency: the output format never drifts, because the format is written down.
• Speed: you type the topic, not the whole instruction stack.
• Shareable: one text block can be handed to a teammate and used immediately.
• Improvable: when an output disappoints you, you edit the skill once and every future run gets better.

How to create a skill in Claude, step by step

The skill creator asks for three things. Understanding what belongs in each field is the whole trick, and most weak skills fail here rather than in the wording.

The three fields explained

1. Skill name — short and literal, such as Resume Optimizer. This is a label, not a slogan.
2. Description — one sentence describing what the skill does and when to use it. Claude reads this to decide whether the skill applies to your request, so write it for matching, not for marketing.
3. Instructions — the actual recipe: the input you will supply, the output you expect, and the numbered steps in between.

The steps

1. Open Claude and go to Settings, then Capabilities, then Skills.
2. Choose Create skill.
3. Paste the skill name from any block below into the name field.
4. Paste the description line into the description field.
5. Paste everything under Instructions into the instructions box.
6. Save it, then start a new chat and type the skill name plus your topic.

Developers working in the terminal can do the same thing as a file. Create .claude/skills/resume-optimizer/SKILL.md, put name and description in the YAML front matter at the top, and put the instructions in the body. If you already work in the CLI, our breakdown of Claude Code commands every developer should know pairs well with this.

---
name: resume-optimizer
description: Rewrite resume bullets to match a target job description and pass ATS filters.
---

Input: Current resume text + target job description
Output: Rewritten bullets + missing keywords + formatting fixes

Steps:
1. Read the job description and pull out the 10 most repeated skills and keywords.
2. Compare them against the resume and list what is missing.
3. Rewrite each bullet in the format: action verb + task + measurable result.
4. Flag anything vague, such as "responsible for", and replace it.
5. Return the rewritten resume, then the keyword gap list, then formatting notes.

That file is the same skill in a different wrapper. The three fields never change: name, description, instructions.

Rule of thumb: if you cannot describe the input and the output in one line each, the skill is not ready to be saved yet.

Writing skills you will use every week

These four Claude AI skills cover the writing most people repeat without ever getting faster at it: posts, subject lines, product copy, and threads.

1. LinkedIn post generator

Turns a half-formed thought into a post with a hook, a middle, and a reason for someone to comment.

Skill name: LinkedIn Post Generator
Description: Turn one idea or headline into a ready-to-post LinkedIn update with a strong hook and a comment-driving question.

Instructions:
Input: Topic or headline + industry + tone (professional, casual, or story-driven)
Output: Hook line + 3 to 5 short paragraphs + takeaway + closing question + 3 hashtags

Steps:
1. Ask for the topic, the industry, and the tone if the user did not provide them.
2. Write a one-line hook that states a bold result, a mistake, or a surprising number.
3. Expand into 3 to 5 short paragraphs, one idea each, separated by blank lines.
4. Never write more than two sentences in a paragraph.
5. Close with a one-line takeaway, then a question that invites replies.
6. Add exactly 3 relevant hashtags.

Example:
Input: I cut my weekly reporting time in half + SaaS + story-driven
Output: Hook, short story, lesson, question, hashtags. Ready to paste.

Time: under 1 minute

2. Email subject line optimizer

Subject lines decide whether the rest of the email ever gets read. This skill returns options ranked by likely open rate instead of one safe guess.

Skill name: Email Subject Line Optimizer
Description: Rewrite a dull email subject into high-open-rate options ranked by expected performance.

Instructions:
Input: Email topic or original subject line + audience + goal (open, click, or reply)
Output: 8 subject line options, ranked, each with a one-line reason and a character count

Steps:
1. Identify the single promise the email makes to the reader.
2. Write 8 options across these angles: curiosity, benefit, number, question, urgency, personal, contrarian, plain-direct.
3. Keep every option under 50 characters so it survives mobile inboxes.
4. Rank them strongest to weakest for the stated goal.
5. Add a one-line reason for each ranking.
6. Suggest one matching preview text line for the top option.

Rules:
- No all-caps, no more than one exclamation mark, no spam trigger words.

Example:
Input: Monthly newsletter is out + developers + click
Output: 8 ranked options with reasons and character counts.

3. Product description writer

Feature lists do not sell. This skill converts specs into benefit-led copy that still carries the keywords a marketplace needs.

Skill name: Product Description Writer
Description: Convert a product name and feature list into sales-driven marketplace copy with keywords built in.

Instructions:
Input: Product name + key features + target audience + platform (Amazon, Shopify, or website)
Output: Headline + 5 bullet benefits + 120-word description + keyword list

Steps:
1. Translate every feature into a benefit by asking what it does for the buyer.
2. Write a headline under 80 characters containing the main keyword.
3. Write 5 bullets, each starting with a capitalised benefit phrase, then the supporting feature.
4. Write a 120-word description in second person, speaking to the buyer as you.
5. List 10 search keywords a buyer would actually type.
6. End with one line handling the most likely objection, such as sizing or compatibility.

Rules:
- Never invent certifications, awards, or test results.
- Keep pricing or savings claims approximate unless exact figures are supplied.

Example:
Input: Steel water bottle + 24-hour cold + leakproof + gym users + Amazon
Output: Headline, 5 bullets, description, keywords, objection line.

4. Twitter thread creator

One idea, eight tweets, each one earning the next. The skill enforces the structure that makes threads readable.

Skill name: Twitter Thread Creator
Description: Expand a single idea into a structured 5 to 8 tweet thread with a hook and a closing call to action.

Instructions:
Input: Main idea + audience + thread length (5 to 8 tweets)
Output: Numbered tweets, each under 280 characters, copy-paste ready

Steps:
1. Write tweet 1 as the hook: a promise, a result, or a myth you are about to break.
2. Give every following tweet exactly one point, written so it can stand alone.
3. Start each tweet with a concrete noun or verb, never with and or so.
4. Put the most useful tweet in the middle, not at the end.
5. Close with a one-line summary plus a follow or reply request.
6. Print a character count after each tweet.

Rules:
- Maximum one emoji per tweet.
- No manual numbering like 1/8 inside the text.

Example:
Input: Why most side projects die + indie developers + 7 tweets
Output: 7 numbered tweets with character counts.

Learning skills that shorten the study loop

These four turn passive reading into something you can be tested on, which is the part most self-study quietly skips.

5. Interview question generator

Practice against the questions you will actually be asked, including the awkward ones nobody prepares for.

Skill name: Interview Question Generator
Description: Produce realistic interview questions for any role, with answer skeletons and follow-ups.

Instructions:
Input: Job title + industry + experience level (fresher, mid, senior)
Output: 10 common questions + 5 hard questions + answer structure for each

Steps:
1. Split questions into technical, behavioural, and role-specific.
2. Write 10 questions that appear in almost every interview for this role.
3. Write 5 harder questions that separate strong candidates from average ones.
4. For each question, give a 3-line answer skeleton, not a full script.
5. Add one follow-up question the interviewer is likely to ask next.
6. Finish with 3 questions the candidate should ask the interviewer.

Rules:
- Match difficulty to the stated experience level.
- Never present salary figures as exact; use approximate ranges only.

Example:
Input: Backend developer + fintech + mid-level
Output: 15 questions with answer skeletons and follow-ups.

6. Study notes converter

Paste messy lecture notes and get back something structured enough to revise from the night before an exam.

Skill name: Study Notes Converter
Description: Turn raw messy notes into organised summaries with key takeaways and self-test questions.

Instructions:
Input: Raw notes, lecture text, or scribbles (any length)
Output: Structured outline + 5 key takeaways + 5 quiz questions with answers + a text mind map

Steps:
1. Detect the main topic and split the notes into 3 to 6 logical sections.
2. Rewrite each section as short bullets, keeping every fact from the original.
3. Mark anything that looks like a definition with the label DEFINITION.
4. Write 5 key takeaways in plain language.
5. Write 5 quiz questions covering the hardest points, with answers below them.
6. Draw a simple indented text mind map showing how the sections connect.

Rules:
- Never add facts the notes do not contain.
- List anything unclear under a heading called Needs checking.

Example:
Input: two pages of biology lecture scribbles
Output: outline, takeaways, quiz, mind map, needs-checking list.

7. Concept explainer

The most reusable skill on this list. It explains anything at the level you ask for, with an analogy that actually lands.

Skill name: Concept Explainer
Description: Explain any complex topic in simple language with analogies, examples, and a plain-English summary.

Instructions:
Input: The topic + the level to explain at (child, beginner, or working professional)
Output: One-line definition + analogy + step-by-step explanation + real example + common misunderstanding

Steps:
1. Give a one-sentence definition with no jargon in it.
2. Give one everyday analogy, then say clearly where the analogy breaks down.
3. Explain the mechanism in 4 to 6 numbered steps.
4. Give one real-world example the reader has probably met before.
5. State the single most common misunderstanding about the topic.
6. Close with a 3-line summary that could be repeated from memory.

Rules:
- Any technical term you use must be defined in the same sentence.
- Match the depth to the requested level; do not oversimplify for professionals.

Example:
Input: How does HTTPS work + beginner
Output: definition, analogy, 5 steps, example, misconception, summary.

8. Skill gap analyzer

Career advice usually stops at learn more. This one produces an ordered list with a timeline attached.

Skill name: Skill Gap Analyzer
Description: Compare a current role against a target role and return a prioritised learning roadmap.

Instructions:
Input: Current role + target role + industry + hours available per week
Output: Skill gap list + priority order + resources + week-by-week roadmap

Steps:
1. List the skills the target role expects, split into must-have and nice-to-have.
2. List the skills the current role already builds.
3. Produce the gap: what is missing, and how large each gap is (small, medium, large).
4. Rank the gaps by hiring impact, not by how interesting they are.
5. Suggest one free and one paid resource for each top gap.
6. Build a roadmap that fits the stated weekly hours, with a checkpoint every 4 weeks.

Rules:
- Never promise a specific salary outcome or a guaranteed timeline.

Example:
Input: Support engineer to backend developer + SaaS + 8 hours a week
Output: gap list, ranked priorities, resources, roadmap.

Business and marketing skills

Four skills that replace the slow parts of marketing: validating an idea, naming it, selling it, and posting about it.

9. Business idea validator

An honest second opinion before you spend three months building. It is written to argue with you, not agree with you.

Skill name: Business Idea Validator
Description: Stress-test a business idea and return a viability verdict with risks, opportunities, and next steps.

Instructions:
Input: The business idea in 1 to 2 lines + target market + region
Output: Verdict + strengths + risks + market gaps + 5 validation steps to run this week

Steps:
1. Restate the idea in one sentence to confirm you understood it.
2. Name the exact customer and the problem they pay to remove today.
3. List 3 strengths and 5 realistic risks, with the biggest risk first.
4. Name the closest existing alternatives, including doing nothing.
5. Give a verdict: strong, needs reshaping, or weak, with the reason in one line.
6. List 5 cheap validation steps that can be run within seven days.

Rules:
- Be direct about weaknesses; do not soften a bad idea.
- Do not state market sizes or revenue as exact figures; use approximate ranges and say they are estimates.

Example:
Input: Subscription tiffin service for hostel students + tier-2 city
Output: verdict, strengths, risks, alternatives, 5 validation steps.

10. Tagline and slogan generator

Twenty options beat one, because you only recognise the right tagline when you see it next to the wrong ones.

Skill name: Tagline and Slogan Generator
Description: Generate memorable brand taglines from a company description and brand personality.

Instructions:
Input: Company name + what it does + brand personality + target market
Output: 15 taglines grouped by style + top 3 recommendations + usage notes

Steps:
1. Extract the single promise the brand makes to its customer.
2. Write 15 taglines grouped as: benefit-led, playful, bold, minimal, and descriptive.
3. Keep every tagline under 7 words.
4. Pick the top 3 and explain in one line each why they fit the personality.
5. Show how the top pick reads next to the company name in a logo lockup.
6. Flag any option that is too close to a well-known existing slogan.

Rules:
- No rhyming for the sake of rhyming.
- Avoid empty words such as solutions, synergy, and next-generation.

Example:
Input: MmantraTech + practical tech tutorials + friendly and sharp + developers
Output: 15 taglines, top 3, lockup example.

11. Email campaign copy generator

Subject, body, and call to action written as one unit, so the promise at the top matches the button at the bottom.

Skill name: Email Campaign Copy Generator
Description: Write a complete campaign email with subject line, body, and call to action for a stated goal.

Instructions:
Input: Product or offer + audience + goal (sales, awareness, or re-engagement) + tone
Output: Subject line + preview text + email body + call to action + one follow-up email

Steps:
1. State the one action the reader should take, and keep the whole email pointed at it.
2. Write the subject line and preview text as a pair, not as duplicates.
3. Open the body with the reader problem, not with company news.
4. Keep the body under 180 words, in paragraphs of two lines each.
5. Write one primary call to action and no competing links.
6. Write a shorter follow-up email for people who did not open the first.

Rules:
- No exact discount, price, or revenue claims unless supplied by the user.
- No fake scarcity such as invented deadlines.

Example:
Input: Course launch + junior developers + sales + friendly
Output: subject, preview, body, CTA, follow-up email.

12. Social media caption writer

Captions that fit the platform instead of the same paragraph pasted everywhere.

Skill name: Social Media Caption Writer
Description: Write platform-specific captions with hooks, emojis, and hashtags that drive engagement.

Instructions:
Input: Photo or video description + platform (Instagram, TikTok, or Facebook) + goal + hashtag preference
Output: 3 caption options (short, medium, story-style) + hashtag set + best posting angle

Steps:
1. Ask what is happening in the image or video if the description is thin.
2. Write 3 captions: one under 10 words, one around 30 words, one mini story of 60 words.
3. Put the hook in the first 5 words, because the rest gets truncated.
4. Add one clear call to action such as save, share, or comment.
5. Give 12 hashtags split into 4 broad, 4 niche, and 4 very specific.
6. Suggest the single strongest option and say why.

Rules:
- Emojis support the text, never replace words.
- Never use hashtags unrelated to the content.

Example:
Input: Desk setup photo + Instagram + saves + moderate hashtags
Output: 3 captions, 12 hashtags, recommendation.

Coding skills for developers

These three cover the daily friction of writing code: understanding it, fixing it, and matching it. If you already automate work in the terminal, they sit nicely alongside Claude AI slash commands explained.

13. Code explanation chatbot

Paste any snippet and get a line-by-line reading, plus the bugs the author did not mention.

Skill name: Code Explanation Chatbot
Description: Explain any code snippet line by line in plain English, including risks and edge cases.

Instructions:
Input: Code snippet (any language) + the reader level (beginner or experienced)
Output: One-line summary + line-by-line explanation + data flow + risks + suggested improvements

Steps:
1. Detect the language and state it.
2. Summarise in one sentence what the code does overall.
3. Explain each meaningful line or block in plain English, in order.
4. Describe how data moves through the code from input to output.
5. List potential issues: unhandled errors, edge cases, performance traps, security risks.
6. Suggest up to 3 concrete improvements, with a short corrected snippet for the top one.

Rules:
- Never claim the code works if you cannot verify the surrounding context.
- Say clearly when behaviour depends on code that was not shown.

Example:
Input: a 20-line Python function + beginner
Output: summary, line-by-line walkthrough, risks, improved snippet.

14. Error message debugger

Stack traces are written for the compiler, not for you. This skill translates them and gives you the fix order.

Skill name: Error Message Debugger
Description: Decode an error message, explain the root cause, and return ordered fixes.

Instructions:
Input: The full error or stack trace + language or framework + what the user was doing
Output: Plain-English meaning + likely causes ranked + fix steps + prevention tip

Steps:
1. Translate the error into one plain sentence a beginner would understand.
2. Point to the exact line or call in the trace that matters, and say why.
3. List the likely causes ranked from most to least probable.
4. Give numbered fix steps for the top cause, with the command or code change to make.
5. Add a quick check the user can run to confirm the fix worked.
6. Finish with one prevention tip so the error does not return.

Rules:
- Ask for the surrounding code if the trace alone is not enough.
- Never invent a file path or line number that was not in the trace.

Example:
Input: SQLSTATE 1045 access denied + Laravel + running migrations
Output: meaning, ranked causes, fix steps, verification, prevention.

15. Regex pattern generator

Describe the pattern in English, get a working expression plus the test cases that prove it.

Skill name: Regex Pattern Generator
Description: Build a regular expression from a plain-English description, with an explanation and test cases.

Instructions:
Input: What to match in plain English + language or tool (JavaScript, Python, PHP, grep) + case sensitivity
Output: The regex + a piece-by-piece explanation + matching examples + non-matching examples

Steps:
1. Restate the matching rule in one sentence and list any assumptions.
2. Produce the regex in the correct syntax and delimiters for the stated language.
3. Break the pattern into parts and explain what each part does.
4. Give 5 strings that match and 5 that do not, and say why for each.
5. Warn about greedy matching, backtracking cost, or unicode issues if they apply.
6. Give a simpler alternative if a plain string method would do the job better.

Rules:
- Never return an untested-looking pattern without example strings.
- Prefer readable patterns over the shortest possible one.

Example:
Input: Match Indian mobile numbers with optional +91 + JavaScript + case-insensitive
Output: regex, breakdown, 5 matches, 5 non-matches.

Career and personal development skills

Four skills for the paperwork of a career. Each one produces something you can send, not advice about sending it.

16. Resume optimizer

Rewrites your bullets against a specific job description so the keywords a filter looks for are actually present.

Skill name: Resume Optimizer
Description: Rewrite resume bullets to match a target job description and pass automated screening filters.

Instructions:
Input: Current resume text + the job description being applied to
Output: Rewritten bullets + missing keyword list + formatting fixes + a match score out of 10

Steps:
1. Pull the 10 most repeated skills and keywords from the job description.
2. Compare them against the resume and list what is missing.
3. Rewrite each bullet as action verb + task + measurable result.
4. Replace vague phrases such as responsible for and worked on.
5. Flag formatting that automated screeners handle badly: tables, columns, graphics, headers.
6. Give a match score out of 10 and the two changes that would raise it most.

Rules:
- Never invent experience, employers, dates, or metrics that were not supplied.
- If a metric is missing, mark it as ADD NUMBER instead of guessing one.

Example:
Input: 2-page resume + backend developer job post
Output: rewritten bullets, keyword gaps, formatting fixes, score.

17. Cover letter generator

A letter about the company and the role, not a paragraph restating the resume that is already attached.

Skill name: Cover Letter Generator
Description: Write a personalised cover letter from a job title, company, and short experience summary.

Instructions:
Input: Job title + company name + your experience summary + one achievement + tone
Output: Full cover letter under 300 words + a short 120-word version

Steps:
1. Open with the specific role and one reason this company in particular.
2. Use paragraph 2 for the single most relevant achievement, with its result.
3. Use paragraph 3 to connect your skills to two requirements from the job post.
4. Close with a direct, confident line asking for the conversation.
5. Keep the whole letter under 300 words.
6. Produce a shortened 120-word version for email body use.

Rules:
- Never restate the resume line by line.
- Never invent achievements or claim familiarity with tools not mentioned.
- No phrases such as I am writing to apply or to whom it may concern.

Example:
Input: Frontend developer + a design-led startup + 3 years React + rebuilt checkout flow
Output: full letter plus short email version.

18. Personal brand statement creator

The About section most people rewrite ten times and still hate. This gives you three lengths at once.

Skill name: Personal Brand Statement Creator
Description: Write a compelling About Me for LinkedIn, a portfolio, or a website in three lengths.

Instructions:
Input: Skills + achievements + values + target audience + platform
Output: Short bio (30 words) + medium bio (80 words) + long bio (150 words) + a one-line headline

Steps:
1. Identify who the reader is and what they need to believe after reading.
2. Write the one-line headline: role + speciality + who you help.
3. Write the 30-word version for bios with tight character limits.
4. Write the 80-word version with one proof point included.
5. Write the 150-word version with a short origin line and a closing invitation.
6. Offer a first-person and a third-person variant of the medium version.

Rules:
- No unverifiable superlatives such as best or world-class.
- Every claim must trace back to something the user supplied.

Example:
Input: Laravel + APIs + shipped 3 fintech products + clarity + hiring managers + LinkedIn
Output: headline, 3 bio lengths, first and third-person variants.

19. Goal breakdown planner

Big goals fail because nobody converts them into a Tuesday. This skill does that conversion.

Skill name: Goal Breakdown Planner
Description: Turn a large goal into milestones, weekly tasks, and daily habits with a progress checklist.

Instructions:
Input: The goal + deadline + current situation + hours available per week
Output: Milestones + weekly task list + daily habits + checkpoints + failure plan

Steps:
1. Rewrite the goal so it has a number and a date attached.
2. Work backwards from the deadline into 3 to 5 milestones.
3. Break the first milestone into weekly tasks that fit the stated hours.
4. Name 2 daily habits, each under 30 minutes, that move the goal forward.
5. Set a checkpoint question to answer at the end of every week.
6. Add a recovery plan for the week the plan gets broken, because it will.

Rules:
- Never plan more hours than the user said they have.
- Prefer fewer tasks done fully over a long list done partly.

Example:
Input: Launch a side project + 90 days + full-time job + 8 hours a week
Output: milestones, week 1 tasks, daily habits, checkpoints, recovery plan.

Research and analysis skills

Three skills that compress a week of tab-hopping into a briefing you can act on.

20. Competitor analysis brief

A structured read on who you are up against and where the open space actually is.

Skill name: Competitor Analysis Brief
Description: Produce a competitive brief covering rival strengths, weaknesses, market gaps, and threats.

Instructions:
Input: Your company + 2 to 5 competitor names + industry + region
Output: Per-competitor summary + comparison points + market gaps + threats + 3 recommended moves

Steps:
1. Summarise each competitor in 3 lines: who they serve, what they lead on, where they are weak.
2. Compare them on positioning, pricing model, audience, and content presence.
3. Identify gaps nobody is serving well.
4. List the 3 biggest threats to your company from this set.
5. Recommend 3 moves, ordered by effort against impact.
6. State clearly which claims are inference rather than confirmed fact.

Rules:
- Never state competitor revenue, funding, or headcount as exact figures.
- Label any assumption as ASSUMPTION so it can be checked later.

Example:
Input: A tech blog + 3 rival blogs + developer education + India
Output: 3 summaries, comparison, gaps, threats, 3 moves.

21. Market research summarizer

Trends, numbers, and risks in one page, with the sources you still need to verify marked as such.

Skill name: Market Research Summarizer
Description: Summarise the trends, statistics, opportunities, and risks of any industry into a one-page brief.

Instructions:
Input: Industry or topic + specific area of interest + region + time horizon
Output: 5 trends + key statistics + opportunities + risks + 3 recommendations + what to verify

Steps:
1. State the scope you are summarising in one line.
2. List 5 current trends, each with a one-line reason it is happening.
3. Give the key numbers as approximate ranges, never as precise figures.
4. List opportunities and risks separately, ranked by impact.
5. Give 3 recommendations tied to the stated interest area.
6. End with a Verify this list naming every claim that needs a live source.

Rules:
- Never present a statistic as confirmed without a source.
- Say plainly when information may be out of date.

Example:
Input: EdTech + short-form video learning + India + next 12 months
Output: trends, approximate numbers, opportunities, risks, verify list.

22. Customer persona builder

Three personas with real pain points, so your copy stops talking to an average that does not exist.

Skill name: Customer Persona Builder
Description: Build detailed buyer personas with demographics, behaviours, pain points, and objections.

Instructions:
Input: Product or service + target market + any known customer data
Output: 3 personas, each with name, profile, goals, pain points, objections, and buying triggers

Steps:
1. Build 3 distinct personas: the ideal buyer, the reluctant buyer, and the wrong-fit buyer.
2. For each, give a name, age range, role, and one-line background.
3. List their top 3 goals and top 3 frustrations in their own words.
4. Name the objection that stops them from buying, and the answer to it.
5. Name the trigger event that makes them start looking for a product like yours.
6. Suggest the single message and channel most likely to reach each persona.

Rules:
- Mark every detail not supported by supplied data as an assumption.
- Keep the wrong-fit persona honest; it saves marketing money.

Example:
Input: Paid coding course + working professionals + India
Output: 3 personas with goals, pains, objections, triggers, channels.

Productivity skills for the working week

Four skills aimed at the admin that eats a workday: meetings, projects, decisions, and the inbox.

23. Meeting agenda generator

An agenda with time boxes and a decision owner turns a status meeting into a short one.

Skill name: Meeting Agenda Generator
Description: Build a structured meeting agenda with time allocation, preparation notes, and follow-up template.

Instructions:
Input: Meeting topic + attendees + duration + key discussion points
Output: Agenda with time boxes + pre-read list + decision list + follow-up template

Steps:
1. State the one outcome that makes this meeting worth holding.
2. Order the agenda so decisions come before updates, not after.
3. Give every item a time box, and leave 10 percent of the meeting unallocated.
4. Name what each attendee must read or prepare beforehand.
5. List the decisions that must be made and who owns each one.
6. Add a follow-up template with decisions, owners, and deadlines.

Rules:
- If the outcome can be reached by an email, say so at the top.
- Never schedule more items than the duration realistically holds.

Example:
Input: Sprint planning + 5 attendees + 45 minutes + scope, blockers, release date
Output: timed agenda, pre-reads, decision owners, follow-up template.

24. Task breakdown assistant

Splits an intimidating project into tasks small enough to start today, in dependency order.

Skill name: Task Breakdown Assistant
Description: Break a large project into ordered tasks with estimates, dependencies, and priorities.

Instructions:
Input: Project description + deadline + people or resources available
Output: Task list with estimates + dependency order + priority ranking + risk list

Steps:
1. Restate the finished project in one sentence so scope is agreed.
2. Break it into phases, then into tasks no longer than one working day each.
3. Estimate every task in hours and mark the estimate as approximate.
4. Mark dependencies clearly: which task blocks which.
5. Rank tasks by priority using impact and blocking risk.
6. List the 3 tasks most likely to overrun and why.

Rules:
- Any task larger than one day must be split further.
- Never present time estimates as guaranteed.

Example:
Input: Rebuild company website + 6 weeks + 1 developer, 1 designer
Output: phased task list, estimates, dependencies, priorities, risks.

25. Decision matrix maker

Scores your options against weighted criteria, which is how you find out what you actually care about.

Skill name: Decision Matrix Maker
Description: Score competing options against weighted criteria and return a clear recommendation.

Instructions:
Input: Options to compare + decision criteria + weight or importance of each criterion
Output: Scored matrix + weighted totals + recommendation + risks + reversal cost

Steps:
1. Confirm the options and criteria, and ask for weights if they were not given.
2. Score each option against each criterion from 1 to 5, with a one-line reason.
3. Multiply scores by weights and show the weighted total per option.
4. Give a clear recommendation, not a balanced non-answer.
5. State the strongest argument against the recommendation.
6. State how expensive it would be to reverse this decision later.

Rules:
- Never leave the recommendation ambiguous.
- Show the scoring so the user can adjust any weight themselves.

Example:
Input: Three hosting providers + cost, speed, support, scaling + cost weighted highest
Output: scored matrix, totals, recommendation, counter-argument, reversal cost.

26. Email reply generator

The fastest win on this list. Paste the email, pick a tone, send the reply.

Skill name: Email Reply Generator
Description: Draft a professional email reply in a chosen tone, with alternative versions.

Instructions:
Input: The original email + desired tone (formal, casual, apology, urgent, or decline) + any facts to include
Output: Ready-to-send reply + 2 alternative tone versions + suggested subject line

Steps:
1. Identify what the sender is actually asking for, including anything implied.
2. Answer that request in the first two lines of the reply.
3. Keep the reply under 150 words unless detail was requested.
4. Match the requested tone exactly; do not over-apologise.
5. End with the next step and a date where one applies.
6. Provide 2 alternative versions in different tones.

Rules:
- Never commit to a deadline or promise the user did not state.
- If information is missing, leave a clearly marked placeholder.

Example:
Input: Client asking for a delayed deliverable + apology tone
Output: reply, 2 alternatives, subject line.

Creative skills worth keeping around

Three skills for naming, writing, and having fun with it.

27. Brand naming generator

Thirty names sorted by naming style, with the practical checks you should run before falling in love with one.

Skill name: Brand Naming Generator
Description: Generate business or product name ideas grouped by style, with domain and availability checks.

Instructions:
Input: What the business does + brand personality + target market + any words to avoid
Output: 30 names in 5 style groups + top 5 picks + domain tips + naming risks

Steps:
1. Extract 10 root words from the business description and its benefit.
2. Generate 30 names grouped as: real word, invented word, compound, short and punchy, and descriptive.
3. Keep names under 12 characters wherever possible.
4. Pick the top 5 and explain the fit in one line each.
5. Suggest domain variations to check and warn about hard-to-spell options.
6. Flag any name that sounds like an existing well-known brand.

Rules:
- Never claim a domain or trademark is available; tell the user to verify.
- Avoid random vowel-dropping that makes a name unreadable.

Example:
Input: AI tutoring for school students + friendly and modern + parents
Output: 30 grouped names, top 5, domain tips, risk flags.

28. Story prompt generator

The example from the original brief, expanded into a full framework you can start writing from immediately.

Skill name: Story Prompt Generator
Description: Generate creative writing inspiration with story premises, character backstories, and plot twists.

Instructions:
Input: Genre + setting (place and time) + character type + tone
Output: Story premise + character backstory + 3 plot twists + central conflict + 3 ending options

Steps:
1. Write a one-paragraph premise containing a want, an obstacle, and a cost.
2. Build the protagonist: background, flaw, secret, and what they want versus what they need.
3. Define the central conflict and name the force opposing the protagonist.
4. Offer 3 plot twists at increasing levels of boldness.
5. Offer 3 endings: hopeful, bittersweet, and dark.
6. Suggest the opening line of the story.

Rules:
- Never reuse the same twist structure twice in one response.
- Keep the premise specific; no generic chosen-one plots.

Example:
Input: Fantasy + medieval castle + young wizard + serious
Output: premise, backstory, 3 twists, conflict, 3 endings, opening line.

29. Roast and compliment generator

Light social content, with a tone dial so it stays funny rather than mean.

Skill name: Roast and Compliment Generator
Description: Write funny roasts or witty compliments about a job, hobby, or habit at a chosen intensity.

Instructions:
Input: Subject (job, hobby, or habit) + mode (roast or compliment) + tone (friendly, witty, or savage)
Output: 8 lines ready to share + the 2 strongest picks

Steps:
1. Find the 3 clichés everyone associates with the subject.
2. Write 8 lines built on those clichés, each under 20 words.
3. Aim jokes at the habit or role, never at appearance, identity, or anything a person cannot change.
4. Alternate between observational and exaggerated styles.
5. Mark the 2 strongest lines.
6. Offer a softer version of any line that lands too hard.

Rules:
- Never target a named private individual, protected group, or personal trait.
- Keep savage mode playful; if a line reads as genuinely cruel, rewrite it.

Example:
Input: Frontend developers + roast + witty
Output: 8 lines, 2 top picks, softer alternatives.

Which skills to build first

Building all 29 in one sitting is how a good idea becomes an unused folder. Build five, use them for a week, then add more.

Pick by frequency, not by excitement. The skill you will run twice a day beats the clever one you will run twice a year.

1. Concept explainer — the widest use of any skill here, for any subject at any level.
2. Email reply generator — smallest effort, fastest daily payback.
3. Error message debugger — removes the most frustrating minutes of a developer day.
4. Resume optimizer — highest impact per run when you need it.
5. LinkedIn post generator — keeps publishing consistent when motivation dips.
6. Email subject line optimizer — measurable improvement you can see in open rates.
7. Interview question generator — practice material that never runs out.
8. Task breakdown assistant — turns a stalled project into a first task.
9. Code explanation chatbot — makes unfamiliar codebases readable.
10. Goal breakdown planner — the one that makes the other nine get used.

Mistakes that make a skill useless

Most skills that get deleted were not badly written. They were badly scoped. These five mistakes cause almost every failure.

Writing a vague description

The description is a matcher, not a headline. Helps with writing matches everything and therefore triggers at the wrong moments. Writes LinkedIn posts from a topic or headline triggers exactly when it should.

Skipping the output format

If you do not state the output shape, you get a different shape every run, and the whole consistency benefit disappears. Always write the Output line, and be specific about counts and lengths.

Making one skill do four jobs

A skill that writes posts, captions, emails, and taglines will do all four averagely. Split it. Narrow skills produce sharper output and are far easier to fix later.

Leaving out the rules

The Rules block is where you prevent the failure you already know about: invented statistics, exact salary claims, emoji floods, made-up file paths. Every time an output disappoints you, add one rule and the mistake stops repeating.

Pasting an entire novel into the instructions

Long instructions cost more on every single run and often make outputs worse, not better. Keep the instruction body tight — input, output, steps, rules, one example. If you want to understand where that cost goes, read why Claude AI credits disappear fast.

A skill is finished when you can delete a line from it and the output gets worse. Until then, keep cutting.

How to improve a skill after you save it

1. Run it three times on real work, not on test topics.
2. Note the one thing you fixed by hand each time.
3. Add that fix to the skill as a numbered step or a rule.
4. Re-run and confirm the manual fix is no longer needed.

Three rounds of that loop is usually the difference between a skill you tolerate and one you rely on.

Final thoughts

Claude AI skills are not a shortcut to thinking. They are a way to stop re-explaining the same instructions to the same assistant every week, which is where most of the time actually goes.

Three things to take away. Start with five skills you will genuinely use daily rather than all 29. Write the input, the output, and the rules before the steps, because those three lines carry most of the quality. Improve each skill from real runs, not from imagined ones.

Copy any block above, paste it into the skill creator, and run it once today. Then tell us in the comments which of these Claude AI skills earned a permanent place in your workflow.