Email Sequence
freekmurze/dotfiles
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
Design and write email automation sequences (welcome/onboarding, nurture, re-engagement, trial expiration, sales) for SaaS and B2B, with subject lines, copy, CTAs, and timing.
$ npx skills add borghei/Claude-Skills --skill email-sequence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-Skills --skill email-sequence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills email-sequence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-Skills --skill email-sequence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills email-sequence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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/borghei/Claude-Skills.git --path marketing/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 borghei/Claude-Skills --skill email-sequence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-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/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-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 borghei/Claude-Skills --skill email-sequence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-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 borghei/Claude-Skills email-sequence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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-sequenceDesign and write email automation sequences (welcome/onboarding, nurture, re-engagement, trial expiration, sales) for SaaS and B2B, with subject lines, copy, CTAs, and timing.
Email Sequence is an agent skill from borghei/Claude-Skills. Design and write email automation sequences (welcome/onboarding, nurture, re-engagement, trial expiration, sales) for SaaS and B2B, with subject lines, copy, CTAs, and timing. Use when building drip campaigns or designing lifecycle email.
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/performance_analyzer.py`, `scripts/sequence_mapper.py` and `scripts/subject_line_scorer.py`).
It sits in Marketing & SEO, covering Email marketing. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
apple.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Email Sequence loads about 4.2k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 1,858 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 found no risky patterns in SKILL.md.
Automated 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); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 1,858 words, ~4,216 tokens.
.claude/skills/email-sequence/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Category: Marketing Tags: email sequences, drip campaigns, nurture flows, onboarding emails, lifecycle marketing, automation
Email Sequence Design creates complete, ready-to-implement email automation flows. Every output includes subject lines, preview text, full body copy, CTAs, send timing, and exit conditions. The goal is sequences that nurture relationships and drive specific conversion actions -- not just "stay top of mind" email noise.
This skill writes the sequences. For email HTML templates and rendering infrastructure, use email-template-builder. For tracking email performance, use analytics-tracking.
| Type | Trigger | Goal | Typical Length |
|---|---|---|---|
| Welcome/Onboarding | New signup | Activate user, show core value | 5-7 emails over 14 days |
| Trial Expiration | Trial nearing end | Convert to paid | 4-5 emails over 7 days |
| Lead Nurture | Content download, webinar | Qualify and convert | 6-8 emails over 30 days |
| Re-engagement | Inactive 30+ days | Bring back or clean list | 3-4 emails over 14 days |
| Post-Purchase | Subscription start | Reduce churn, expand | 4-6 emails over 30 days |
| Event-Based | Specific user action | Drive next action | 2-3 emails over 7 days |
| Sales (Warm) | MQL or PQL signal | Book meeting or start trial | 4-5 emails over 14 days |
Before designing the sequence, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Before writing any email, define the architecture:
Sequence Name: [Name]
Trigger: [What starts the sequence]
Primary Goal: [Single conversion action]
Secondary Goals: [Relationship building, data collection]
Length: [Number of emails]
Duration: [Total time span]
Exit Conditions: [When they leave the sequence]
Suppression: [Other sequences to suppress while active]Each email serves a purpose in a progression:
| Emotional State | Purpose | Key Message | |
|---|---|---|---|
| 1 | Curious, uncertain | Welcome, set expectations | "Here's what to expect" |
| 2 | Exploring, evaluating | Demonstrate core value | "Here's the one thing to try first" |
| 3 | Engaged or dropping off | Social proof | "Here's how others succeeded" |
| 4 | Considering commitment | Remove objections | "Common concerns addressed" |
| 5 | Ready to decide | Create urgency | "Your trial ends in X days" |
For every email in the sequence, deliver:
Email [#]: [Name/Purpose]
Send: [Timing from trigger or previous email]
Segment: [Conditions -- who receives this variant]
Subject: [Subject line - under 50 characters]
Preview: [Preview text - 80-120 characters, complements subject]
Body:
[Complete copy -- not an outline, not bullets, the actual words]
CTA: [Button text] → [Destination URL]
P.S.: [Optional -- works for urgency or human touch]Not everyone follows the same path. Define branches:
After Email 2:
IF user activated core feature → Skip to Email 4 (post-activation)
IF user has not logged in → Send Email 2B (re-engagement variant)
IF user unsubscribed → Exit sequence
After Email 4:
IF user converted → Exit sequence, enter post-purchase sequence
IF user visited pricing 2+ times → Send Email 4B (pricing objection handler)
ELSE → Continue to Email 5| Day | Subject | Purpose | |
|---|---|---|---|
| 1 | 0 (immediate) | Welcome to [Product] -- start here | Set expectations, one CTA to activate |
| 2 | 1 | The one feature that changes everything | Drive to core value action |
| 3 | 3 | How [Company] got [Result] in [Timeframe] | Social proof, case study |
| 4 | 5 | Quick question | Check engagement, offer help |
| 5 | 7 | 3 things you might have missed | Feature discovery, breadth |
| 6 | 10 | Your trial is halfway done | Progress report, urgency |
| 7 | 13 | Last day of your trial | Convert or lose access |
Exit conditions: User converts to paid at any point, user unsubscribes, user explicitly requests removal.
Branching:
| Day | Subject | Purpose | |
|---|---|---|---|
| 1 | 0 | Your [resource name] is ready | Deliver promised content |
| 2 | 3 | The mistake most [role] make with [topic] | Educational, establish authority |
| 3 | 7 | [Company] went from [problem] to [result] | Case study, social proof |
| 4 | 14 | The [topic] framework we use internally | Exclusive value, reciprocity |
| 5 | 21 | Quick question about [their challenge] | Personal, segmentation |
| 6 | 28 | See if [Product] is right for you | Soft CTA, demo or trial |
Exit conditions: Books demo, starts trial, unsubscribes, or completes sequence.
| Day | Subject | Purpose | |
|---|---|---|---|
| 1 | 0 | We noticed you've been away | Acknowledge absence, show value |
| 2 | 3 | Here's what you missed | Product updates, new features |
| 3 | 7 | [Exclusive offer or incentive] | Incentivize return |
| 4 | 14 | Should we stop emailing you? | Clean list, last chance |
Critical rule: If no engagement after Email 4, remove from active email list. Sending to unengaged contacts damages sender reputation.
| Day Before Expiry | Subject | Purpose | |
|---|---|---|---|
| 1 | 7 | Your trial ends in one week | Awareness, usage summary |
| 2 | 3 | Here's what you'll lose access to | Loss aversion, feature list |
| 3 | 1 | Tomorrow is your last day | Urgency, simple CTA |
| 4 | 0 | Your trial just ended | Conversion, offer extension option |
| 5 | +3 | We saved your data for 30 days | Last chance, data retention |
| Formula | Example | Why It Works |
|---|---|---|
| How [company] [achieved result] | "How Stripe reduced churn 23%" | Specific, curiosity, social proof |
| The [number] [thing] [audience] [needs] | "The 3 metrics every PM tracks" | Specific, relevant, scannable |
| Quick question about [topic] | "Quick question about your trial" | Personal, non-threatening |
| [Name], [action-oriented statement] | "Sarah, your dashboard is ready" | Personal, action-oriented |
| Your [asset] is [status] | "Your free trial ends tomorrow" | Ownership, urgency |
| Day | Time Window | Notes |
|---|---|---|
| Tuesday | 9-11 AM recipient's timezone | Highest open rates |
| Wednesday | 9-11 AM | Second best |
| Thursday | 9-11 AM | Good for follow-ups |
| Monday | 10 AM-12 PM | After inbox clearing |
| Friday | Avoid for important emails | Low engagement |
| Weekend | Avoid for B2B | Exception: consumer products |
| Metric | Welcome | Nurture | Re-engagement | Trial Expiration |
|---|---|---|---|---|
| Open rate (directional only) | 50-70% | 25-40% | 15-25% | 40-60% |
| Click rate | 10-20% | 3-8% | 2-5% | 8-15% |
| Conversion rate | 5-15% | 1-3% | 3-8% | 10-25% |
| Unsubscribe rate | <0.5% | <0.3% | 1-3% | <0.5% |
Open rates are inflated and unreliable. Apple Mail Privacy Protection downloads remote content (including tracking pixels) in the background by default, whether or not the recipient reads the email (Apple — Mail Privacy Protection). Opens from Apple Mail users register as "opens" regardless of engagement, and some security scanners do the same. Treat opens as a directional signal only; judge sequences on clicks, replies, conversions, unsubscribes/complaints, and inbox placement. Exclude machine opens (where your ESP flags them) before comparing to any open-rate benchmark.
| Signal | Meaning | Action |
|---|---|---|
| Click rate declining across sequence | Fatigue or irrelevance | Shorten sequence, sharpen each email's single CTA |
| High opens, low clicks | Body/CTA doesn't land — or opens are machine-inflated (Apple MPP) | Check opens excluding machine opens; rewrite body copy, simplify CTA |
| High click rate, low conversion | Landing page problem | Audit post-click experience |
| Rising unsubscribes after Email 3 | Too frequent or too salesy | Increase spacing, add more value |
| Email 1 low clicks and replies, or rising spam-folder placement | Deliverability issue | Run an inbox placement / seed test, check sender reputation (e.g., Google Postmaster Tools) and SPF/DKIM/DMARC |
| Segment | Definition | Sequence Adjustment |
|---|---|---|
| Power users | Used core feature 5+ times | Skip beginner content, focus on advanced features |
| Window shoppers | Signed up, never activated | More hand-holding, simpler first steps |
| Pricing page visitors | Viewed pricing 2+ times | Address pricing objections directly |
| Feature explorers | Used 3+ features | Highlight integration and workflow value |
| Ghost users | No login in 7+ days | Re-engagement sequence |
| Tier | Effort | Impact | Example |
|---|---|---|---|
| 1: Name + company | Low | Moderate | "Hi Sarah, how's the Acme team finding..." |
| 2: Behavioral | Medium | High | "Since you set up your first project..." |
| 3: Segment-specific copy | High | Highest | Entirely different email body per segment |
| Skill | Use When |
|---|---|
| email-template-builder | Building HTML email templates and rendering infrastructure |
| analytics-tracking | Setting up email click tracking and UTM attribution |
| launch-strategy | Coordinating email sequences around product launches |
| content-creator | Writing landing page copy that email CTAs point to |
| ab-test-setup | Designing statistically valid email A/B tests |
| Symptom | Likely Cause | Fix |
|---|---|---|
| Welcome email low click rate or poor inbox placement | Deliverability issue or weak subject/offer | Run an inbox placement test; check sender reputation and SPF/DKIM/DMARC. Test subject variants and judge them on clicks, not opens. |
| Clicks declining across sequence | Fatigue or irrelevance | Shorten sequence, improve subject lines, or add more value per email. |
| High opens, low clicks | Body copy or CTA is weak, or opens inflated by Apple MPP | Check machine-open-excluded opens; rewrite body with stronger benefit and simplify CTA to one action. |
| High click rate, low conversion | Landing page problem | Audit post-click experience: message match, page speed, form friction. |
| Rising unsubscribes after email 3 | Too frequent or too salesy | Increase spacing between emails and add more educational content. |
| Emails clipped by Gmail | HTML template over 102KB | Use render_size_analyzer.py from email-template-builder to reduce size. |
| Sequence not triggering | Automation platform misconfiguration | Verify trigger events, check suppression rules for conflicts. |
In Scope: Lifecycle email sequence design, copy, timing, branching logic, segmentation, and performance optimization for SaaS/B2B.
Out of Scope: Email HTML rendering (use email-template-builder), cold outreach sequences (use cold-email), marketing automation platform setup, transactional email infrastructure.
Limitations: Benchmarks are SaaS/B2B focused. Adjust thresholds for e-commerce, consumer, or other verticals.
scripts/subject_line_scorer.py)Scores sequence email subject lines for open-rate potential and auto-detects sequence type (welcome, trial, nurture, re-engagement).
python scripts/subject_line_scorer.py "Your trial ends tomorrow"
python scripts/subject_line_scorer.py --file subjects.txt --jsonscripts/sequence_mapper.py)Generates a visual sequence map with timing, branching logic, and exit conditions from a sequence definition.
python scripts/sequence_mapper.py sequence_def.json
python scripts/sequence_mapper.py --sample --jsonscripts/performance_analyzer.py)Analyzes email sequence metrics against benchmarks, identifies bottlenecks, and recommends optimizations.
python scripts/performance_analyzer.py metrics.json
python scripts/performance_analyzer.py --sample --json© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in marketing/email-sequence of borghei/Claude-Skills.
Open the folder on GitHubat commit c9a1487
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 skillborghei/Claude-Skills | 874 | — | ~4.2k | Automated safety check: Pass | MIT | |
| Email Sequencefreekmurze/dotfiles | 1k | 18 repos | ~2k | Automated safety check: Pass | None | |
| Email SequenceLeoYeAI/openclaw-marketing-skills | 1k | 2 repos | ~2.1k | Automated safety check: Pass | Custom licence | |
| Onboarding Crofreekmurze/dotfiles | 1k | 15 repos | ~1.6k | Automated safety check: Pass | None | |
| Marketing OsYuzzyuk/marketing-os | 535 | — | ~2.5k | Automated safety check: Pass | MIT | |
| OnboardingNexus-JPF/note-companion | 869 | 3 repos | ~1.6k | 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.
LeoYeAI/openclaw-marketing-skills
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.
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.
irinabuht12-oss/email-campaigns-claude
Design, build, and send beautiful HTML email campaigns via Resend.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
Design and write email automation sequences (welcome/onboarding, nurture, re-engagement, trial expiration, sales) for SaaS and B2B, with subject lines, copy, CTAs, and timing. Email Sequence is an agent skill from borghei/Claude-Skills. Design and write email automation sequences (welcome/onboarding, nurture, re-engagement, trial expiration, sales) for SaaS and B2B, with subject lines, copy, CTAs, and timing.
Email Sequence fits situations like: building drip campaigns; designing lifecycle email.
Run `npx skills add borghei/Claude-Skills --skill email-sequence -a claude-code`. Or copy the skill folder (marketing/email-sequence in borghei/Claude-Skills) into .claude/skills/email-sequence in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill email-sequence -a codex`. Or copy the skill folder (marketing/email-sequence in borghei/Claude-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 borghei/Claude-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 Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md names 1 domain. As links in the text: apple.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Email Sequence is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.2k tokens (SKILL.md is roughly 17k 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), Email Sequence (LeoYeAI/openclaw-marketing-skills, 1k stars), Onboarding Cro (freekmurze/dotfiles, 1k stars) and Marketing Os (Yuzzyuk/marketing-os, 535 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.