What it does: Reads your sent emails and writes the rules your team's writing should follow, ready to add to Grammarly's style guide.
Use it when: Everyone on your team writes emails a different way.
You get: Up to 15 short rules (words to use, words to skip, length, tone), each with an example from your emails.
Open in
See the prompt
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.
What it does: Finds the replies you type over and over and writes them as short snippets your team can add to Grammarly.
Use it when: Your team types the same answers to customers every day, a little different each time.
You get: 10 snippets with a short name, the text with blanks to fill, and when to use each.
Open in
See the prompt
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
What it does: Reads the angry message and your draft, takes the heat out of your reply, then tells you what to check in Grammarly's tone check.
Use it when: A customer or partner sent something sharp and your reply sounds defensive.
You get: A calm rewrite that names their feeling, keeps your facts, and gives one clear next step.
Open in
See the prompt
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