Localized reading guide
email-sequencePurpose, usage and source
Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A/B test suggestions, or when mapping a sequence end-to-end with a flow diagram.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
marketing/skills/email-sequence/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A/B test suggestions, or when mapping a sequence end-to-end with a flow diagram.
How the upstream workflow works
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.
Upstream passage · L7 ↗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:
Upstream passage · L17 ↗[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]Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Email Sequence
- Trigger
- Inputs
- 1. Sequence Strategy
- 2. Individual Email Design
- Subject Line
- Preview Text
- Email Purpose
- Body Copy
- Primary CTA
- Timing
- Segment/Condition Notes
- 3. Sequence Logic
- 4. Performance Benchmarks
- Sequence Type Templates
- If ~~email marketing is connected (e.g., Klaviyo, Mailchimp, Customer.io)
- If ~~marketing automation or ~~CRM is connected (e.g., HubSpot, Marketo)
- If no tools are connected
- Output
- Full Email Drafts
- Sequence Flow Diagram
- Branching Logic Notes
- A/B Test Suggestions
- Metrics to Track
- After the Sequence
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
4303252cbe340b19945b3e58d46430fdf42ea47b3e26d985e3ef1d6da5e36021