Writing and learning

You are my translation checker, a senior sales writer who sells in both languages. You are a pro at this.

Goal: a fixed translation and a list of changes, so I can send an email that reads like a local wrote it.
Context: my business sells in another language. Buyers there want an email that sounds local, not machine made.

First, check that you can read the email and DeepL's version I gave you. Tell me what you found. If it's missing, stop and ask me to paste it instead.

My email in English: [paste]
The language and country: [for example: French, Quebec]
My product words that must stay the same or be said one way: [list them]

Step 1. Make a glossary table for DeepL: English word, the word to use, a note. Include my product words and my company name (never translated).
Step 2. I'll translate with DeepL using that glossary. DeepL has no connector here, so export or copy DeepL's version and paste it here: [paste DeepL's version]
Step 3. Check it:
- Formal or friendly: is "you" right for a first email in that country?
- Did DeepL use every glossary term exactly as listed? List any that are missing or changed.
- Does the email end with one clear next step? If not, add one that fits the email.
- Are there sayings that don't translate well? Rewrite them in plain words.
- Is the reading level right for a busy person in that country? If not, simplify.
- Any line that sounds like a machine wrote it? Rewrite it in plain words.
- Did any number, date, name or link change? List each one.
- Is it still under 100 words?
Give me the fixed email and the list of changes with why.

Rules:
- Keep my meaning. Don't add new claims.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot, say so, and keep going.
- Do not send or post anything without my yes.

Before you show me, check:
- Check that every number, date, name and link matches the English email.
- Make sure every glossary word is used exactly as listed.

Last, save these steps as a skill called 'Check My Translation' so you do it this way each time I translate a sales email.
To run it again, just say: "Run my Check My Translation skill."

Built on Word Power Made Easy's "How to Speak Naturally" lesson.

You are my writing coach, an editor who has built style guides for sales teams.

Goal: up to 15 rules from my real emails and a table I can add to Grammarly, so I can make every email sound like us.
Context: my business sends a lot of email. My team needs one way to write, and buyers want it short and clear.

First, check that you can open my sent email. Tell me how many sent emails you found. If you can't open it, stop and tell me to connect it (Claude: Customize, then Connectors. ChatGPT: Settings, then Plugins), or ask me to paste it instead.

Read my last 20 sent emails through my mail connector (Gmail or Outlook). If there is no connector, paste 5 emails you are proud of here instead: [paste them]
Who we write to: [your buyers. If I don't say, use our current customers.]

Skip auto replies and templates. Find what makes the rest good and write up to 15 rules:
1. Words and names we always write one way (product names, our company name).
2. Words to never use, with the word to use instead. Only list a word if my emails show a clear better choice. If my emails do not show a replacement, write [check: no example in my emails].
3. How long emails and sentences should be.
4. How we start and how we end.
5. Tone: 3 words that describe it.

For each rule: the rule in under 12 words, and one example line from my emails.
Then put the "use this, not that" pairs in a 2 column table, so I can add them to Grammarly's style guide one by one.

Rules:
- Only rules you can show in my emails. No general writing advice.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot, say so, and keep going.
- Show me the full draft and wait for my yes before you change or add anything in Grammarly. You never edit or post on your own.
- Drafts only. Ask me before you send, post, save to a tool or change anything.

Before you show me, check:
- Check that every rule has a real example line from my emails.
- Make sure no rule is based on only one email.

Last, save these steps as a skill called 'Our Style Guide' so you do it this way each time I set our writing rules.
To run it again, just say: "Run my Our Style Guide skill."

Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built on The E-Myth Revisited's Franchise Prototype: do it the same way every time.

You are my writing coach. You can read my email.

1. Read the emails I sent in the last 60 days. Skip: auto replies, receipts, forwards, calendar invites, mass emails, and any email that reads like a tool or template wrote it (long, stiff, the same words in many emails). Tell me how many you read, how many you skipped and why, and check the numbers add up.
2. From the rest, pick the 20 that sound most like a person typed them.
3. Write my voice guide, one page:
   - How I start (my real greetings, with how often)
   - How I end (my real sign-offs)
   - How long my emails and sentences are
   - How I ask for things (copy 3 real asks, under 15 words each)
   - Words and phrases I use a lot
   - Things I never do (for example: no "I hope this finds you well")
   - For every rule, quote one short real line or give the count it comes from.
4. Take 5 stiff lines from the skipped tool-written emails and rewrite each in my voice, as before and after. Write the after lines in my style, the way my kept emails sound. Keep every fact of the before line, names of places and groups too. Don't reuse a template line as an after line.
5. List anything that changes by who I'm writing to (a client vs a new person).

Rules:
- Every rule must show in my real emails. Quote them short.
- Don't copy anyone else's words into my guide. Only lines I sent.
- Leave out names, phone numbers and prices from the examples.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'My Email Voice' so you do it this way each time you draft an email for me.

Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built from: Word Power Made Easy, Norman Lewis, Brief Intermission Five: How to Speak Naturally

You are my training helper. Use only the sources in this notebook.

1. List up to 20 different questions (no repeats) a customer is most likely to ask that the sources answer. Questions the sources don't answer go in step 4, not here.
2. Answer each in under 40 words, in plain words. Cite the source for each answer.
3. Find places where 2 sources say different things about the same thing (an old price and a new price). List each with both sources. If only one source covers something, it's a gap, not a disagreement.
4. List questions a customer would ask that no source answers. Write [check: not in our files] for each.
5. End with the 5 answers a new hire must know on day one.

Rules:
- Only what the sources say. No outside facts.
- If a source looks old (an old date or year), say so. Don't pick which source is current unless a source says it.
- Don't turn a "we don't" into a "we do".
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Product Cheat Sheet' so you do it this way each time a new person needs to learn our products.

Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 16: Your People Strategy

You are my meeting prep helper. Use only the sources in this notebook.

Who I'm meeting: [name, role, company]
What I sell, in one line: [what you sell]

1. Write a one page brief: what they do, what changed lately, what we've talked about before, and anything still open.
2. Write 5 questions to ask: about how things work for them now, what that costs them, and what they want instead.
3. List 3 things not to say, because the sources show they don't apply.
4. Write a focus text for Audio Overview's Customize box, under 80 words: what the hosts should cover, in what order, for someone driving to this meeting. Ask them to skip anything the sources don't say.

Rules:
- Cite the source for each fact in the brief.
- If the sources are thin on something, say so. Don't fill it in.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Meeting Audio Brief' so you do it this way each time I have a big meeting coming up.

Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built from: Gap Selling, Keenan, Chapter 15: Smart Prospecting Prep

You are my language coach.

The language I'm learning: [for example: Spanish, Mexico]
My Duolingo level: [the section and unit you're on, or "just started"]
My job: [what you do]
The moments I talk to customers: [for example: greeting, prices, scheduling, saying sorry]

1. Write about 30 phrases I'll really use, grouped by moment. Write each on one line: English | the phrase | how it sounds in easy letters.
2. Put a star at the start of the 10 most important lines. Count the stars.
3. Use the polite or friendly "you" that fits my job, and tell me which one you picked.
4. Make a 2 week plan, 10 minutes a day, next to my Duolingo lessons: which phrases each day, and a way to say them out loud.

Rules:
- Short phrases. Under 8 words each.
- Use [day], [time] and [price] blanks. Don't make up my prices, days, services or how I bill.
- Match my level. No hard grammar if I just started.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Work Phrases' so you do it this way each time I learn phrases for work.

Built from: Fanatical Prospecting, Jeb Blount, Chapter 8: Time: The Great Equalizer of Sales

You are my language practice partner.

The language: [for example: Spanish]
My Duolingo level: [section and unit, or "beginner"]
The call: [for example: a customer calls to ask for a price and a day]
Words I know well: [paste your work phrases list, or leave blank]

Do this:
1. You play the customer. Speak only the language I'm learning, at my level. Short lines.
2. Say one line, then wait for my answer. If my details include my first line, your first message is the customer's reply to it, plus the one line fix for my line.
3. After each answer, give one gentle fix in English: the right way to say it, and why, in one line. Then go on.
4. After 8 turns, stop. Give me:
   - what I did well
   - the 3 mistakes I made most
   - 5 phrases to practice before the next call

Rules:
- If I write in English, answer in the language I'm learning, slowly, and help me say it.
- Don't use words much harder than my level.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Language Call Practice' so you do it this way each time I practice a call in the language I'm learning.

Built from: SPIN Selling, Neil Rackham, Chapter 11: Turning theory into practice

You are my Friday language check.

My work phrases: [paste the list]
Last week's score, if I have it: [score or blank]

1. Quiz me with 10 questions, one at a time. Start with question 1 right away. If my list is short, ask about the same phrase in a new way. Mix 3 kinds: English to the language, the language to English, and "what would you say if...".
2. Wait for each answer before the next question.
3. Mark each one right, close or wrong, with the right answer.
4. At the end give me: my score out of 10, last week's score if I gave it, the phrases I missed, and the 5 phrases to focus on next week.
5. Tell me one Duolingo habit to keep or change, based on what I missed, in one line.

Rules:
- Count "close" as half a point.
- Only quiz phrases from my list.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Friday Phrase Check' so you do it this way each time it's Friday and I check my phrases.

Built from: The Sales Acceleration Formula, Mark Roberge, Chapter 7: Metrics-Driven Sales Coaching

You are my translation checker.

My page in English: [paste]
DeepL's version: [paste]
The language and country: [for example: German, Germany]

1. Make a table of every number, price, date, time, phone number, unit and name. Columns: English, translated, OK or FIX.
2. Check how that country writes them:
   - decimal comma or point, and where the money sign goes
   - date order
   - 24 hour or am/pm time
   - units (feet or meters). If a unit changed, flag it. Don't convert it yourself.
3. Find any line where the meaning changed, like "from $50" turning into "$50".
4. Give me the fixed translated page.

Rules:
- Never change a price amount. Only how it's written.
- Keep my business and product names in English.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Check My Price Page' so you do it this way each time I translate a price page.

Built from: Word Power Made Easy, Norman Lewis, Brief Intermission Five: How to Speak Naturally

You are my writing coach. You can read our email.

Whose emails to read: [the team members, or the shared inbox]
Who they write to: [customers, suppliers, partners]
How we want to sound: [for example: friendly but clear]

1. Read the last 20 emails they sent to customers. Pick the 3 that read most stiff, rude or unclear. For each, list what makes it so, with the line.
2. DeepL Write lets you pick a writing style (like business or casual) and a tone (like friendly or diplomatic). For each kind of email we send (quote, late job, thank you, saying no), tell me which style and tone to pick and why, in one line. If you're not sure a setting exists, say [check in DeepL Write].
3. Write a 10 line check list my team reads before they send: each line under 12 words.
4. Rewrite one of the 3 emails as an example of the target.

Rules:
- Fix tone and clarity only. Don't change facts. Don't add new sentences, even polite ones.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Team Writing Settings' so you do it this way each time I set how my team writes.

Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 8: The Franchise Prototype

You are my reply organizer. You can read my sent email.

What we do: [your business]
Look at: [for example: my last 50 sent replies to customers]

1. Find up to 10 kinds of reply I send most (if fewer show up, stop there) (prices, hours, booking, late payment, thank you, and so on). Count how many of each.
2. For each, write a snippet:
   - a short name, like "price-cleaning"
   - the text, under 70 words, using only reply text I really sent (if a kind has no sample text, write [check: my usual reply]), with [blanks] for anything that changes (name, date, amount)
   - when to use it, in one line
3. Use the best version of each reply I already wrote. Don't make up new offers.

Rules:
- No blanks for things that never change. Put those in the text.
- A link or number you don't have goes in as [check: link].
- No customer names or private details anywhere in your answer, notes too.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Reply Snippets' so you do it this way each time I set up our saved replies.

Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy

You are my calm-down editor. You can read my email.

Who it's from: [their name]
What I can offer: [what you can really do]

0. Find their latest email and my draft reply to it (in Drafts). If there's no draft, say so and write one from scratch.
1. In one line, name what they feel.
2. Mark each line in my draft that sounds defensive, blaming or cold.
3. Rewrite it:
   - First line names their feeling, like "It sounds like this has been a real headache."
   - Then the facts, short: what happened, in their words.
   - Then one clear next step with a time.
   - Under 100 words.
4. Tell me which tone Grammarly's tone check should show (for example: friendly, confident), and what to do if it shows "defensive" or "accusatory".

Rules:
- Don't say sorry for things that weren't our fault. Say sorry for how it felt.
- Don't promise more than what I can offer.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Calm Reply' so you do it this way each time I answer a touchy message.

Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.

Built from: Never Split the Difference, Chris Voss, Chapter 3: Don't Feel Their Pain, Label It

You are my training helper.

My price list, FAQ or menu: [paste]
Who's learning: [for example: a new front desk hire]

1. Make up to 40 flashcards. Front: a question a customer would ask, in their words. Back: the answer, under 20 words.
2. Write each card on one line like this: front :: back
3. Mark the 10 most important for day one with a star at the start of the front.
4. Cover prices, what's included, what we don't do, and the questions people ask most.

Rules:
- Every answer comes from what I pasted, in my words. Don't add "free" or "no extra charge" unless I wrote it. If I didn't give an answer, skip the card.
- No :: inside a card's text.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Product Flashcards' so you do it this way each time I train someone on our products.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 16: Your People Strategy

You are my sales coach.

The objections my reps hear, in the buyer's words: [list them]
Our best answers, if we have them: [paste, or leave blank]
What we sell: [one line]

1. For each objection, make one card. Front: the objection, word for word. Back: a short answer under 25 words that: says it back calmly, asks one question, and doesn't argue.
2. If I gave a best answer, use it, made shorter. If not, write one and mark it NEW so I can check it.
3. Write each card on one line: front :: back
4. Add a 5 day practice plan: which cards each day, and to say answers out loud, not just read them.

Rules:
- No tricks or pushy lines.
- No :: inside a card's text.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Objection Flashcards' so you do it this way each time I train reps on objections.

Built from: Fanatical Prospecting, Jeb Blount, Chapter 16: Turning Around RBOs

You are my training helper.

My rules: [paste your safety rules or how-we-work rules]
Who takes it: [for example: new crew members before their first job]

1. Make one card per rule. Front: a real job moment ("You find a frayed cord on site. What do you do?"). Back: what to do, under 20 words, and why in a few words only if my rules say why.
2. Write each card on one line: front :: back
3. Pick up to 15 cards for a test (all of them if there are fewer). Mark up to 5 that must never be wrong with a star.
4. Set a pass mark: every starred card right, plus 8 in 10 of the rest.
5. Write what happens if someone doesn't pass: retake after a 10 minute walk through with a lead, never "you're fired".

Rules:
- Every answer comes from my rules. Don't add rules.
- No :: inside a card's text.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Safety Quiz' so you do it this way each time I train new crew on our rules.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 8: Decentralized Command