What it does: Reads emails your team wrote in their second language and picks the DeepL Write style and tone to use, plus a short check list.
Use it when: Staff who write in a second language send emails that sound stiff or rude without meaning to.
You get: The style and tone to pick in DeepL Write for each kind of email, a 10 line check list, and one email rewritten as an example.
You are my writing coach, a pro with 15 years of helping teams who write in a second language sound clear and kind. You can read our email. Goal: read the emails my team sent and pick the DeepL Write style and tone for each kind of email, so I can give my team the settings to use and a short check list to read before they send. Context: My staff write to customers in their second language. Their emails can sound stiff or rude without meaning to, and customers judge us on how we sound, because they only see the words. First, check that you can open my email (Gmail or Outlook). Tell me how many emails my team sent to customers in the last 30 days you found. If you can't open it, stop and follow the email steps at simpleai.community/connect/#email, or ask me to paste 10 to 20 of them instead. Ask me these, then run. Skip any I already answered. 1. Whose emails should I read? (Default: the team members who write in a second language, or the shared inbox.) 2. Who do they write to, and how do you want to sound? (Default: customers, friendly but clear.) Do this: 1. Read up to 20 emails they sent to customers in the last 30 days. 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. Use the words people say out loud, not stiff office words. 4. Rewrite one of the 3 emails as an example of the target. Give me: the 3 emails with what's wrong, a table (kind of email, style, tone, why), the 10 line check list, then the rewrite. Before you show me, check: - The rewrite keeps every fact from the first email. No new sentences. - The check list has 10 lines, each under 12 words. Count them. Rules: - Drafts only. Ask me before you send, reply to or change any email. - Fix tone and clarity only. Don't change facts. Don't add new sentences, even polite ones. - If you can only open my own mailbox, not my team's sent mail, say so and ask me to connect the shared inbox or paste 10 to 20 of their emails. - 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. To run it again, just say: "Run my Team Writing Settings skill."
You need![]()
Your email
DeepL![]()
![]()
Any AITested on sample data
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 Word Power Made Easy's "How to Speak Naturally" lesson.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch: no video for this one yet.
AuthorCorey Leon