thatrebeccarae/claude-marketing / skills/email-composer
email-composer
VerifiedDraft 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.
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 3.5 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 5.2 KB |
| SKILL.md | skill md | 3.9 KB |
REFERENCE.md
View on GitHub# Email Composer — Reference
## Email Templates
### Cold Outreach
```
Subject: [Specific value proposition for their situation]
Hi [First Name],
[One sentence showing you researched them — reference something specific about their company, role, or recent work.]
[One sentence about the problem you solve that is relevant to them.] [One sentence about the result, ideally with a number.]
[Specific, low-friction CTA: "Would a 15-minute call next week make sense?" or "Would it be helpful if I sent over [specific deliverable]?"]
Best,
[Your Name]
```
**Rules:**
- Under 100 words
- No attachments on first touch
- Never lead with "My name is..." or "I'm reaching out because..."
- Reference something specific about them (not generic flattery)
### Warm Follow-Up (After Introduction)
```
Subject: [Mutual contact name] suggested we connect
Hi [First Name],
[Mutual contact] mentioned you're [working on / dealing with / interested in] [specific thing]. [One sentence connecting your expertise to their need.]
I [helped / worked with] [similar company/situation] and [specific result].
Would [specific, easy next step] be useful? Happy to [offer something of value first].
Best,
[Your Name]
```
### Deliverable Handoff
```
Subject: [Deliverable name] — ready for review
Hi [First Name],
Attached is the [deliverable name] covering [scope summary].
Key findings:
- [Finding 1 — the most important insight]
- [Finding 2]
- [Finding 3]
[One sentence about recommended next steps or what you need from them.]
Let me know if you have questions — happy to walk through it on a call.
Best,
[Your Name]
```
### Status Update
```
Subject: [Project name] — Week of [Date] Update
Hi [Name/Team],
**Completed this week:**
- [Item 1]
- [Item 2]
**In progress:**
- [Item 1 — expected completion date]
- [Item 2 — expected completion date]
**Blocked / Needs input:**
- [Item — what is needed and from whom]
**Next week:**
- [Priority 1]
- [Priority 2]
Let me know if anything needs reprioritizing.
Best,
[Your Name]
```
### Scope Change Discussion
```
Subject: [Project name] — Scope adjustment for [reason]
Hi [First Name],
During [work/analysis], we identified [new requirement or change]. This was not part of the original scope, and I want to flag it before proceeding.
**What changed:**
[1-2 sentences describing the change]
**Impact:**
- Timeline: [X days/weeks added]
- Budget: [$X additional] or [Absorbed within current scope]
- Trade-off: [If we do this, we deprioritize X]
**Recommendation:**
[Your suggested path forward]
Can we discuss this [on our next call / this week]? I want to make sure we're aligned before moving forward.
Best,
[Your Name]
```
### Meeting Follow-Up
```
Subject: Follow-up: [Meeting topic] — Action items
Hi [Name/Team],
Thanks for the conversation today. Here's what we agreed on:
**Decisions made:**
- [Decision 1]
- [Decision 2]
**Action items:**
- [ ] [Action] — [Owner] — by [Date]
- [ ] [Action] — [Owner] — by [Date]
- [ ] [Action] — [Owner] — by [Date]
**Next meeting:** [Date/Time] to review [topic]
Let me know if I missed anything.
Best,
[Your Name]
```
### Invoice Follow-Up
```
Subject: Invoice #[Number] — Payment reminder
Hi [First Name],
Quick note that invoice #[Number] for [amount] was due on [date]. I know these can slip through — just wanted to flag it.
[If applicable: The invoice is attached / The invoice is in [system].]
Is there anything you need from my end to process this?
Thanks,
[Your Name]
```
## Follow-Up Cadence
### Cold Outreach
| Touch | Timing | Approach |
|-------|--------|----------|
| 1 | Day 0 | Initial email — value proposition |
| 2 | Day 3 | Reply to original — add new value (case study, data point) |
| 3 | Day 7 | New angle — different pain point or use case |
| 4 | Day 14 | Breakup email — "Is this not a priority right now?" |
**Rules:**
- Always reply to the original thread (builds context)
- Each follow-up adds NEW value, not just "checking in"
- After 4 touches with no response, stop and re-approach in 60-90 days
- Never guilt-trip ("I've emailed you 3 times...")
### Client Communication
| Scenario | Follow-Up Timing |
|----------|-----------------|
| Deliverable sent, no response | 3 business days |
| Proposal sent | 5 business days |
| Invoice overdue | 3 days after due date, then weekly |
| Meeting scheduled, no confirmation | Day before |
| Scope change proposed | 2 business days |
## Closing Phrases by Context
| Context | Options |
|---------|---------|
| **Formal** | Sincerely, Best regards, Respectfully |
| **Professional** | Best, Thanks, Kind regards, Regards |
| **Casual** | Cheers, Thanks!, Talk soon, -[Name] |
| **After a favor** | Appreciate it, Thanks for your help |
| **Urgent** | Thanks in advance, Appreciate the quick turnaround |
## Composition Checklist
- [ ] Subject line is specific (not "Update" or "Hello")
- [ ] Opening sentence establishes context
- [ ] Body is under 150 words (or justified if longer)
- [ ] One clear CTA
- [ ] Tone matches the relationship
- [ ] Proofread for typos and tone
- [ ] Correct recipient (check before sending)
- [ ] Attachments actually attached (if mentioned)
- [ ] No sensitive/confidential info if CC'd broadly
- [ ] Signature block is appropriate
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |