The Baker's Dozen · Cultivated AI · Lab 03
A skill is a method you save once and reuse forever: your best way of doing one repeatable task, written down so the AI does it your way every time. In Session 2 everyone writes one with Claude's skill creator, installs it, and runs it on real work. Pick the card closest to your week, or bring your own.
One idea for every corner of the company, matched to the worlds from the questionnaire. Each one is a task somebody at the company already does every week by hand. The test of a task worth saving: you do it at least weekly, and you already have one finished example that shows what good looks like.
🥐 Kitchen & production
Turns how you actually do it into a document anyone can follow.
Feed itA voice-note transcript or rough steps for one kitchen process.
Get backA clean numbered SOP with quantities, timings and the checks that matter.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief.
# SOP writer
Skill name: sop-writer
## When to use it
Whenever I hand you rough notes, a voice-note transcript or a list of steps for one kitchen or shop process and want a document a new hire can follow.
A plain request that should wake it up: "turn these notes into an SOP".
## What I will paste in each time
A voice-note transcript or rough steps for one kitchen process.
## What I want back
A clean numbered SOP with quantities, timings and the checks that matter.
## My method, in order
1. Read everything first, then list the steps in the order they actually happen, one action per step.
2. For each step keep the quantity, time, temperature or setting exactly as I gave it. Where a step needs a check, add one: what it should look, feel or sound like.
3. Put a short "Before you start" list at the top: equipment, ingredients, anything to pre-heat or pre-weigh.
4. Add a "Common mistakes" list at the end, only from things I mentioned.
5. Finish with "Questions for the owner": anything missing or unclear, as a numbered list.
## Rules
- Never invent a quantity, time or temperature. If it is missing, ask in the questions list.
- Keep my units and my names for things (maida, not all-purpose flour).
- Plain words a first-week hire understands. No paragraph longer than two sentences.
- More than twelve steps: split into stages with a heading each.
- Title format: "SOP: {process name}", then who it is for and how long it takes.
## A stand-in example
Input: a voice note about the 5am croissant dough: "500 flour, 10 salt, 55 sugar, 10 yeast, 300 cold milk from the walk-in, mix on speed 1 for 4 min then speed 2 for 6, dough should be smooth and pull off the bowl, rest 1 hour covered."
Output: "SOP: Croissant dough, first mix", a Before you start list (scale, spiral mixer, milk from the walk-in), five numbered steps with the check "dough pulls cleanly off the sides of the bowl", one common mistake (warm milk), and one question (which flour brand).
This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct.
## How to build it
- Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most.
- Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it sop-writer, lowercase with hyphens.
- Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute.
- Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output.
- Package it: put SKILL.md inside a folder named sop-writer, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run.
## Important
I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice. 📦 Operations & supply
Follow-ups that get firmer each round without burning the relationship.
Feed itThe vendor, what's pending, and how many times you've already asked.
Get backA follow-up message in your voice, matched to the round you're on.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Vendor chaser Skill name: vendor-chaser ## When to use it Whenever I tell you a vendor has something pending and I need the next follow-up message. A plain request that should wake it up: "chase Gupta Mills for the maida, third time". ## What I will paste in each time The vendor, what's pending, and how many times you've already asked. ## What I want back A follow-up message in your voice, matched to the round you're on. ## My method, in order 1. Ask for anything missing: what exactly is pending, the promised date, which round this is (first, second, third or later), and how long we have worked with them. 2. Match the tone to the round. First: friendly reminder. Second: firm, with the date and the effect on us. Third or later: formal, and says what we will do next. 3. Always name the exact item, the quantity and the date that was promised. 4. End with one clear ask: a new date, or a call today. 5. Give me the message ready to paste into WhatsApp, then one line on what to do if there is no reply in 24 hours. ## Rules - Under 80 words. This is WhatsApp, not a letter. - Warm and direct. No sarcasm, no threats, never mention legal action. - Mention sourcing from someone else only when I say we are ready to. - Sign off with my name and "The Baker's Dozen". - Hindi or Gujarati phrases are fine when I use them in the input. ## A stand-in example Input: "Prime Packaging, 200 one-kg cake boxes promised for Monday, now Thursday, second time asking, contact is Sunil, we have used them for three years." Output: a four-line message to Sunil: the 200 boxes promised Monday, weekend orders start Friday and we are short, can they reach us by Friday morning, please confirm today. Sign-off. Then: if no reply by tomorrow noon, call him, and ask the second supplier for a quote. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it vendor-chaser, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named vendor-chaser, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
🛵 Marketplace
Replies in brand voice, and it knows what not to answer.
Feed itA batch of customer reviews pasted straight from the platform.
Get backA reply for each, with the ones needing a real human decision flagged instead of answered.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief.
# Review responder
Skill name: review-responder
## When to use it
Whenever I paste customer reviews from Zomato, Swiggy, Google or Instagram and want replies.
A plain request that should wake it up: "reply to these reviews".
## What I will paste in each time
A batch of customer reviews pasted straight from the platform.
## What I want back
A reply for each, with the ones needing a real human decision flagged instead of answered.
## My method, in order
1. Read all the reviews first. Sort them into three piles: praise, complaints we can answer, and ones that need a human decision.
2. Praise: thank them, name one specific thing they mentioned, invite them back. Two sentences.
3. Complaints: apologise once, say plainly what we will do, and take it private ("please message us your order number"). Three sentences.
4. Third pile: do not write a reply. Write "NEEDS A HUMAN" and one line on why.
5. Return the replies in the same order as the reviews, each under its review.
## Rules
- Never promise a refund, replacement, discount or compensation. Only a human can.
- Never argue, never explain what the customer did wrong.
- Flag as NEEDS A HUMAN: anything about health or safety, a named staff member, a legal threat, a review that looks fake, or anything I would want to know about.
- Under 50 words per reply. Warm and plain. At most one exclamation mark.
- Use the customer's name if it is shown.
## A stand-in example
Input: three reviews. Five stars about the almond croissant. Two stars, "cake arrived late and the cream was melted". One star, "found hair in the bread, disgusting, reporting you".
Output: reply one thanks them and mentions the almond croissant. Reply two apologises, says we are checking the delivery with the partner, and asks for the order number by message. The third is "NEEDS A HUMAN: food safety complaint, likely to escalate".
This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct.
## How to build it
- Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most.
- Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it review-responder, lowercase with hyphens.
- Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute.
- Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output.
- Package it: put SKILL.md inside a folder named review-responder, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run.
## Important
I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice. 📣 Marketing & content
Your brand voice, saved once, applied every time.
Feed itWhat the product is, the occasion, and one line about the photo.
Get backThree caption options with hashtags, sized for each platform.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Caption machine Skill name: caption-machine ## When to use it Whenever I tell you what we are posting and want captions. A plain request that should wake it up: "captions for the Diwali box photo". ## What I will paste in each time What the product is, the occasion, and one line about the photo. ## What I want back Three caption options with hashtags, sized for each platform. ## My method, in order 1. Ask for the three things if they are missing: the product, the occasion, and one line about the photo. 2. Write three options with different angles: one about the product, one about the moment or the person eating it, one short and playful. 3. Size each option for the platform I name. Instagram: the first 125 characters must work on their own. WhatsApp status: two lines. X: under 280 characters. 4. Add hashtags from my saved set: five to ten for Instagram, none for WhatsApp. 5. Add a call to action only if I give an order link or a date. ## Rules - Our voice: warm, plain, a little playful. Sounds like a person at the counter. - Never use: indulge, delectable, elevate, decadent, treat yourself, foodie. - Never invent a price, an ingredient, or a claim like eggless or sugar-free unless I say it. - Up to two emoji, never more. - One of the three options must be under 60 characters. ## A stand-in example Input: "Product: Diwali gift box, twelve assorted cookies. Occasion: pre-orders open. Photo: box open on a marble counter, morning light. Instagram." Output: three captions. The second is built around gifting the person who always brings the sweets. The third is "Twelve cookies. Zero sharing required." Then the hashtag set and one line about pre-orders. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it caption-machine, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named caption-machine, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
📈 Trade
From order details to a client-ready quote in one pass.
Feed itThe buyer, products, quantities and any special terms.
Get backA formatted quote, plus the follow-up message to send three days later.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Quote writer Skill name: quote-writer ## When to use it Whenever I give you an enquiry with products and quantities and want a quote. A plain request that should wake it up: "quote for the Mehta wedding order". ## What I will paste in each time The buyer, products, quantities and any special terms. ## What I want back A formatted quote, plus the follow-up message to send three days later. ## My method, in order 1. Ask for anything missing: buyer name, delivery date, products, quantities, and any special terms. 2. Use my price list. If a product is not on it, ask. Do not guess a price. 3. Lay out the quote: greeting, one line per item with quantity, rate and line total, subtotal, discount if any, GST, grand total, delivery date, payment terms, validity. 4. Then write the follow-up message for three days later: short, friendly, one question. 5. Give me both, ready to paste. ## Rules - Rupees with Indian commas (₹1,20,000). GST on its own line at the rate I give, default 5%. - Payment terms unless I say otherwise: 50% advance on confirmation, balance before dispatch. - Quote valid for 7 days. - No discount unless I state one. - Sign off with my name and "The Baker's Dozen". ## A stand-in example Input: "Mehta family, 200 butter croissants at ₹45, 4 kg cookies at ₹900 a kg, delivery 14 September, they asked for 10% off, say yes." Output: a quote with two item lines, subtotal ₹12,600, discount ₹1,260, GST at 5% on ₹11,340, grand total ₹11,907, the delivery and payment lines, valid until the date. Then a follow-up for three days later asking whether to block the date. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it quote-writer, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named quote-writer, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
🧾 Finance & accounts
Messy lists in, books-ready tables out.
Feed itA pasted block of expenses or bank entries.
Get backA categorised table with GST split out and anything odd flagged for a second look.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Expense untangler Skill name: expense-untangler ## When to use it Whenever I paste a block of expenses, bills or bank entries and want them sorted for the books. A plain request that should wake it up: "sort these expenses". ## What I will paste in each time A pasted block of expenses or bank entries. ## What I want back A categorised table with GST split out and anything odd flagged for a second look. ## My method, in order 1. Read every line. Pull out the date, the vendor, the amount, and any GST mentioned. 2. Put each entry in one category from my list: ingredients, packaging, salaries, rent, utilities, marketing, delivery, equipment, repairs, other. 3. Split GST out where the entry shows it. Leave it blank where it does not. 4. Return a table with columns: date, vendor, amount, GST, category, note. Then a second list: rows I should look at twice, with the reason. 5. Offer the table tab-separated so I can paste it straight into Sheets. ## Rules - Never change an amount or a date. Never drop a row. If a row is unreadable, keep it with "unclear" in the note. - Flag for a second look: duplicates, any round-number amount over ₹10,000, a vendor I have not seen before, and anything with no date. - Guessing a category is fine. Write "guess" in the note when you do. - Dates as DD/MM/YYYY. ## A stand-in example Input: five lines from the WhatsApp expense log: maida from Gupta Mills ₹18,000 with GST, a Swiggy payout adjustment, a ₹25,000 cash entry with no vendor, and two identical ₹1,200 gas cylinder entries on the same day. Output: a six-column table, with the ₹25,000 row and the twin gas entries listed under "look at twice". This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it expense-untangler, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named expense-untangler, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
🤝 People & admin
One role description becomes the whole hiring toolkit.
Feed itThe role, and the three things the person must be able to do.
Get backA job post, interview questions that test those exact things, and a simple scorecard.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Hiring kit Skill name: hiring-kit ## When to use it Whenever I describe a role I need to hire for. A plain request that should wake it up: "hiring kit for a counter salesperson". ## What I will paste in each time The role, and the three things the person must be able to do. ## What I want back A job post, interview questions that test those exact things, and a simple scorecard. ## My method, in order 1. Ask for the role, the three things the person must be able to do, the hours, and the pay range if I want it shown. 2. Write the job post: under 200 words, plain language, what the day looks like, the three must-dos, how to apply. 3. Write six interview questions. Each one tests one of the must-dos, and each comes with "a good answer sounds like". 4. Add one practical task they can do in the interview. 5. Write a scorecard: the three must-dos plus attitude, each rated 1 to 4, with a line on what a 4 looks like. ## Rules - Never ask about age, marriage, children, religion or caste, in the post or the questions. - No jargon. No "rockstar", no "fast-paced environment". - If I give a pay range, the post shows it. If not, leave the line out rather than write "competitive". - Everything in one document I can print. ## A stand-in example Input: "Counter salesperson, morning shift 7 to 3. Must: handle cash and UPI without mistakes, remember regulars and their usual orders, keep the display full and clean." Output: a short post, six questions including "a customer says they paid but the UPI has not shown up, what do you do", a practical task (arrange a tray from a photo), and the scorecard. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it hiring-kit, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named hiring-kit, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
🎨 Design & creative
Turns "make it pop, need it Friday" into a brief you can work from.
Feed itThe vague request exactly as it arrived.
Get backA proper brief with sizes, formats and deadline, plus the questions to send back.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Brief translator Skill name: brief-translator ## When to use it Whenever someone sends me a vague design request and I need a brief before I start. A plain request that should wake it up: "turn this into a brief". ## What I will paste in each time The vague request exactly as it arrived. ## What I want back A proper brief with sizes, formats and deadline, plus the questions to send back. ## My method, in order 1. Take the request as it arrived. Pull out what is actually being asked: the piece, the audience, the deadline, anything about tone. 2. Fill the gaps with my defaults for our usual outputs, and mark each one "assumed". 3. Write the brief: what it is, who it is for, sizes and formats, copy needed, deadline, who signs off. 4. List up to five questions to send back, only the ones that change the work. 5. Do not start designing. ## Rules - My defaults, to confirm with me the first time: Instagram post 1080×1350, story 1080×1920, WhatsApp forward 1080×1080, menu card A4, box label 100×100 mm, all as PNG plus the editable file. - Every assumption is labelled so it can be corrected. - The deadline in the brief is one day before the one they gave. - The brief fits on one page. ## A stand-in example Input: "Hey can you make something for the Diwali boxes for insta and also print, make it pop, need by Friday." Output: a brief with two pieces (an Instagram post and story, and an A5 print insert), assumed sizes, copy needed from marketing, deadline Thursday, and three questions: price shown or not, which box variants, and whether "print" means the insert or a poster. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it brief-translator, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named brief-translator, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
💻 MIS
The cleanup you repeat every week, done your way automatically.
Feed itA pasted block of messy spreadsheet data.
Get backCleaned rows in consistent formats, with duplicates and oddities listed separately so nothing vanishes silently.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Data cleaner Skill name: data-cleaner ## When to use it Whenever I paste messy rows from a sheet and want them clean. A plain request that should wake it up: "clean this list". ## What I will paste in each time A pasted block of messy spreadsheet data. ## What I want back Cleaned rows in consistent formats, with duplicates and oddities listed separately so nothing vanishes silently. ## My method, in order 1. Look at the columns first and tell me what each one seems to be. 2. Standardise the formats: dates DD/MM/YYYY, phone numbers ten digits with no spaces, names in Title Case, amounts as plain numbers, cities spelled one way. 3. Trim spaces and fix obvious typos in repeated values (Ahmedabad spelled four ways becomes one). 4. Return the cleaned rows in the original order, tab-separated for Sheets. 5. Then a second list: duplicates and rows I should look at, with the reason. ## Rules - Never delete a row. Never merge two rows. Duplicates go in the second list, not in the bin. - Never change a value you are not sure about. Put it in the second list instead. - Report at the end: how many rows in, how many changes, and of what kind. - Keep my column order and my headers. ## A stand-in example Input: twelve customer rows with dates in three formats, phone numbers with +91 and spaces, "ahmedabad", "Ahmedabad" and "AHMEDABAD", and two rows for the same person. Output: twelve cleaned rows, the pair flagged as a likely duplicate, and a report: 12 in, 19 changes (dates 8, phones 6, cities 5). This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it data-cleaner, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named data-cleaner, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
⚖️ Legal
Every agreement read the same careful way.
Feed itA contract or terms document.
Get backA plain-language summary, every date and deadline in a table, and the clauses worth a lawyer's eyes flagged.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Contract summariser Skill name: contract-summariser ## When to use it Whenever I paste a contract, an agreement or platform terms and want to know what I am agreeing to. A plain request that should wake it up: "summarise this agreement". ## What I will paste in each time A contract or terms document. ## What I want back A plain-language summary, every date and deadline in a table, and the clauses worth a lawyer's eyes flagged. ## My method, in order 1. Read the whole document before writing anything. 2. A plain-language summary in under 150 words: who, what, for how long, what we pay or get paid, how it ends. 3. A table of every date, deadline and notice period. 4. Flags: auto-renewal, exclusivity, penalties, indemnity, who can end it and how, jurisdiction, anything one-sided. Quote the clause under each flag. 5. A short list of what is missing that I would expect to see. ## Rules - Quote, do not paraphrase, in the flags section. - Never say a clause is fine or unfair. Say what it does, and "worth a lawyer's eyes" where it matters. - Never advise whether to sign. - If the document looks cut off, say so at the top. ## A stand-in example Input: a nine-page marketplace partner agreement. Output: the summary; a table with the start date, the 30-day termination notice and the weekly payout cycle; flags for automatic renewal and for a clause letting the platform change commission with 15 days' notice, each quoted; and a note that there is no clause about damaged deliveries. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it contract-summariser, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named contract-summariser, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
🧭 Founding & leadership
Every meeting ends with clear owners and dates.
Feed itRough meeting notes or a transcript.
Get backMinutes with decisions, owners and deadlines, plus a drafted follow-up for each owner.
I want to make a custom skill for claude.ai. Use the skill creator and build it with me. Here is my brief. # Minutes machine Skill name: minutes-machine ## When to use it Whenever I paste rough meeting notes or a transcript and want minutes. A plain request that should wake it up: "minutes from this". ## What I will paste in each time Rough meeting notes or a transcript. ## What I want back Minutes with decisions, owners and deadlines, plus a drafted follow-up for each owner. ## My method, in order 1. Separate what was decided from what was discussed. 2. List the decisions first, one line each. 3. Then the actions: what, who, by when. If an owner or a date is missing, write "owner TBD" or "date TBD" and put it in a questions list. 4. Then a short "discussed, not decided" list. 5. Then a follow-up message for each owner, under 60 words, in my voice, ready to paste into WhatsApp. ## Rules - Never add a decision that is not in the notes. Never soften a decision that was made. - Use people's names exactly as I wrote them. - The whole thing fits on one screen. - Ask me for anything missing at the end, not in the middle. ## A stand-in example Input: rough notes from the Monday production meeting: Diwali box pricing to be finalised by Vishal on Thursday, Sneh to get quotes for 2,000 boxes, a discussion about a second counter person with no decision, Keyur mentioned the oven service is due. Output: two decisions, three actions (the oven service with "date TBD"), one discussed-not-decided item, and three follow-up messages. This example is a stand-in. Before you write the skill, ask me for one real finished example: an input I actually had and the output I was happy with. Use mine instead of this one. If I do not have one to hand, ask me three questions and draft one for me to correct. ## How to build it - Interview me first. Ask about anything above that is unclear or missing, one question at a time, five at most. - Then write the skill: a SKILL.md whose description, under 200 characters, says exactly when to use it and with the words I actually use, so Claude picks it up from a plain request like the one above without me naming the skill. Name it minutes-machine, lowercase with hyphens. - Put my method, my rules and the example inside it. Plain language, no jargon. Short enough to read in a minute. - Test it once on the example and show me the output before we finish. If the output breaks a rule, fix the skill, not the output. - Package it: put SKILL.md inside a folder named minutes-machine, zip that folder, and give me the zip to download. End with the exact steps to install it in claude.ai (Customize, Skills, the plus button, Create skill, upload the zip) and a one-line test I can run. ## Important I am not a developer. This skill is for me and my teammates at a bakery business. Keep everything in plain language and in my voice.
Copy any card's prompt and replace the When, Feed, Get back, Method and Rules sections with your own task. Keep the last two sections: they are what make Claude build and package it properly.
Custom skills need a paid Claude plan (Pro, Max or Team) and one setting switched on. Five steps from a pasted brief to a zip in your downloads.
On claude.ai open Settings, then Capabilities, and turn on "Code execution and file creation". Skills run inside it. On a Team plan the admin may have done this already.
Open Customize, then Skills. Anthropic's own skills are listed there; make sure Skill creator is switched on. If you cannot see it, carry on: the prompt asks Claude the same questions.
Claude interviews you: a few questions, one at a time, and it will ask for a real finished example. Answer in your own words, and paste a real input with the output you were happy with.
Claude runs the skill once on your example and shows the output. Anything that breaks a rule gets fixed in the skill, not in the output. Say what is wrong and let it revise.
When you are happy, Claude gives you a zip named after the skill. Inside it is one folder with SKILL.md at the top. Save it somewhere you will find again.
One upload, then it is on for every chat. You never have to name it: Claude reads the description and reaches for the skill when your request matches.
The same page as step B. Older layouts call it Settings, Capabilities, Skills.
Then upload the zip you downloaded.
Your skill appears in the list with its description. Make sure it is switched on.
Start a new chat. Do not name the skill. Type the request the way you would to a colleague, then paste this week's input. Claude should reach for the skill on its own.
Open the zip's SKILL.md and read the description line. It must say plainly when to use it, with the words you actually use. Ask Claude to rewrite it pushier, re-zip, upload again.
Send the zip to a teammate; they upload it the same way. On a Team plan the workspace owner can add it for everyone from the admin settings, which is how the shared skills folder becomes real.
Three passes in thirty minutes is a good result. A skill that has not been run on real work is a guess.