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

Design and write email campaigns and sequences including

Email sequences

by rampstackco · MIT license · ★ 901 on GitHub · updated Sep 15

Email sequences cover

Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write…

---
name: email-sequences
description: "Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns."
category: content
catalog_summary: "Onboarding flows, lifecycle campaigns, transactional copy"
display_order: 5
---

# Email Sequences

Plan and write email campaigns. Sequences (multi-message flows triggered by events) and broadcasts (one-off sends). Stack-agnostic. Works with any email service provider.

---

## When to use

- Writing welcome and onboarding email sequences
- Planning lifecycle campaigns (activation, retention, win-back)

Overview

Plan and write email campaigns. Sequences (multi-message flows triggered by events) and broadcasts (one-off sends). Stack-agnostic. Works with any email service provider.

Manual install (npx, ZIP)
Claude Codenpx skills add rampstackco/claude-skills --skill email-sequences -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/rampstackco/claude-skills/tar.gz/3d4510a94a76 \ | tar -xz -C ~/.claude/skills --strip-components=2 claude-skills-3d4510a94a76/skills/email-sequences
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/cd0d3017831807bb8a5a/email-sequences.zip" -OutFile "$env:TEMP\email-sequences.zip"; Expand-Archive "$env:TEMP\email-sequences.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.md10.2 KB
  • references/2 files · 15.3 KB
Read the files here
rampstackco/3d4510a3 files
SKILL.md
Show the full text283 lines

Email Sequences

Plan and write email campaigns. Sequences (multi-message flows triggered by events) and broadcasts (one-off sends). Stack-agnostic. Works with any email service provider.


When to use

  • Writing welcome and onboarding email sequences
  • Planning lifecycle campaigns (activation, retention, win-back)
  • Writing transactional emails (receipts, password resets, notifications)
  • Newsletter design and writing
  • Abandoned-cart or re-engagement flows
  • Writing a one-off broadcast, launch announcement, or news email
  • Drafting email subject lines and preview text for any send

When NOT to use

  • Landing pages and conversion pages (use landing-page-copy)
  • Long-form articles (use content-and-copy)
  • Brand voice work (use brand-voice)
  • Analytics setup for email (use analytics-strategy)

Required inputs

  • The audience (segment or list)
  • The trigger or context (signup, purchase, abandonment, time-based, manual)
  • The goal of the email or sequence
  • Brand voice
  • Any technical constraints (provider, deliverability requirements)

If the audience is undefined, define it before writing. Generic emails to "everyone" perform worse than targeted ones.


The framework: 6 sequence types

Most email programs run a handful of standard sequence patterns. Each has its own goals, structure, and pitfalls.

1. Welcome / onboarding

Triggered by signup. Goal: get the user to first value.

Typical structure (5 emails over 14 days):

  • Email 1 (immediate): Welcome. Confirm they're in. State what happens next. Single CTA: the next obvious action.
  • Email 2 (day 1 or 2): First-value step. Help them get to a quick win or core action.
  • Email 3 (day 4 or 5): Education. Show them something they probably haven't discovered yet.
  • Email 4 (day 8): Social proof. Customer story or use case relevant to their segment.
  • Email 5 (day 14): Outcome reminder. Where they could be in 30/60/90 days. Soft commercial cue.

Common failure: Front-loading product features. Users don't care about features yet; they care about getting to value.

2. Lifecycle / activation

Time- or behavior-triggered. Goal: move users from signup to engaged user.

Patterns:

  • Sent when a user completes a milestone (first project, first invite, first export)
  • Or sent when a user has NOT completed a milestone after N days
  • Each email targets a specific next step

Best practice: Trigger on behavior, not just time. A user who has done 3 onboarding steps doesn't need an email telling them to get started.

3. Retention / engagement

Ongoing. Goal: keep active users engaged.

Patterns:

  • Newsletter (weekly or monthly)
  • Product updates
  • Tips and tutorials
  • Customer-only content (community, behind-the-scenes)

Cadence rule: Frequency that earns the read, not frequency that fills the calendar. Weekly newsletter that is genuinely useful beats daily newsletter that gets archived.

4. Re-engagement / win-back

Triggered by inactivity. Goal: pull a lapsed user back.

Typical structure (3 emails):

  • Email 1: "We miss you" framing or value reminder. What's new since they were last active.
  • Email 2: Specific incentive (discount, feature unlock, content offer).
  • Email 3: "Last call" or list-cleaning email. "We'll stop emailing you unless you click this."

Best practice: Honor the unsubscribe. Aggressive win-back damages deliverability. A clean list of engaged subscribers beats a large list of inactive ones.

5. Transactional

Triggered by actions: receipts, password resets, notifications, order confirmations, shipping updates.

Best practices:

  • Confirm the action that triggered the email at the top
  • Include all relevant detail without padding
  • Use plain language ("Your order shipped" not "Your shipment notification")
  • One primary CTA (track package, view receipt, view account)
  • Subject line states the action ("Your receipt for order #12345")

Highest open rates of any email type. Use sparingly for marketing nudges; over-marketing transactional emails damages trust.

6. Broadcast

One-off sends. Announcements, launches, news, time-sensitive campaigns.

Best practices:

  • Subject line earns the open
  • Single clear message per send
  • Specific audience targeting (do not blast the entire list for narrow announcements)
  • Clear CTA in the first screen-height
  • Mobile-optimized (most opens are mobile)

The 5 components of every email

Regardless of sequence type, every email has the same components.

1. Subject line

The deciding factor for whether the email gets opened.

Patterns:

  • Specific ("Your week 1 progress: 3 of 5 steps done")
  • Curiosity ("The mistake most teams make in week 2")
  • Direct ("Your invoice #12345")
  • Personal ("Quick question, [name]")
  • Urgency ("Last day for the team plan discount") - use sparingly

Avoid:

  • ALL CAPS
  • Excessive punctuation (!!!)
  • Click-bait that doesn't deliver
  • Generic ("Newsletter #23")

Length: 30 to 50 characters. Mobile clients truncate longer.

2. Preview text (preheader)

The line that appears below or beside the subject in most email clients.

Best practice:

  • Treat as the subject's wingman
  • Add what the subject line couldn't fit
  • Avoid wasting it on "View this email in browser"
  • 50 to 90 characters
3. Opening

The first line of the email body. The reader is deciding whether to keep reading.

Strong openings:

  • Reference the trigger ("You signed up yesterday for...")
  • Get to the point ("Here's what changed this week...")
  • Personal ("Saw your team just hit milestone X. Nice work.")

Weak openings:

  • "I hope this email finds you well."
  • "Welcome to our amazing platform."
  • Long throat-clearing before the actual content
4. Body

The substance.

Length guide:

  • Welcome and transactional: under 100 words
  • Lifecycle and activation: 100 to 250 words
  • Newsletter: 200 to 800 words depending on format
  • Sales sequences: 250 to 500 words

Structure:

  • One core message per email (avoid "while we have you...")
  • Short paragraphs (2 to 3 lines)
  • Bullets or lists when content is enumerable
  • Mobile-first formatting
5. CTA

The action the email is asking for.

Best practices:

  • One primary CTA per email (multiple CTAs split attention)
  • Button or clearly-styled link, not buried in prose
  • Action verb + specific outcome ("See your dashboard" not "Click here")
  • Above the fold AND repeated at the end of longer emails
  • Plain text link as a fallback for users who block buttons

Workflow

For a new sequence
  1. Define the trigger. What event starts this sequence? (Signup, purchase, abandonment, manual.)
  2. Define the goal. What does success look like at the end of the sequence?
  3. Map the journey. What does the recipient need to know, do, or feel between trigger and goal?
  4. Outline emails. One purpose per email. Sequence them across appropriate timing.
  5. Draft email 1. Subject, preview, opening, body, CTA.
  6. Draft remaining emails. Each builds on the previous.
  7. Test the sequence. Send to yourself. Read on mobile. Time the gaps.
  8. Set up triggers. Configure in the email service provider.
  9. Measure. Open rate, click rate, completion rate per email. Sequence completion rate.
For a single broadcast
  1. Define the audience. Specific segment, not the whole list.
  2. Define the goal. One thing this email accomplishes.
  3. Draft subject + preview. Generate 5 to 10 variations.
  4. Draft body. Single message, clear CTA.
  5. Test on mobile. Most opens are mobile.
  6. Schedule. Day and time matched to audience behavior.
  7. Measure. Open rate, click rate, downstream conversions.

Failure patterns

  • Sending to "everyone." Generic broadcasts to the full list have lower engagement than targeted segments.
  • Too many CTAs in one email. Splits attention. Pick one.
  • Subject line clickbait that doesn't deliver. Crashes the trust the email program is trying to build.
  • Sequences that ignore behavior. Sending day-3 onboarding email to a user who already activated wastes the touch.
  • Mobile-broken layouts. 60 to 70 percent of opens are on mobile. Test there first.
  • Long pre-text. Burying the message under "I hope this email finds you well" wastes the read.
  • Aggressive win-back. Emailing dormant users 5 times damages deliverability and brand trust.
  • No measurement. Without tracking opens, clicks, and downstream conversion, you can't iterate.
  • Ignoring deliverability. Sender reputation, authentication (SPF, DKIM, DMARC), list hygiene. Skip these and emails go to spam regardless of how good the content is.

Output format

Default output is a markdown document per email or sequence:

# Sequence: [Name]

**Trigger:** [What starts this sequence]
**Goal:** [Outcome at completion]
**Audience:** [Specific segment]
**Length:** [N emails over X days]

## Email 1 - [Subject working title]

**Send:** [Trigger / Day N]
**Subject:** [text]
**Preview:** [text]

[Body]

**Primary CTA:** [text]
**CTA URL:** [destination]

---

## Email 2 - [Subject working title]

[Same structure]

---

[etc.]

For a single broadcast, just one email block.


Reference files

1---
2name: email-sequences
3description: "Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns."
4category: content
5catalog_summary: "Onboarding flows, lifecycle campaigns, transactional copy"
6display_order: 5
7---
8 
9# Email Sequences
10 
11Plan and write email campaigns. Sequences (multi-message flows triggered by events) and broadcasts (one-off sends). Stack-agnostic. Works with any email service provider.
12 
13---
14 
15## When to use
16 
17- Writing welcome and onboarding email sequences
18- Planning lifecycle campaigns (activation, retention, win-back)
19- Writing transactional emails (receipts, password resets, notifications)
20- Newsletter design and writing
21- Abandoned-cart or re-engagement flows
22- Writing a one-off broadcast, launch announcement, or news email
23- Drafting email subject lines and preview text for any send
24 
25## When NOT to use
26 
27- Landing pages and conversion pages (use `landing-page-copy`)
28- Long-form articles (use `content-and-copy`)
29- Brand voice work (use `brand-voice`)
30- Analytics setup for email (use `analytics-strategy`)
31 
32---
33 
34## Required inputs
35 
36- The audience (segment or list)
37- The trigger or context (signup, purchase, abandonment, time-based, manual)
38- The goal of the email or sequence
39- Brand voice
40- Any technical constraints (provider, deliverability requirements)
41 
42If the audience is undefined, define it before writing. Generic emails to "everyone" perform worse than targeted ones.
43 
44---
45 
46## The framework: 6 sequence types
47 
48Most email programs run a handful of standard sequence patterns. Each has its own goals, structure, and pitfalls.
49 
50### 1. Welcome / onboarding
51 
52Triggered by signup. Goal: get the user to first value.
53 
54**Typical structure (5 emails over 14 days):**
55 
56- **Email 1 (immediate):** Welcome. Confirm they're in. State what happens next. Single CTA: the next obvious action.
57- **Email 2 (day 1 or 2):** First-value step. Help them get to a quick win or core action.
58- **Email 3 (day 4 or 5):** Education. Show them something they probably haven't discovered yet.
59- **Email 4 (day 8):** Social proof. Customer story or use case relevant to their segment.
60- **Email 5 (day 14):** Outcome reminder. Where they could be in 30/60/90 days. Soft commercial cue.
61 
62**Common failure:** Front-loading product features. Users don't care about features yet; they care about getting to value.
63 
64### 2. Lifecycle / activation
65 
66Time- or behavior-triggered. Goal: move users from signup to engaged user.
67 
68**Patterns:**
69- Sent when a user completes a milestone (first project, first invite, first export)
70- Or sent when a user has NOT completed a milestone after N days
71- Each email targets a specific next step
72 
73**Best practice:** Trigger on behavior, not just time. A user who has done 3 onboarding steps doesn't need an email telling them to get started.
74 
75### 3. Retention / engagement
76 
77Ongoing. Goal: keep active users engaged.
78 
79**Patterns:**
80- Newsletter (weekly or monthly)
81- Product updates
82- Tips and tutorials
83- Customer-only content (community, behind-the-scenes)
84 
85**Cadence rule:** Frequency that earns the read, not frequency that fills the calendar. Weekly newsletter that is genuinely useful beats daily newsletter that gets archived.
86 
87### 4. Re-engagement / win-back
88 
89Triggered by inactivity. Goal: pull a lapsed user back.
90 
91**Typical structure (3 emails):**
92 
93- **Email 1:** "We miss you" framing or value reminder. What's new since they were last active.
94- **Email 2:** Specific incentive (discount, feature unlock, content offer).
95- **Email 3:** "Last call" or list-cleaning email. "We'll stop emailing you unless you click this."
96 
97**Best practice:** Honor the unsubscribe. Aggressive win-back damages deliverability. A clean list of engaged subscribers beats a large list of inactive ones.
98 
99### 5. Transactional
100 
101Triggered by actions: receipts, password resets, notifications, order confirmations, shipping updates.
102 
103**Best practices:**
104- Confirm the action that triggered the email at the top
105- Include all relevant detail without padding
106- Use plain language ("Your order shipped" not "Your shipment notification")
107- One primary CTA (track package, view receipt, view account)
108- Subject line states the action ("Your receipt for order #12345")
109 
110**Highest open rates** of any email type. Use sparingly for marketing nudges; over-marketing transactional emails damages trust.
111 
112### 6. Broadcast
113 
114One-off sends. Announcements, launches, news, time-sensitive campaigns.
115 
116**Best practices:**
117- Subject line earns the open
118- Single clear message per send
119- Specific audience targeting (do not blast the entire list for narrow announcements)
120- Clear CTA in the first screen-height
121- Mobile-optimized (most opens are mobile)
122 
123---
124 
125## The 5 components of every email
126 
127Regardless of sequence type, every email has the same components.
128 
129### 1. Subject line
130 
131The deciding factor for whether the email gets opened.
132 
133**Patterns:**
134- **Specific** ("Your week 1 progress: 3 of 5 steps done")
135- **Curiosity** ("The mistake most teams make in week 2")
136- **Direct** ("Your invoice #12345")
137- **Personal** ("Quick question, [name]")
138- **Urgency** ("Last day for the team plan discount") - use sparingly
139 
140**Avoid:**
141- ALL CAPS
142- Excessive punctuation (!!!)
143- Click-bait that doesn't deliver
144- Generic ("Newsletter #23")
145 
146**Length:** 30 to 50 characters. Mobile clients truncate longer.
147 
148### 2. Preview text (preheader)
149 
150The line that appears below or beside the subject in most email clients.
151 
152**Best practice:**
153- Treat as the subject's wingman
154- Add what the subject line couldn't fit
155- Avoid wasting it on "View this email in browser"
156- 50 to 90 characters
157 
158### 3. Opening
159 
160The first line of the email body. The reader is deciding whether to keep reading.
161 
162**Strong openings:**
163- Reference the trigger ("You signed up yesterday for...")
164- Get to the point ("Here's what changed this week...")
165- Personal ("Saw your team just hit milestone X. Nice work.")
166 
167**Weak openings:**
168- "I hope this email finds you well."
169- "Welcome to our amazing platform."
170- Long throat-clearing before the actual content
171 
172### 4. Body
173 
174The substance.
175 
176**Length guide:**
177- Welcome and transactional: under 100 words
178- Lifecycle and activation: 100 to 250 words
179- Newsletter: 200 to 800 words depending on format
180- Sales sequences: 250 to 500 words
181 
182**Structure:**
183- One core message per email (avoid "while we have you...")
184- Short paragraphs (2 to 3 lines)
185- Bullets or lists when content is enumerable
186- Mobile-first formatting
187 
188### 5. CTA
189 
190The action the email is asking for.
191 
192**Best practices:**
193- One primary CTA per email (multiple CTAs split attention)
194- Button or clearly-styled link, not buried in prose
195- Action verb + specific outcome ("See your dashboard" not "Click here")
196- Above the fold AND repeated at the end of longer emails
197- Plain text link as a fallback for users who block buttons
198 
199---
200 
201## Workflow
202 
203### For a new sequence
204 
2051. **Define the trigger.** What event starts this sequence? (Signup, purchase, abandonment, manual.)
2062. **Define the goal.** What does success look like at the end of the sequence?
2073. **Map the journey.** What does the recipient need to know, do, or feel between trigger and goal?
2084. **Outline emails.** One purpose per email. Sequence them across appropriate timing.
2095. **Draft email 1.** Subject, preview, opening, body, CTA.
2106. **Draft remaining emails.** Each builds on the previous.
2117. **Test the sequence.** Send to yourself. Read on mobile. Time the gaps.
2128. **Set up triggers.** Configure in the email service provider.
2139. **Measure.** Open rate, click rate, completion rate per email. Sequence completion rate.
214 
215### For a single broadcast
216 
2171. **Define the audience.** Specific segment, not the whole list.
2182. **Define the goal.** One thing this email accomplishes.
2193. **Draft subject + preview.** Generate 5 to 10 variations.
2204. **Draft body.** Single message, clear CTA.
2215. **Test on mobile.** Most opens are mobile.
2226. **Schedule.** Day and time matched to audience behavior.
2237. **Measure.** Open rate, click rate, downstream conversions.
224 
225---
226 
227## Failure patterns
228 
229- **Sending to "everyone."** Generic broadcasts to the full list have lower engagement than targeted segments.
230- **Too many CTAs in one email.** Splits attention. Pick one.
231- **Subject line clickbait that doesn't deliver.** Crashes the trust the email program is trying to build.
232- **Sequences that ignore behavior.** Sending day-3 onboarding email to a user who already activated wastes the touch.
233- **Mobile-broken layouts.** 60 to 70 percent of opens are on mobile. Test there first.
234- **Long pre-text.** Burying the message under "I hope this email finds you well" wastes the read.
235- **Aggressive win-back.** Emailing dormant users 5 times damages deliverability and brand trust.
236- **No measurement.** Without tracking opens, clicks, and downstream conversion, you can't iterate.
237- **Ignoring deliverability.** Sender reputation, authentication (SPF, DKIM, DMARC), list hygiene. Skip these and emails go to spam regardless of how good the content is.
238 
239---
240 
241## Output format
242 
243Default output is a markdown document per email or sequence:
244 
245```markdown
246# Sequence: [Name]
247 
248**Trigger:** [What starts this sequence]
249**Goal:** [Outcome at completion]
250**Audience:** [Specific segment]
251**Length:** [N emails over X days]
252 
253## Email 1 - [Subject working title]
254 
255**Send:** [Trigger / Day N]
256**Subject:** [text]
257**Preview:** [text]
258 
259[Body]
260 
261**Primary CTA:** [text]
262**CTA URL:** [destination]
263 
264---
265 
266## Email 2 - [Subject working title]
267 
268[Same structure]
269 
270---
271 
272[etc.]
273```
274 
275For a single broadcast, just one email block.
276 
277---
278 
279## Reference files
280 
281- [`references/subject-line-patterns.md`](references/subject-line-patterns.md) - Subject line patterns with examples for each sequence type.
282- [`references/sequence-templates.md`](references/sequence-templates.md) - Skeleton templates for the 6 sequence types.
283 
View all files on GitHub →

Details

Updated
Sep 15, 2026
License
MIT
Stars on the repo
★ 901
Checked
Source
rampstackco/claude-skills ↗
Creator
rampstackco · 60 listings
View creator

Made with email-sequences

Email sequences — Showcase grid filtered by Tone equals Provocative and Sensory equals Resonant, showing eight matching brand cards with… (from the rampstackco/claude-skills README)
Email sequences — Showcase grid filtered by Tone equals Provocative and Sensory equals Resonant, showing eight matching brand cards with… (from the rampstackco/claude-skills README)

by rampstackco

Email sequences — Showcase grid with all four axis filters set to Provocative, Editorial Restrained, Coach, and Resonant, showing zero… (from the rampstackco/claude-skills README)
Email sequences — Showcase grid with all four axis filters set to Provocative, Editorial Restrained, Coach, and Resonant, showing zero… (from the rampstackco/claude-skills README)

by rampstackco

Email sequences — RampStack architecture diagram. A central navy hub card shows the RampStack mark with the subtitle 'Stack-agnostic… (from the rampstackco/claude-skills README)
Email sequences — RampStack architecture diagram. A central navy hub card shows the RampStack mark with the subtitle 'Stack-agnostic… (from the rampstackco/claude-skills README)

by rampstackco

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 rampstackco

SkillRun a comprehensive WCAG accessibility audit coveringrampstackco/claude-skills · by rampstackcoRun a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.★ 901 GitHub starsSkillOptimize content and site structure for AI-driven searchAEO and GEOrampstackco/claude-skills · by rampstackcoOptimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure content for AI extraction, or future-proof their SEO for the shift from blue links to AI answers. Triggers on AEO, GEO, AI search, AI SEO, AI overview, generative search, LLM optimization, llms.txt, AI citation, ChatGPT search, Perplexity, Gemini, Claude search, AI assistant optimization, answer engine. Also triggers when the user expresses concern about AI eating their organic traffic or wants to understand how to remain visible as search shifts.★ 901 GitHub starsSkillRun a structured after-action review on a launch, incidentAfter action reportrampstackco/claude-skills · by rampstackcoRun a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.★ 901 GitHub starsSkillDesign measurement frameworks including event taxonomyAnalytics strategyrampstackco/claude-skills · by rampstackcoDesign measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.★ 901 GitHub starsSkillDirect visual and creative work for campaigns, photographyArt directionrampstackco/claude-skills · by rampstackcoDirect visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables. Use `creative-direction` instead when the ask is the project-wide aesthetic brief that this skill consumes as input.★ 901 GitHub starsSkillPlan and run backups, set recovery objectivesBackup and disaster recoveryrampstackco/claude-skills · by rampstackcoPlan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.★ 901 GitHub stars