Email & Message Rewriter

Tone Options

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:

1. 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

2. Tone label — e.g. "Tone used: Professional + Assertive"

3. What changed — 2–3 bullet points explaining the key improvements made (e.g. "Made the ask clearer", "Removed passive voice", "Added specific deadline")

4. 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.