Email Sequence
Designs automated email sequences end to end: the trigger, branches and exit rules, the full copy of every message, and the sender setup that keeps them out of spam (SPF, DKIM, DMARC, one-click unsubscribe, consent). Covers onboarding and welcome series, lead nurture, abandoned cart, dunning, win-back and sunset flows. Use when someone asks for a "drip campaign", "welcome sequence", "onboarding emails", "nurture sequence", "win-back emails", "lifecycle emails", "email automation", or says "our emails land in spam" or "nobody clicks our onboarding emails". In-app onboarding belongs to onboardin
Install
npx skills add TerminalSkills/skills --skill email-sequencegit clone --depth 1 https://github.com/TerminalSkills/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/email-sequence ~/.claude/skills/email-sequencePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Email Sequence
## Overview
An email sequence is a small state machine: an event puts a person in, behaviour moves them between branches, and a goal event takes them out. Most weak sequences fail in the machine, not the prose: they keep selling to people who already bought, mail on a calendar regardless of what the person did, or never reach the inbox because the sending domain is not authenticated.
This skill produces three artifacts: a sequence specification an engineer can build in any email service, the complete copy of each message, and a sender-readiness check against the published requirements of Gmail, Yahoo and Outlook.
## Instructions
### 1. Establish the facts
Look in the project first: which email service is wired in, and which product events already exist.
```bash
grep -rniE "resend|postmark|sendgrid|customer\.?io|mailchimp|klaviyo|brevo|loops" package.json src/ | head -20
grep -rnE "track\(|identify\(|capture\(" src/ | head -20
```
Then ask for whatever is still unknown:
- The moment that starts the sequence and the single behaviour it should cause (the goal event).
- Who must not enter: existing customers, people without marketing consent, internal accounts.
- Every other email these people already get, and how often.
- Sending domain, daily volume, and the countries recipients live in.
- Proof the user is allowed to cite: real customer results, numbers, quotes.
### 2. Decide whether each message is commercial or transactionalDetails
- Skill name
email-sequence- Repository
- TerminalSkills/skills
- Path
skills/email-sequence/SKILL.md- License
- Apache-2.0
- Repo updated
- 8 November 2026
FAQ
What does the Email Sequence skill do?
Designs automated email sequences end to end: the trigger, branches and exit rules, the full copy of every message, and the sender setup that keeps them out of spam (SPF, DKIM, DMARC, one-click unsubscribe, consent). Covers onboarding and welcome series, lead nurture, abandoned cart, dunning, win-back and sunset flows. Use when someone asks for a "drip campaign", "welcome sequence", "onboarding emails", "nurture sequence", "win-back emails", "lifecycle emails", "email automation", or says "our emails land in spam" or "nobody clicks our onboarding emails". In-app onboarding belongs to onboardin
How do I install the Email Sequence skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TerminalSkills/skills --skill email-sequence. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Email Sequence popular?
It lives in TerminalSkills/skills, which has 213 GitHub stars and 34 forks.
Related skills
3dsmax Rendering
213TerminalSkills/skills
Scripts and configures production rendering in Autodesk 3ds Max with the V-Ray and Corona renderers: output size and files, render elements, denoising, light mix, batch and command-line rendering, and network rendering. Use when a user asks to set up a production render, render several cameras in one batch, render from the command line or on a render farm, add render passes for compositing, or cut render time for archviz and product shots.
3dsmax Scripting
213TerminalSkills/skills
Covers scripting Autodesk 3ds Max, the 3D modeling and rendering application, with MAXScript and Python (pymxs): scene manipulation, object creation, material assignment, camera and light setup, batch operations, and file I/O. Use when tasks involve automating repetitive 3ds Max workflows, batch processing scenes, running scripts headless with 3dsmaxbatch, creating custom tools, or scripting scene setup for archviz, product visualization, or VFX.
3proxy
213TerminalSkills/skills
3proxy is a small open-source proxy server that runs HTTP/HTTPS, SOCKS4/5, SNI and TCP/UDP port-mapping proxies from one config file. Use when a user asks to set up an HTTP or SOCKS5 proxy, add proxy users and passwords, write 3proxy access rules, chain or rotate upstream (parent) proxies, limit bandwidth, connections or monthly traffic per user, run 3proxy in Docker, or fix a 3proxy.cfg that will not start.
Environmental Scanning Foresight
200lyndonkl/claude
Monitors external trends across PESTLE dimensions, detects weak signals of emerging change, develops scenario-based futures, and sets adaptive signposts for early warning. Use when scanning external trends for strategic planning, detecting early indicators of change, planning scenarios for multiple futures, setting signposts and indicators for early warning, or when user mentions environmental scanning, horizon scanning, trend analysis, scenario planning, strategic foresight, or futures thinking.
Email Drafter
213TerminalSkills/skills
Draft professional emails for various business scenarios with appropriate tone and structure. Use when a user asks to write an email, compose a message, draft a reply, write a follow-up, create an outreach email, respond to a client, write a cold email, or craft any professional correspondence.
Facilitation Patterns
200lyndonkl/claude
Provides structured formats and techniques for running productive group sessions, from standups to multi-day workshops. Covers format selection, agenda design, participation management, decision methods, and handling difficult dynamics. Use when running meetings, workshops, brainstorms, design sprints, retrospectives, or team decision-making sessions, or when user mentions facilitation, workshop design, meeting patterns, session planning, or effective collaboration.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.