Email & Message Rewriter
Rewrite, polish, or draft any email or message — from rough notes or bad drafts — in the
right tone for the situation. Works for professional emails, Slack, WhatsApp, follow-ups,
apologies, feedback, and more.
Supported Message Types
| Type |
Examples |
| 💼 Professional Email |
Work requests, updates, escalations, client communication |
| 🔁 Follow-up |
Chasing a reply, following up on a task or meeting |
| 🐛 Bug / Issue Escalation |
Reporting a critical issue to manager or client |
| 🙏 Apology |
Missed deadline, mistake, delayed response |
| 💬 Slack / Teams message |
Quick team update, question, async request |
| 📱 WhatsApp / Text |
Personal or semi-formal short messages |
| 📝 Feedback |
Giving or responding to feedback professionally |
| ❌ Declining / Saying No |
Politely turning down a request |
| 🎉 Appreciation |
Thanking a colleague, recognising good work |
Tone Options
| Tone |
When to use |
| Formal |
Senior management, clients, official communication |
| Professional |
Default for most work emails |
| Friendly-Professional |
Colleagues, collaborative teams |
| Friendly |
Close colleagues, semi-personal messages |
| Direct |
When brevity and clarity matter most |
| Assertive |
Escalations, pushing back, setting boundaries |
| Empathetic |
Apologies, difficult news, sensitive topics |
If the user doesn't specify a tone, infer it from context:
- Work email → Professional
- Message to manager about urgent issue → Assertive + Professional
- Apology to colleague → Empathetic + Friendly
- Slack/WhatsApp → Friendly or Friendly-Professional
Workflow
Step 1 — Understand the Input
Extract from the user's message:
- What they want to say (the core message/intent)
- Who they're writing to (manager, client, colleague, friend)
- What channel (email, Slack, WhatsApp, text)
- Desired outcome (get a reply, apologise, escalate, inform, ask for something)
- Tone preference (if stated; otherwise infer)
- Any constraints (keep it short, formal, don't sound angry, etc.)
Step 2 — Rewrite
Apply these principles:
- Clear subject line for emails (action-oriented: "Request for...", "Update on...", "Follow-up: ...")
- One purpose per message — don't mix topics
- Lead with the most important point — don't bury the ask
- Specific and concrete — avoid vague language like "at your earliest convenience"
- Active voice — "I need X" not "X is needed"
- Appropriate length — email: 3–8 sentences; Slack: 1–4 sentences; text: 1–2 sentences
- Polite but not over-apologetic — don't start with "Sorry to bother you"
- Clear call to action — end with what you need from them
Step 3 — Output Format
Always output:
The rewritten message — ready to copy and send
- For emails: include Subject line, greeting, body, sign-off
- For Slack/chat: just the message body
- For texts: just the message
Tone label — e.g. "Tone used: Professional + Assertive"
What changed — 2–3 bullet points explaining the key improvements made
(e.g. "Made the ask clearer", "Removed passive voice", "Added specific deadline")
Alternative version (optional but valuable) — if there's a meaningfully different
way to approach the same message (e.g. softer vs. more direct), offer it as Option B
with a one-line explanation of when to use it.
Example
Input:
"Write an email to my manager telling him the test environment is broken and i cant do my testing and we might miss the release deadline but dont want to sound panicky"
Output:
Subject: Test Environment Issue — Potential Impact on Release Timeline
Hi [Manager's Name],
I wanted to flag an issue with the test environment that's currently blocking my testing work. Since this morning, [describe the issue briefly — e.g. the env is down / deployments are failing], and I haven't been able to proceed with the scheduled test execution.
If this isn't resolved by [date/time], it could impact our ability to meet the [release name] deadline. I wanted to raise it early so we have time to act.
Could you help escalate this with the infra/DevOps team, or let me know if there's an alternative environment I can use in the meantime?
Happy to jump on a quick call if helpful.
Thanks,
[Your Name]
Tone used: Professional + Assertive
What changed:
- Replaced panic with clear, factual framing of the problem
- Added a specific deadline reference to convey urgency without drama
- Ended with a concrete ask and offered a solution path
Option B (more direct, for urgent escalation):
Subject: URGENT: Test Env Down — Release at Risk
[Manager's Name], the test environment has been down since [time] and is blocking all QA activity. We risk missing the [release] deadline if it's not resolved by [time]. Requesting immediate escalation to DevOps. Let me know how you'd like to proceed.
— [Your Name]
(Use this if the situation is truly critical and speed matters more than softness)
Tips for Best Results
- Paste your rough draft — even terrible wording is fine, the skill will fix it.
- Say who you're writing to — it changes the tone significantly.
- Mention the outcome you want — a reply? An action? An apology accepted?
- Say if there are constraints — "keep it under 5 lines", "don't sound too formal".
- Multiple emails? List them all — each gets its own rewrite.
1---2name: email-message-rewriter3description: Rewrites, polishes, or drafts emails and messages from rough notes, bullet points, or poorly worded drafts — in the right tone for the situation. Handles professional emails, Slack messages, WhatsApp texts, follow-ups, apologies, feedback, and more. Use this skill whenever the user says: "rewrite this email", "make this sound professional", "write an email for me", "help me reply to this", "make this polite", "draft a message", "how do I say this nicely", "write a follow-up", "make this less aggressive", "I need to send this but don't know how to word it", or shares a rough draft asking for improvements. Always trigger — even for short messages. A one-line rewrite is still worth doing well.4---56# Email & Message Rewriter78Rewrite, polish, or draft any email or message — from rough notes or bad drafts — in the9right tone for the situation. Works for professional emails, Slack, WhatsApp, follow-ups,10apologies, feedback, and more.1112---1314## Supported Message Types1516| Type | Examples |17|---|---|18| 💼 Professional Email | Work requests, updates, escalations, client communication |19| 🔁 Follow-up | Chasing a reply, following up on a task or meeting |20| 🐛 Bug / Issue Escalation | Reporting a critical issue to manager or client |21| 🙏 Apology | Missed deadline, mistake, delayed response |22| 💬 Slack / Teams message | Quick team update, question, async request |23| 📱 WhatsApp / Text | Personal or semi-formal short messages |24| 📝 Feedback | Giving or responding to feedback professionally |25| ❌ Declining / Saying No | Politely turning down a request |26| 🎉 Appreciation | Thanking a colleague, recognising good work |2728---2930## Tone Options3132| Tone | When to use |33|---|---|34| **Formal** | Senior management, clients, official communication |35| **Professional** | Default for most work emails |36| **Friendly-Professional** | Colleagues, collaborative teams |37| **Friendly** | Close colleagues, semi-personal messages |38| **Direct** | When brevity and clarity matter most |39| **Assertive** | Escalations, pushing back, setting boundaries |40| **Empathetic** | Apologies, difficult news, sensitive topics |4142If the user doesn't specify a tone, **infer it from context**:43- Work email → Professional44- Message to manager about urgent issue → Assertive + Professional45- Apology to colleague → Empathetic + Friendly46- Slack/WhatsApp → Friendly or Friendly-Professional4748---4950## Workflow5152### Step 1 — Understand the Input5354Extract from the user's message:55- **What they want to say** (the core message/intent)56- **Who they're writing to** (manager, client, colleague, friend)57- **What channel** (email, Slack, WhatsApp, text)58- **Desired outcome** (get a reply, apologise, escalate, inform, ask for something)59- **Tone preference** (if stated; otherwise infer)60- **Any constraints** (keep it short, formal, don't sound angry, etc.)6162### Step 2 — Rewrite6364Apply these principles:65- **Clear subject line** for emails (action-oriented: "Request for...", "Update on...", "Follow-up: ...")66- **One purpose per message** — don't mix topics67- **Lead with the most important point** — don't bury the ask68- **Specific and concrete** — avoid vague language like "at your earliest convenience"69- **Active voice** — "I need X" not "X is needed"70- **Appropriate length** — email: 3–8 sentences; Slack: 1–4 sentences; text: 1–2 sentences71- **Polite but not over-apologetic** — don't start with "Sorry to bother you"72- **Clear call to action** — end with what you need from them7374### Step 3 — Output Format7576Always output:77781. **The rewritten message** — ready to copy and send79 - For emails: include Subject line, greeting, body, sign-off80 - For Slack/chat: just the message body81 - For texts: just the message82832. **Tone label** — e.g. "Tone used: Professional + Assertive"84853. **What changed** — 2–3 bullet points explaining the key improvements made86 (e.g. "Made the ask clearer", "Removed passive voice", "Added specific deadline")87884. **Alternative version** (optional but valuable) — if there's a meaningfully different89 way to approach the same message (e.g. softer vs. more direct), offer it as Option B90 with a one-line explanation of when to use it.9192---9394## Example9596**Input:**97> "Write an email to my manager telling him the test environment is broken and i cant do my testing and we might miss the release deadline but dont want to sound panicky"9899**Output:**100101**Subject:** Test Environment Issue — Potential Impact on Release Timeline102103Hi [Manager's Name],104105I wanted to flag an issue with the test environment that's currently blocking my testing work. Since this morning, [describe the issue briefly — e.g. the env is down / deployments are failing], and I haven't been able to proceed with the scheduled test execution.106107If this isn't resolved by [date/time], it could impact our ability to meet the [release name] deadline. I wanted to raise it early so we have time to act.108109Could you help escalate this with the infra/DevOps team, or let me know if there's an alternative environment I can use in the meantime?110111Happy to jump on a quick call if helpful.112113Thanks,114[Your Name]115116---117**Tone used:** Professional + Assertive118**What changed:**119- Replaced panic with clear, factual framing of the problem120- Added a specific deadline reference to convey urgency without drama121- Ended with a concrete ask and offered a solution path122123**Option B (more direct, for urgent escalation):**124> Subject: URGENT: Test Env Down — Release at Risk125> [Manager's Name], the test environment has been down since [time] and is blocking all QA activity. We risk missing the [release] deadline if it's not resolved by [time]. Requesting immediate escalation to DevOps. Let me know how you'd like to proceed.126> — [Your Name]127> *(Use this if the situation is truly critical and speed matters more than softness)*128129---130131## Tips for Best Results132133- **Paste your rough draft** — even terrible wording is fine, the skill will fix it.134- **Say who you're writing to** — it changes the tone significantly.135- **Mention the outcome you want** — a reply? An action? An apology accepted?136- **Say if there are constraints** — "keep it under 5 lines", "don't sound too formal".137- **Multiple emails?** List them all — each gets its own rewrite.
ShreyasBh02