email-writing

Files (5)

• QUICK_REFERENCE.md
• README.md
• SKILL.md
• EMAIL_TEMPLATES.txt · assets/
• TONE_GUIDELINES.json · references/

SKILL.md (first lines)

# Email Writing Skill

## Purpose

Transform vague email intentions into polished, context-appropriate communication that achieves the sender's goal. This skill adapts tone, formality, length, and psychological framing based on purpose and recipient, then delivers multiple draft options so you choose what feels right.

---

## Input Requirements

The AI should gather (through conversation or structured form):

### Email Fundamentals

- **Purpose of email**: What do you want to happen? (inform, request, propose, decline, thank, apologize, announce, etc.)
- **Recipient(s)**: Who are you writing to? (title, relationship, how well do you know them)
- **Recipient's context**: What do they care about? What's their situation? (busy executive, peer collaborator, new contact, etc.)
- **Your relationship to recipient**: First time reaching out? Ongoing? Hierarchical? Peer?

### Tone & Content Preferences

- **Desired tone**: Formal, professional-warm, casual, enthusiastic, earnest, urgent, etc.
- **Length preference**: Brief (3 sentences), medium (paragraph), detailed (multiple paragraphs)
- **Key message**: What's the 1-2 things they absolutely need to know?
- **Call to action**: What do you want them to do? (reply, attend, approve, forward, etc.)
- **Deadline or urgency**: When do you need a response?

### Optional Enhancements

- **Specific details to include**: Names, dates, numbers, achievements
- **Tone of voice examples**: "Write it like you're texting a friend" or "Write it like a McKinsey consultant"
- **Things to avoid**: Topics/language that won't land well with this recipient
- **Previous context**: If replying, relevant background from prior emails

---

## Processing Steps

### Step 1: Identify the Email Context

Map the email to one of 10+ context types:

- **Leadership/Executive Update** — upward communication, structured format
- **Course/Workshop Announcement** — engaging, enthusiasm, benefit-focused
- **Bio/Abstract/Speaking Response** — professional, credentialed, compelling
- **Networking/Outreach** — warm, value-first, genuine interest
- **Customer/Client Support** — empathetic, solution-focused, clear next steps
- **Internal Team Update** — collaborative, context-setting, inclusive
- **Apology/Difficult Conversation** — sincere, accountable, forward-looking
- **Sales/Partnership Proposal** — compelling, credibility, mutual benefit
- **Decline/Difficult No** — kind, clear, alternative options
- **Thank You/Recognition** — specific, genuine, timely
- **Meeting Request/Scheduling** — clear value, flexible, respect their time

### Step 2: Analyze Recipient Psychology

- What's their current pressure/priority?
- How do they prefer to receive information? (bullets, narrative, data, story)
- What matters to them in this domain?
- What would make them say "yes"?
- What objections might they have?

### Step 3: Determine Tone & Formality Level

- Map purpose + recipient + relationship to appropriate tone
- Formality scale: Very Formal | Professional | Warm-Professional | Casual | Very Casual
- Emotional tone: Urgent | Grateful | Earnest | Enthusiastic | Neutral | Empathetic

### Step 4: Structure the Email

- **Subject line**: Specific, benefit-forward, sense of urgency if needed
- **Greeting**: Appropriate formality (Dear [Name] | Hi [Name] | Hey [Name])
- **Hook/Opening**: Why they should care (in first 1-2 sentences)
- **Body**: Key message, evidence, context (if needed)
- **Call to action**: Crystal clear what you want them to do
- **Closing**: Appropriate sign-off for tone (Sincerely | Best | Thanks | Cheers)

### Step 5: Draft Multiple Versions

Generate 2-3 alternatives:

- **Primary draft**: Your recommended version (best balance of tone/effectiveness)
- **Alternate A**: Slightly more formal version (if they might find primary too casual)
- **Alternate B**: Slightly warmer/more casual version (if primary feels stiff)

### Step 6: Quality Check

- Does it achieve the stated purpose?
- Is the tone consistent throughout?
- Is the CTA crystal clear?
- Did you avoid common mistakes for this context?
- Would the recipient feel respected/understood?

---

## Email Contexts (Detailed)

### 1. Leadership/Executive Update

**When:** Reporting to boss, CEO, board, senior stakeholders  
**Tone:** Formal, concise, results-oriented  
**Rules:**

- Assume they're busy; lead with the headline
- Include metrics/results before narrative
- Structure with clear sections (Status | Wins | Challenges | Next Steps)
- Be honest about problems; show you have solutions
- Respect their time (target: 3-4 paragraphs max)

**Opening:** "I wanted to share quick progress on [Project]. We're on track for [Goal]."  
**Closing:** "Please let me know if you'd like to discuss further."

---

### 2. Course/Workshop Announcement

**When:** Announcing a new learning opportunity  
**Tone:** Enthusiastic, benefit-focused, accessible  
**Rules:**

From baralmanish/AI-Agent-Skills, MIT.

More from baralmanish/AI-Agent-Skills