email-composer 标准

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.

营销 Claude Code Gemini CLI MCP 客户端 Windsurf MIT 163

在 GitHub 打开

安装方式

cp -r skills/email-composer ~/.claude/skills/email-composer

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同，Claude Code 默认是 ~/.claude/skills/

整仓一次性获取：git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git

依赖与权限

无需 API Key
需要联网访问外部服务
依赖外部命令：git
以上为按正文与 frontmatter 自动推断的信号，仅供参考；安装前建议先阅读原文。

SKILL.md 正文

来源 thatrebeccarae/claude-marketing@a8a63ec · 许可 MIT · 内容未修改

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](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.