New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Write and sequence multi-email nurture or launch campaigns

Email Campaign Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Email Campaign Skill cover

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.

---
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?)

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill email-campaign -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/email-campaign
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/38149f605f2fbe48f27d/email-campaign.zip" -OutFile "$env:TEMP\email-campaign.zip"; Expand-Archive "$env:TEMP\email-campaign.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.1 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text87 lines

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"
1---
2name: email-campaign
3description: "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."
4---
5 
6# Email Campaign Skill
7 
8This 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.
9 
10## Required Inputs
11 
12Ask the user for these if not provided:
13- **Campaign goal** (onboard new users / launch a product / nurture leads / re-engage churned users / announce a feature)
14- **Audience** (who receives this? job title, lifecycle stage, what they know already)
15- **Product or offer** being promoted or introduced
16- **Number of emails in sequence** (if unsure, recommend based on goal)
17- **Tone** (professional / conversational / bold / educational)
18- **Sender name** (person or brand?)
19 
20## Sequence Recommendations by Goal
21 
22If the user hasn't specified number of emails, use these defaults:
23- **Onboarding:** 4 emails over 7 days (Day 0, Day 1, Day 3, Day 7)
24- **Product launch:** 3 emails (Teaser → Launch Day → Follow-up/Last chance)
25- **Lead nurture:** 5 emails over 2 weeks
26- **Re-engagement:** 3 emails (Gentle nudge → Value reminder → Final offer)
27- **Feature announcement:** 2 emails (Announcement → How-to/deep dive)
28 
29## Output Structure Per Email
30 
31For every email in the sequence, produce:
32 
33---
34 
35**Email [N] of [Total] — [Descriptive label e.g. "Welcome / Day 0"]**
36**Send timing:** [When relative to trigger event or previous email]
37 
38**Subject line:** [Primary option]
39**Subject line (A/B variant):** [Alternative to test]
40**Preview text:** [40–90 characters — adds context to the subject, doesn't repeat it]
41 
42**Body:**
43 
44[Full email copy — formatted with clear opening line, 2–3 body paragraphs, one primary CTA]
45 
46**CTA button text:** [3–6 words]
47**CTA destination:** [What page/action this should link to]
48 
49**Strategic note:** [Why this email does what it does — the psychological or strategic intent. 1–2 sentences.]
50 
51---
52 
53## Writing Rules
54 
55- Opening line must earn attention — no "Hi, welcome to [product]" openers
56- Each email has ONE primary CTA — never two competing asks
57- Keep paragraphs to 2–3 sentences maximum for mobile readability
58- Use "you" more than "we" — centre the reader, not the brand
59- Subject lines under 50 characters perform best on mobile — flag if going over
60- Preview text should add information the subject doesn't — never just repeat it
61- Every email should stand alone — assume some subscribers miss earlier emails
62 
63## Quality Checks
64 
65- [ ] Each email has a single clear CTA
66- [ ] Subject lines are under 50 characters (or flagged)
67- [ ] Preview text doesn't repeat the subject line
68- [ ] Opening line is specific and attention-earning
69- [ ] Sequence has logical narrative arc (doesn't feel like disconnected blasts)
70- [ ] Tone is consistent across all emails
71- [ ] Strategic notes explain the intent of each email
72 
73## Anti-Patterns
74 
75- [ ] Do not include more than one primary CTA per email — competing calls to action reduce click-through by splitting attention
76- [ ] 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
77- [ ] 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
78- [ ] 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
79- [ ] Do not assume all subscribers receive all emails — each email must stand alone for subscribers who missed earlier messages in the sequence
80 
81## Example Trigger Phrases
82 
83- "Write a 3-email launch sequence for [product]"
84- "Build an onboarding email flow for [SaaS tool]"
85- "Create a drip campaign to nurture leads for [offer]"
86- "Write a re-engagement campaign for churned users"
87 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with email-campaign

Email Campaign Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Email Campaign Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Email Campaign Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Email Campaign Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillSays 'newsletter', 'email newsletter', 'weekly digest'Newsletter: Writing email newsletter edition...cwinvestments/memstack · by cwinvestmentsUse this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.★ 423 GitHub starsSkillWrite a signal-based cold outreach email that earns a replySignal-Based Cold Email (2026 benchmarks)kami-community/kami · by kami-communityWrite a signal-based cold outreach email that earns a reply. Use when drafting outbound/SDR email to a prospect with a known recent signal (funding, hiring, exec hire, launch, community post).★ 64 GitHub starsSkillHostinger Reach API for contact management, segmentationHostinger Reach (Email Marketing)hostinger/hostinger-agent-skills · by hostingerHostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.★ 23 GitHub starsMCPExpert email marketing strategist for CRM-driven campaignsmsitarzewski/agency-agents · by msitarzewskiExpert email marketing strategist for CRM-driven campaigns, lifecycle automation, segmentation architecture, and deliverability. Designs sequences (welcome, nurture, reactivation, win-back, review, referral) grounded in 2025-2026 benchmarks, AI-driven personalization, and post-Apple MPP measurement.★ 154k GitHub starsSkillWrite B2B cold emails and follow-up sequences that getCold Email Writingcoreyhaines31/marketingskills · by coreyhaines31Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.★ 51.1k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars