Email Composer
Draft professional emails for business and marketing contexts.
Install
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/email-composer ~/.claude/skills/
Email Categories
1. Outreach & Prospecting
- Cold outreach (personalized, value-first)
- Warm introduction follow-ups
- Partnership proposals
- Speaking and podcast pitches
2. Client Communication
- Project kickoff
- Status updates and reports
- Scope change discussions
- Invoice and payment follow-ups
- Deliverable handoffs
3. Internal / Team
- Campaign briefs
- Performance recaps
- Cross-functional requests
- Meeting agendas and follow-ups
4. Sales & Proposals
- Proposal cover emails
- Pricing discussions
- Objection handling
- Contract and SOW follow-ups
- Win-back campaigns
Structure Framework
Every email follows this structure:
Subject: [Specific, not generic — include key value or action]
[Opening — context in one sentence: why you are writing]
[Body — 2-3 short paragraphs max, bullet points for multiple items]
[CTA — one clear, specific ask]
[Sign-off — matched to relationship level]
Tone Calibration
| Tone |
Characteristics |
When to Use |
| Formal |
Complete sentences, no contractions, titles, "Dear..." |
C-suite, legal, first contact with enterprise |
| Professional |
Direct but warm, contractions OK, first names |
Clients, colleagues, vendors |
| Casual |
Conversational, personality OK, still clear |
Internal team, close working relationships |
| Urgent |
ACTION REQUIRED flag, bold deadlines, consequences |
Time-sensitive, blocking issues |
Subject Line Formulas
| Formula |
Example |
| Action + Topic + Deadline |
"Review: Q1 Campaign Brief by Friday" |
| Number + Benefit |
"3 Quick Wins from Your GA4 Data" |
| Question |
"Can we schedule 15 min to discuss the Shopify migration?" |
| Value + Context |
"Your Klaviyo Audit Results (3 Revenue Opportunities)" |
| Urgency + Specificity |
"Action needed: Tracking code missing from 4 pages" |
Key Principles
- One email, one CTA. Do not dilute with multiple asks.
- 150 words max for most emails. Respect the reader's time.
- Specific subject lines. "Q4 Campaign Brief — Review by Friday" not "Update."
- Add value, not volume. Never "just checking in" without new information.
- Active voice for CTAs. "Can you review this by Thursday?" not "It would be great if this could be reviewed."
- Context first. Recipient should know why they are reading within the first sentence.
Anti-Patterns
- "Just checking in" without adding value
- Walls of text (>200 words for a simple ask)
- Passive voice CTAs ("It would be great if...")
- Multiple asks in one email
- Generic subject lines ("Update", "Quick question", "FYI")
- Marking everything as urgent
- Reply-all when only one person needs to respond
- Sending when emotional — draft, wait, re-read
For templates and follow-up cadence, see REFERENCE.md.
Brand Context (Optional)
If brand-profile.json exists in the working directory, read it before composing emails. Use the formal_casual axis to set salutation and sign-off style, voice descriptors to guide subject line personality, and colors for email template accent recommendations. This profile is produced by the brand-dna skill.
1---2name: email-composer3description: Draft professional emails for business and marketing contexts — outreach, client communication, proposals, follow-ups, and internal updates. Includes tone calibration, subject line formulas, and follow-up cadence recommendations.4license: MIT5---67# Email Composer89Draft professional emails for business and marketing contexts.1011## Install1213```bash14git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/email-composer ~/.claude/skills/15```1617## Email Categories1819### 1. Outreach & Prospecting20- Cold outreach (personalized, value-first)21- Warm introduction follow-ups22- Partnership proposals23- Speaking and podcast pitches2425### 2. Client Communication26- Project kickoff27- Status updates and reports28- Scope change discussions29- Invoice and payment follow-ups30- Deliverable handoffs3132### 3. Internal / Team33- Campaign briefs34- Performance recaps35- Cross-functional requests36- Meeting agendas and follow-ups3738### 4. Sales & Proposals39- Proposal cover emails40- Pricing discussions41- Objection handling42- Contract and SOW follow-ups43- Win-back campaigns4445## Structure Framework4647Every email follows this structure:4849```50Subject: [Specific, not generic — include key value or action]5152[Opening — context in one sentence: why you are writing]5354[Body — 2-3 short paragraphs max, bullet points for multiple items]5556[CTA — one clear, specific ask]5758[Sign-off — matched to relationship level]59```6061## Tone Calibration6263| Tone | Characteristics | When to Use |64|------|----------------|-------------|65| **Formal** | Complete sentences, no contractions, titles, "Dear..." | C-suite, legal, first contact with enterprise |66| **Professional** | Direct but warm, contractions OK, first names | Clients, colleagues, vendors |67| **Casual** | Conversational, personality OK, still clear | Internal team, close working relationships |68| **Urgent** | ACTION REQUIRED flag, bold deadlines, consequences | Time-sensitive, blocking issues |6970## Subject Line Formulas7172| Formula | Example |73|---------|---------|74| Action + Topic + Deadline | "Review: Q1 Campaign Brief by Friday" |75| Number + Benefit | "3 Quick Wins from Your GA4 Data" |76| Question | "Can we schedule 15 min to discuss the Shopify migration?" |77| Value + Context | "Your Klaviyo Audit Results (3 Revenue Opportunities)" |78| Urgency + Specificity | "Action needed: Tracking code missing from 4 pages" |7980## Key Principles81821. **One email, one CTA.** Do not dilute with multiple asks.832. **150 words max for most emails.** Respect the reader's time.843. **Specific subject lines.** "Q4 Campaign Brief — Review by Friday" not "Update."854. **Add value, not volume.** Never "just checking in" without new information.865. **Active voice for CTAs.** "Can you review this by Thursday?" not "It would be great if this could be reviewed."876. **Context first.** Recipient should know why they are reading within the first sentence.8889## Anti-Patterns9091- "Just checking in" without adding value92- Walls of text (>200 words for a simple ask)93- Passive voice CTAs ("It would be great if...")94- Multiple asks in one email95- Generic subject lines ("Update", "Quick question", "FYI")96- Marking everything as urgent97- Reply-all when only one person needs to respond98- Sending when emotional — draft, wait, re-read99100For templates and follow-up cadence, see [REFERENCE.md](REFERENCE.md).101102## Brand Context (Optional)103104If `brand-profile.json` exists in the working directory, read it before composing emails. Use the `formal_casual` axis to set salutation and sign-off style, voice descriptors to guide subject line personality, and colors for email template accent recommendations. This profile is produced by the `brand-dna` skill.
thatrebeccarae