email-campaign

GitHub

用于撰写多阶段邮件营销序列(如欢迎、发布、培育)。根据目标自动推荐节奏,输出带A/B测试标题、预览文本、正文及CTA的完整邮件内容,并附策略说明与质量检查规则。

skills/email-campaign/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

需要编写邮件序列或滴灌营销活动 设计新用户引导流程 策划产品发布邮件 制定潜在客户培育方案

Install

npx skills add mohitagw15856/pm-claude-skills --skill email-campaign -g -y
More Options

Use without installing

npx skills use mohitagw15856/pm-claude-skills@email-campaign

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill email-campaign -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "email-campaign",
    "description": "Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence."
}

Email Campaign Skill

This skill writes complete, sequenced email campaigns — from welcome flows to product launches to re-engagement sequences. Each email is written with subject line, preview text, full body copy, and CTA.

Required Inputs

Ask the user for these if not provided:

  • Campaign goal (onboard new users / launch a product / nurture leads / re-engage churned users / announce a feature)
  • Audience (who receives this? job title, lifecycle stage, what they know already)
  • Product or offer being promoted or introduced
  • Number of emails in sequence (if unsure, recommend based on goal)
  • Tone (professional / conversational / bold / educational)
  • Sender name (person or brand?)

Sequence Recommendations by Goal

If the user hasn't specified number of emails, use these defaults:

  • Onboarding: 4 emails over 7 days (Day 0, Day 1, Day 3, Day 7)
  • Product launch: 3 emails (Teaser → Launch Day → Follow-up/Last chance)
  • Lead nurture: 5 emails over 2 weeks
  • Re-engagement: 3 emails (Gentle nudge → Value reminder → Final offer)
  • Feature announcement: 2 emails (Announcement → How-to/deep dive)

Output Structure Per Email

For every email in the sequence, produce:


Email [N] of [Total] — [Descriptive label e.g. "Welcome / Day 0"] Send timing: [When relative to trigger event or previous email]

Subject line: [Primary option] Subject line (A/B variant): [Alternative to test] Preview text: [40–90 characters — adds context to the subject, doesn't repeat it]

Body:

[Full email copy — formatted with clear opening line, 2–3 body paragraphs, one primary CTA]

CTA button text: [3–6 words] CTA destination: [What page/action this should link to]

Strategic note: [Why this email does what it does — the psychological or strategic intent. 1–2 sentences.]


Writing Rules

  • Opening line must earn attention — no "Hi, welcome to [product]" openers
  • Each email has ONE primary CTA — never two competing asks
  • Keep paragraphs to 2–3 sentences maximum for mobile readability
  • Use "you" more than "we" — centre the reader, not the brand
  • Subject lines under 50 characters perform best on mobile — flag if going over
  • Preview text should add information the subject doesn't — never just repeat it
  • Every email should stand alone — assume some subscribers miss earlier emails

Quality Checks

  • Each email has a single clear CTA
  • Subject lines are under 50 characters (or flagged)
  • Preview text doesn't repeat the subject line
  • Opening line is specific and attention-earning
  • Sequence has logical narrative arc (doesn't feel like disconnected blasts)
  • Tone is consistent across all emails
  • Strategic notes explain the intent of each email

Anti-Patterns

  • Do not include more than one primary CTA per email — competing calls to action reduce click-through by splitting attention
  • Do not open with "Hi, welcome to [product]" or any variation of a generic greeting — the opening line must earn attention immediately or recipients stop reading
  • Do not write preview text that repeats the subject line — preview text is a second chance to earn the open, not a repeat of the first chance
  • Do not write a sequence where each email restates the same value proposition — each email must advance the narrative or serve a distinct purpose in the buyer's journey
  • Do not assume all subscribers receive all emails — each email must stand alone for subscribers who missed earlier messages in the sequence

Example Trigger Phrases

  • "Write a 3-email launch sequence for [product]"
  • "Build an onboarding email flow for [SaaS tool]"
  • "Create a drip campaign to nurture leads for [offer]"
  • "Write a re-engagement campaign for churned users"

Version History

  • a38bc30 Current 2026-07-05 11:34

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
d9c13f51
Indexed
2026-07-05 11:34

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-29 11:35
浙ICP备14020137号-1 $방문자$