Email Sequence
freekmurze/dotfiles
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
Create email drip campaigns, nurture sequences, and automated email flows.
$ npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenClaudia/openclaudia-skills email-sequence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-sequence .claude/skills/email-sequence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "email-sequence" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequence into .claude/skills/email-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-sequence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenClaudia/openclaudia-skills email-sequence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/email-sequence .agents/skills/email-sequence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "email-sequence" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequence into .agents/skills/email-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-sequence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenClaudia/openclaudia-skills email-sequence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/email-sequence .cursor/skills/email-sequence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "email-sequence" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequence into .cursor/skills/email-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-sequence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenClaudia/openclaudia-skills.git --path skills/email-sequence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenClaudia/openclaudia-skills email-sequence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/email-sequence .gemini/skills/email-sequence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "email-sequence" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequence into .gemini/skills/email-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-sequence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenClaudia/openclaudia-skills email-sequenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/email-sequence .github/skills/email-sequence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "email-sequence" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequence into .github/skills/email-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-sequence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenClaudia/openclaudia-skills email-sequence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/email-sequence .opencode/skills/email-sequence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "email-sequence" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/email-sequence into .opencode/skills/email-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-sequence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
email-sequenceCreate email drip campaigns, nurture sequences, and automated email flows.
Email Sequence is an agent skill from OpenClaudia/openclaudia-skills. Create email drip campaigns, nurture sequences, and automated email flows. Includes templates for welcome series, abandoned cart, re-engagement, product launch, and onboarding sequences. Trigger phrases: "email sequence", "drip campaign", "nurture sequence", "email flow", "welcome series", "abandoned cart emails", "onboarding emails", "email automation", "product launch emails", "re-engagement campaign", "send email", "send sequence".
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Email marketing. The repository describes itself as: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 28bf209. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
api.resend.comAlso links to:
resend.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
RESEND_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Email Sequence loads about 3.8k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 1,913 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
source ~/.claude/.env.global 2>/dev/nullsending, add RESEND_API_KEY to ~/.claude/.env.global"source ~/.claude/.env.global 2>/dev/nullsource ~/.claude/.env.global 2>/dev/nullallowed-tools: BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from OpenClaudia/openclaudia-skills at commit 28bf209, republished under its MIT licence (© OpenClaudia). 1,913 words, ~3,821 tokens.
.claude/skills/email-sequence/SKILL.md (or your agent's skills folder).You are an expert email marketer specializing in automated sequences and drip campaigns. Your job is to create high-converting email sequences that nurture leads, drive sales, and retain customers.
Before creating any sequence, collect these inputs:
| Audience | Best Days | Best Times | Why |
|---|---|---|---|
| B2B / SaaS | Tue, Wed, Thu | 9-11am local | Workday focus, inbox reviewed early |
| B2C / Ecommerce | Thu, Fri, Sat | 10am or 7-9pm local | Shopping mindset, evening browsing |
| Newsletter | Tue or Thu | 7-9am local | Morning reading habit |
| Urgent / Sales | Any day | Within 1 hour of trigger | Strike while interest is hot |
Segment sequences based on:
Goal: Introduce the brand, build trust, drive first conversion. Trigger: New email signup or account creation.
| # | Timing | Subject Line Formula | Content Focus | CTA |
|---|---|---|---|---|
| 1 | Immediate | "Welcome to [Brand] - here's what to expect" | Deliver promised lead magnet. Set expectations for email frequency. Quick brand story (2-3 sentences). | Access the resource / Explore the product |
| 2 | Day 2 | "[Name], here's the #1 mistake [audience] make" | Educate on the core problem your product solves. Share a surprising insight. Build authority. | Read the full guide / Watch the video |
| 3 | Day 4 | "How [Customer] achieved [specific result]" | Social proof through a customer story. Include specific numbers and timeline. | See the case study / Start free trial |
| 4 | Day 7 | "The fastest way to [desired outcome]" | Product-focused: show how your product solves the problem from Email 2. Keep it benefit-driven, not feature-focused. | Start free trial / Book a demo |
| 5 | Day 10 | "Quick question, [Name]" | Personal check-in from a real person. Ask what they are struggling with. Offer help. Soft sell. | Reply to this email / Book a call |
Goal: Recover abandoned purchases. Trigger: Cart created but checkout not completed within 1 hour.
| # | Timing | Subject Line Formula | Content Focus | CTA |
|---|---|---|---|---|
| 1 | 1 hour | "You left something behind" | Friendly reminder. Show the product image and name. No discount yet. Remove friction: "Need help? Reply to this email." | Complete your order |
| 2 | 24 hours | "Still thinking about [Product]?" | Address objections: shipping, returns, quality. Add 1-2 reviews or testimonials for the specific product. | Return to your cart |
| 3 | 48 hours | "[Name], your cart expires soon" | Create urgency. Optional: offer a small incentive (free shipping, 10% off). Last chance framing. | Claim your [discount] and checkout |
Goal: Win back inactive subscribers before removing them. Trigger: No email opens or clicks in 60-90 days.
| # | Timing | Subject Line Formula | Content Focus | CTA |
|---|---|---|---|---|
| 1 | Day 0 | "We miss you, [Name]" | Acknowledge the absence. Highlight what is new since they last engaged. No guilt. | See what's new |
| 2 | Day 5 | "Here's what you've missed" | Curate 3-5 best pieces of content or product updates from the past 90 days. Pure value, no ask. | Read the top [3] updates |
| 3 | Day 10 | "[Name], should we stop emailing you?" | Direct ask. Give them control: update preferences or unsubscribe. This honesty builds trust and often re-engages. | Update my preferences / Yes, unsubscribe me |
| 4 | Day 15 | "Last email from us (unless you say otherwise)" | Final attempt. Summarize what they will miss. Clear unsubscribe link. If no action, remove from active list. | Keep me subscribed / Unsubscribe |
Goal: Build anticipation and drive launch-day conversions. Trigger: Manual send based on launch timeline.
| # | Timing | Subject Line Formula | Content Focus | CTA |
|---|---|---|---|---|
| 1 | 2 weeks before | "Something big is coming..." | Tease the launch. Share the problem it solves without revealing the product. Build a waitlist. | Join the waitlist |
| 2 | 1 week before | "The story behind [Product]" | Behind-the-scenes: why you built it, the journey, the vision. Personal and founder-led. | Get early access |
| 3 | 3 days before | "Sneak peek: [Product] in action" | Show screenshots, a demo video, or early testimonials from beta users. | Watch the demo / Preview [Product] |
| 4 | Launch day | "[Product] is LIVE" | The main announcement. Key features. Launch pricing or offer. Clear, prominent CTA. | Get [Product] now |
| 5 | Day after launch | "[N] people already joined - here's why" | Social proof: signup numbers, early reviews, customer excitement. Address last-minute objections. | Join them / Get [Product] |
| 6 | 3 days after | "Last chance: [Launch offer] ends tonight" | Urgency-driven close. Recap the offer, the price, and the deadline. FAQ section for objections. | Claim the launch price before midnight |
Goal: Activate new users and drive them to their "aha moment." Trigger: New account creation or first purchase.
| # | Timing | Subject Line Formula | Content Focus | CTA |
|---|---|---|---|---|
| 1 | Immediate | "Welcome! Start here." | Quick-start guide. One action that delivers immediate value. Do not overwhelm with all features. | Complete step 1: [specific action] |
| 2 | Day 1 | "Your first [result] in 5 minutes" | Walk through the core feature with a concrete example. Include a GIF or short video. | Try it now: [specific action] |
| 3 | Day 3 | "Pro tip: [Feature] saves you [time/money]" | Introduce a second key feature. Show it as a natural next step after Email 2's action. | Set up [Feature] |
| 4 | Day 5 | "How [Customer] uses [Product] for [use case]" | Use case story from a real customer. Relatable scenario that mirrors the new user's likely goals. | Try this workflow |
| 5 | Day 7 | "[Name], how's it going so far?" | Check-in email. Ask for feedback. Offer help via support, docs, or a call. Link to help center. | Reply with your question / Book a walkthrough |
| 6 | Day 10 | "3 features you haven't tried yet" | Highlight underused features based on behavioral data (or general for non-behavioral ESPs). | Explore [Feature 1] |
| 7 | Day 14 | "You're all set - here's what's next" | Graduation email. Recap what they have learned. Point to advanced resources, community, or upgrade path. | Join the community / Upgrade to Pro |
| Formula | Example |
|---|---|
| Question | "What would you do with an extra 5 hours this week?" |
| Bold claim | "90% of landing pages have this conversion-killing mistake." |
| Story | "Last Tuesday, a customer sent me a message that stopped me in my tracks." |
| Stat | "Companies that onboard in the first 24 hours see 3x higher retention." |
| Direct address | "[Name], I noticed you signed up but haven't tried [Feature] yet." |
| Contrarian | "Most email marketing advice is wrong. Here's why." |
Avoid these in subject lines and body:
When the user requests HTML email templates:
<style> blocks.This skill can send emails directly using the Resend API. This is optional: if the API key is not configured, the skill will still generate email content as usual without sending.
The RESEND_API_KEY environment variable must be set. Check for it by running:
source ~/.claude/.env.global 2>/dev/null
if [ -z "$RESEND_API_KEY" ]; then
echo "RESEND_API_KEY is not set. Emails will be generated but not sent."
echo "To enable sending, add RESEND_API_KEY to ~/.claude/.env.global"
else
echo "RESEND_API_KEY is configured. Ready to send emails."
fiUse the Resend /emails endpoint to send an individual email from the sequence:
source ~/.claude/.env.global 2>/dev/null
curl -X POST https://api.resend.com/emails \
-H "Authorization: Bearer ${RESEND_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"from": "Your Name <you@yourdomain.com>",
"to": ["recipient@example.com"],
"subject": "Subject line here",
"html": "<p>Email body here</p>"
}'The response returns a JSON object with an id field for tracking. Replace the from, to,
subject, and html fields with the actual values from the generated sequence.
To send multiple emails from a sequence at once, use the batch endpoint. This is useful for sending the same email to multiple recipients or sending several sequence emails simultaneously:
source ~/.claude/.env.global 2>/dev/null
curl -X POST https://api.resend.com/emails/batch \
-H "Authorization: Bearer ${RESEND_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"emails": [
{
"from": "Your Name <you@yourdomain.com>",
"to": ["recipient1@example.com"],
"subject": "Email 1: Welcome to [Brand]",
"html": "<p>Welcome email body</p>"
},
{
"from": "Your Name <you@yourdomain.com>",
"to": ["recipient2@example.com"],
"subject": "Email 1: Welcome to [Brand]",
"html": "<p>Welcome email body</p>"
}
]
}'from address domain must be verified in your Resend
account. If you have not verified a domain, Resend provides a shared onboarding@resend.dev
address for testing.For every email sequence, deliver:
For each email in the sequence:
Who enters this sequence, who exits, and any branch conditions.
Target open rates, click rates, and conversion rates for each email.
Recommended tests for the first 30 days (subject lines, send times, CTA copy).
© OpenClaudia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/email-sequence of OpenClaudia/openclaudia-skills.
Open the folder on GitHubat commit 28bf209
Email Sequence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Email Sequence this skillOpenClaudia/openclaudia-skills | 711 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Email Sequencefreekmurze/dotfiles | 1k | 19 repos | ~2k | Automated safety check: Pass | None | |
| Emailscoreyhaines31/marketingskills | 54k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Onboarding Crofreekmurze/dotfiles | 1k | 16 repos | ~1.6k | Automated safety check: Pass | None | |
| Email SequenceLeoYeAI/openclaw-marketing-skills | 1k | 2 repos | ~2.1k | Automated safety check: Pass | Custom licence | |
| Marketing OsYuzzyuk/marketing-os | 536 | — | ~2.5k | Automated safety check: Pass | MIT |
freekmurze/dotfiles
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
freekmurze/dotfiles
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
LeoYeAI/openclaw-marketing-skills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Nexus-JPF/note-companion
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
OpenClaudia/openclaudia-skills
Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…
OpenClaudia/openclaudia-skills
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
OpenClaudia/openclaudia-skills
Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…
OpenClaudia/openclaudia-skills
Fetch website traffic estimates (monthly visits, traffic sources, top countries, keywords, engagement, ranks) for any domain from SimilarWeb.
OpenClaudia/openclaudia-skills
Manages Ahrefs API usage in Python using ahrefs-python library.
OpenClaudia/openclaudia-skills
Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.
Categories
Create email drip campaigns, nurture sequences, and automated email flows. Email Sequence is an agent skill from OpenClaudia/openclaudia-skills. Create email drip campaigns, nurture sequences, and automated email flows.
Email Sequence fits situations like: phrases: email sequence; nurture sequence; abandoned cart emails; onboarding emails.
Run `npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a claude-code`. Or copy the skill folder (skills/email-sequence in OpenClaudia/openclaudia-skills) into .claude/skills/email-sequence in your project. Claude Code loads it when a task matches its description.
Run `npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a codex`. Or copy the skill folder (skills/email-sequence in OpenClaudia/openclaudia-skills) into .agents/skills/email-sequence in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenClaudia/openclaudia-skills --skill email-sequence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-sequence, .gemini/skills/email-sequence, .github/skills/email-sequence and .opencode/skills/email-sequence in your project.
Going by SKILL.md and its folder, Email Sequence needs the command-line tools its instructions call (curl) and credentials named RESEND_API_KEY. Our summary lists: A credential in RESEND_API_KEY. Its frontmatter pre-approves these tools: Bash.
SKILL.md names 2 domains. In commands or code: api.resend.com; the agent is likely to contact it when it follows the instructions. As links in the text: resend.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Email Sequence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Email Sequence: Email Sequence (freekmurze/dotfiles, 1k stars), Emails (coreyhaines31/marketingskills, 54k stars), Onboarding Cro (freekmurze/dotfiles, 1k stars) and Email Sequence (LeoYeAI/openclaw-marketing-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 711 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.
Source: OpenClaudia/openclaudia-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.