mcpField
E
email-composer

email-composer

github.com/thatrebeccaraeMarketing & growth187103 installsUpdated 24w ago
Repository

About email-composer

email-composer is a skill for drafting professional business and marketing emails. It serves client-facing and internal teams with guidance on email structure, tone, subject lines, and clear calls to action.

Key features

  1. 01Drafts outreach, client, and team emails
  2. 02Supports sales and proposal messages
  3. 03Tone guidance from formal to urgent
  4. 04Subject-line formulas for common goals
  5. 05Single-call-to-action email structure

Use cases

  1. 01Write personalized prospect outreach
  2. 02Prepare client project updates
  3. 03Draft proposal or payment follow-ups
  4. 04Create concise internal campaign briefs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/thatrebeccarae/claude-marketing --skill email-composer

After installing, type/email-composerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

EXAMPLES.md
LICENSE
REFERENCE.md

Details

From the project README

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

ToneCharacteristicsWhen to Use
FormalComplete sentences, no contractions, titles, "Dear..."C-suite, legal, first contact with enterprise
ProfessionalDirect but warm, contractions OK, first namesClients, colleagues, vendors
CasualConversational, personality OK, still clearInternal team, close working relationships
UrgentACTION REQUIRED flag, bold deadlines, consequencesTime-sensitive, blocking issues

Subject Line Formulas

FormulaExample
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

  1. One email, one CTA. Do not dilute with multiple asks.
  2. 150 words max for most emails. Respect the reader's time.
  3. Specific subject lines. "Q4 Campaign Brief — Review by Friday" not "Update."
  4. Add value, not volume. Never "just checking in" without new information.
  5. Active voice for CTAs. "Can you review this by Thursday?" not "It would be great if this could be reviewed."
  6. 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.

Comments

Markdown supported