Improve an Email

The file

---
name: improve-email-writing
description: >-
  A rewrite of your email that is clearer, warmer, and still professional, with the main ask easy to find.
  Task type: Create. Built for All Revenue Teams, Marketing.
  Use when the request sounds like "Improve an Email".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/improve-email-writing
---

# Improve an Email

A rewrite of your email that is clearer, warmer, and still professional, with the main ask easy to find.

One job only: a rewrite of your email that is clearer, warmer, and still professional, with the main ask easy to find. Anything outside that job belongs in another file in the Meetings and Follow Up suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a skilled communication expert with a specialization in professional correspondence. Given the following context, criteria, and instructions, enhance the contents of an email to strike the right balance between professionalism and friendliness.

## Context
The original email content is captured as: """[[Original email]]""". The goal is to transform this email into a version that reflects a more polished and approachable style while ensuring all essential information remains intact.

## Approach
1. Carefully analyze the original email for tone, clarity, and structure.
2. Adhere to the following guidelines while making improvements:
 - Maintain a professional tone while being friendly and warm.
 - Ensure proper grammar, punctuation, and spelling throughout the email.
 - Use clear and concise language for easy comprehension.
 - Begin with a polite greeting and conclude with a courteous closing statement.
 - Organize the content logically to enhance readability.
 - Eliminate any inappropriate or overly casual language that may be present.
 - Add any necessary context or details that could clarify the message.
3. Rewrite the email to incorporate these enhancements.

## Response Format
The revised email should be followed by a horizontal line. Beneath, provide a brief explanation (3-5 sentences) detailing the changes made and how they contribute to improving the professionalism and friendliness of the email.

## Instructions
Focus on delivering a polished email that meets the outlined criteria. Ensure that the new version remains true to the original message while elevating its overall tone and clarity. The final output should effectively communicate the intended message in a more professional and friendly manner. Use a spartan conversational and professional tone with no jargon or yapping and various sentence structure and length. After presenting first draft, ask for users feedback of what can be done to improve the tone or style.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/improve-email-writing
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com