Email Sequence
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured framework for creating end-to-end email sequences. It guides users through defining the narrative arc, mapping the customer journey, and establishing technical requirements like branching logic, exit conditions, and suppression rules. It supports various campaign types—from onboarding and lead nurturing to win-back and product launches—ensuring that every email serves a specific purpose within the broader lifecycle. The output includes copy-ready drafts, a visual flow diagram, A/B testing strategies, and performance benchmarks to help users measure success.
What it does
- Generates full email copy including subject lines, preview text, and primary CTAs.
- Maps out sequence architecture with timing, branching logic, and exit conditions.
- Provides industry-standard performance benchmarks for different sequence types.
- Creates a text-based flow diagram to visualize the user journey.
- Suggests A/B testing strategies to optimize open and click-through rates.
- Offers guidance on integrating sequences into CRM or marketing automation platforms.
When to use it
- When you need to build a structured onboarding or lead nurture flow.
- When you are planning a product launch or event follow-up campaign.
- When you need to re-engage inactive users or win back churned customers.
- When you want to map out a complex drip campaign with conditional branching.
- When you need to establish clear KPIs and success metrics for an email series.
Advantages
- Ensures a consistent narrative arc across the entire sequence.
- Reduces manual effort by providing ready-to-use email drafts and logic.
- Helps identify potential drop-off points through visual flow mapping.
- Provides actionable benchmarks to evaluate campaign effectiveness.
- Facilitates data-driven optimization through structured A/B testing suggestions.
Usage examples
- “Create a 5-email onboarding sequence for a new SaaS project management tool.”
- A complete 5-email series with subject lines, body copy, timing, and a flow diagram designed to guide new users from sign-up to core feature adoption.
- “Draft a 3-email win-back sequence for users who haven't logged in for 60 days.”
- A strategic sequence including a check-in, a 'what's new' update, and a final incentive offer, complete with exit conditions and performance benchmarks.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/email-sequence/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip email-sequence.zip -d .agents/skills
Documentation by Anthropic
Email Sequence
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Design and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case.
Trigger
User runs /email-sequence or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.
Inputs
Gather the following from the user. If not provided, ask before proceeding:
Sequence type — one of:
Onboarding
Lead nurture
Re-engagement
Product launch
Event follow-up
Upgrade/upsell
Win-back
Educational drip
Goal — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier)
Audience — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage)
Number of emails (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below
Timing/cadence preferences (optional) — desired spacing between emails (e.g., "every 3 days", "weekly", "aggressive first week then taper off")
Brand voice — if configured in local settings, apply automatically and inform the user. If not configured, ask: "Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone."
Additional context (optional):
Specific offers, discounts, or incentives to include
CTAs or landing pages to link to
Content assets available (blog posts, case studies, videos, guides)
Product features to highlight
Competitor differentiators to reference
Process
1. Sequence Strategy
Before drafting any emails, define the overall sequence architecture:
Narrative arc — what story does this sequence tell across all emails? What is the emotional and logical progression from first email to last?
Journey mapping — map each email to a stage of the buyer or user journey (awareness, consideration, decision, activation, expansion)
Escalation logic — how does the intensity, urgency, or value of each email build on the previous one?
Success definition — what specific action signals that the sequence has done its job and the recipient should exit?
2. Individual Email Design
For each email in the sequence, produce:
Subject Line
Provide 2-3 options per email
Vary approaches: curiosity, benefit-driven, urgency, personalization, question-based
Keep under 50 characters where possible; note preview behavior on mobile
Preview Text
40-90 characters that complement (not repeat) the subject line
Should add context or intrigue that increases open likelihood
Email Purpose
One sentence explaining why this email exists and what it moves the recipient toward
Body Copy
Full draft ready to use
Clear hierarchy: hook, body, CTA
Short paragraphs (2-3 sentences max)
Scannable formatting with bold key phrases where appropriate
Personalization tokens where relevant (e.g., first name, company name, product used)
Primary CTA
Button text and destination
One primary CTA per email (secondary CTA only if appropriate for the sequence stage)
Timing
Days after the trigger event or after the previous email
Note if timing should adjust based on engagement (e.g., "send sooner if they opened but did not click")
Segment/Condition Notes
Who receives this email vs. who skips it
Any behavioral or attribute-based conditions (e.g., "only send to users who have not completed setup")
3. Sequence Logic
Define the flow control for the sequence:
Branching conditions — alternate paths based on engagement. For example:
"If opened email 2 but did not click CTA, send email 2b (softer re-ask) instead of email 3"
"If clicked CTA in email 1, skip email 2 and go directly to email 3"
Exit conditions — when a recipient converts (completes the desired action), remove them from the sequence. Define what "conversion" means for this sequence.
Re-entry rules — can someone re-enter the sequence? Under what conditions? (e.g., "if a user churns again 90 days later, re-enter the win-back sequence")
Suppression rules — do not send if the recipient is already in another active sequence, has unsubscribed from marketing, or has contacted support in the last 48 hours
4. Performance Benchmarks
Provide expected benchmarks based on the sequence type so the user can set targets:
| Metric | Onboarding | Lead Nurture | Re-engagement | Win-back |
|---|---|---|---|---|
| Open rate | 50-70% | 20-30% | 15-25% | 15-20% |
| Click-through rate | 10-20% | 3-7% | 2-5% | 2-4% |
| Conversion rate | 15-30% | 2-5% | 3-8% | 1-3% |
| Unsubscribe rate | <0.5% | <0.5% | 1-2% | 1-3% |
Adjust benchmarks based on industry and audience if the user has provided that context.
Sequence Type Templates
Use these as starting frameworks. Adapt length and content based on the user's goal and audience.
Onboarding (5-7 emails over 14-21 days): Welcome and set expectations -- Quick win to demonstrate value -- Core feature deep dive -- Advanced feature or integration -- Social proof and community -- Check-in and feedback request -- Upgrade prompt or next steps
Lead Nurture (4-6 emails over 3-4 weeks): Value-first educational content -- Pain point identification -- Solution positioning with proof -- Social proof and results -- Soft CTA (trial, demo, resource) -- Direct CTA (buy, book, sign up)
Re-engagement (3-4 emails over 10-14 days): "We miss you" with a compelling reason to return -- Value reminder highlighting what they are missing -- Incentive or exclusive offer -- Last chance with clear deadline
Win-back (3-5 emails over 30 days): Friendly check-in asking what went wrong -- What is new since they left -- Special offer or incentive to return -- Feedback request (even if they do not come back) -- Final goodbye with door open
Product Launch (4-6 emails over 2-3 weeks): Teaser or pre-announcement -- Launch announcement with full details -- Feature spotlight or use case -- Social proof and early results -- Limited-time offer or bonus -- Last chance or reminder
Event Follow-up (3-4 emails over 7-10 days): Thank you with key takeaways or recordings -- Resource roundup from the event -- Related offer or next step -- Feedback survey
Upgrade/Upsell (3-5 emails over 2-3 weeks): Usage milestone or success celebration -- Feature gap or limitation they are hitting -- Upgrade benefits with proof -- Limited-time incentive -- Direct comparison of plans
Educational Drip (5-8 emails over 4-6 weeks): Introduction and what they will learn -- Lesson 1: foundational concept -- Lesson 2: intermediate concept -- Lesson 3: advanced concept -- Practical application or exercise -- Resource roundup -- Graduation and next steps
Tool Integration
If ~~email marketing is connected (e.g., Klaviyo, Mailchimp, Customer.io)
Reference how to set up the sequence as a flow or automation in the platform
Note any platform-specific features to use (e.g., smart send time, conditional splits, A/B testing)
Map the branching logic to the platform's visual flow builder concepts
If ~~marketing automation or ~~CRM is connected (e.g., HubSpot, Marketo)
Reference lead scoring data to inform segmentation and exit conditions
Use lifecycle stage data to tailor messaging per segment
Note how to set enrollment triggers based on CRM properties or list membership
If no tools are connected
Deliver all email content in copy-paste-ready format
Include a setup checklist the user can follow in any email platform:
Create the automation or flow
Set the enrollment trigger
Add each email with the specified delays
Configure branching and exit conditions
Set up tracking for the recommended metrics
Output
Present the complete sequence with the following sections:
Sequence Overview Table
| # | Subject Line | Purpose | Timing | Primary CTA | Condition |
|---|
Full Email Drafts
Each email with subject line options, preview text, purpose, body copy, CTA, timing, and segment notes.
Sequence Flow Diagram
A text-based diagram showing the email flow, branching paths, and exit points. Use a clear format such as:
[Trigger] --> Email 1 (Day 0)
|
Opened? --Yes--> Email 2 (Day 3)
| |
No Clicked CTA? --Yes--> [EXIT: Converted]
| |
v No
Email 1b (Day 2) |
| v
+--------> Email 3 (Day 7)
|
v
Email 4 (Day 10)
|
[EXIT: Sequence complete]Branching Logic Notes
Summary of all conditions, exits, and suppressions in a reference list.
A/B Test Suggestions
2-3 recommended A/B tests (subject lines, CTA text, send time, email length)
What to test, how to split, and how to measure the winner
Metrics to Track
Primary conversion metric for the sequence
Per-email metrics: open rate, CTR, unsubscribe rate
Sequence-level metrics: overall conversion rate, time to conversion, drop-off points
Recommended review cadence (e.g., "Review performance weekly for the first month, then monthly")
After the Sequence
Ask: "Would you like me to:
Revise the copy or tone for any specific email?
Add a branching path for a specific scenario?
Create a variation of this sequence for a different audience segment?
Draft the A/B test variants for the subject lines?
Build a companion sequence (e.g., a post-purchase follow-up after this lead nurture converts)?"
Files
- ATTRIBUTION.mdAdded by AutoGineer928 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md10.4 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · marketing/skills/email-sequence · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from marketing/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download email-sequence.zip