Systems Lab

Agent skill

email-composer

Draft professional emails for business and marketing contexts — outreach, client communication, proposals, follow-ups, and internal updates.

slowingSelf-containedActs undeclared523 words

Filed under Outbound email.

From thatrebeccarae/claude-marketing · 42 skills · 119 · pushed 2026-05-14

What it does when it runs

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.

Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.
Actions present in the files
shell

Ask about email-composer

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/thatrebeccarae/claude-marketing.git /tmp/claude-marketing
git -C /tmp/claude-marketing sparse-checkout set "skills/email-composer"
mkdir -p ~/.claude/skills/email-composer
cp -R "/tmp/claude-marketing/skills/email-composer/." ~/.claude/skills/email-composer/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from thatrebeccarae/claude-marketing/blob/a8a63ec1341f05ec9c1e9cb52b4edeb14e3bdcba/skills/email-composer/SKILL.md, which is licensed MIT (skill frontmatter). 523 words, 13 headings.

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.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what email-composer does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.