Install the "email-drip-sequence" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/distribution/email-drip-sequence into .claude/skills/email-drip-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-drip-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.
Type 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.
skills CLI
$ npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "email-drip-sequence" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/distribution/email-drip-sequence into .agents/skills/email-drip-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-drip-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.
skills CLI
$ npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "email-drip-sequence" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/distribution/email-drip-sequence into .cursor/skills/email-drip-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-drip-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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "email-drip-sequence" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/distribution/email-drip-sequence into .gemini/skills/email-drip-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-drip-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.
Installs 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).
skills CLI
$ npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "email-drip-sequence" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/distribution/email-drip-sequence into .github/skills/email-drip-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-drip-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.
skills CLI
$ npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "email-drip-sequence" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/distribution/email-drip-sequence into .opencode/skills/email-drip-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-drip-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.
Facts
Skill name
email-drip-sequence
GitHub stars
699
Token cost
~3k tokens
SKILL.md length
1,174 words
Files
2
Skills in repo
50
Repo updated
First seen
Licence
MIT
At a glance
Write an email drip sequence for affiliate marketing. An agent skill from Affitor/affiliate-skills.
Works in 6 steps: Gather Information → Plan the Sequence → Write Each Email → …
: write me an email sequence
SKILL.md covers Stage, When to Use, Input Schema and Workflow, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Email Drip Sequence is an agent skill from Affitor/affiliate-skills. Write an email drip sequence for affiliate marketing. Triggers on: "write me an email sequence", "create a drip campaign", "email nurture sequence", "affiliate email funnel", "welcome email series", "email onboarding sequence", "write emails for my list", "set up a drip sequence", "email campaign for [product]", "nurture my subscribers", "email follow-up sequence", "build my email funnel", "write 5 emails promoting [product]", "email automation sequence".
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file. Compatibility notes: Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
It sits in Marketing & SEO, covering Email marketing and Influencer and creator marketing. The repository describes itself as: 50 AI agent skills for affiliate marketing. Research trending content, write data-backed posts, generate infographics, build landing pages, deploy — full flywheel with social… The licence is MIT.
When your agent uses it
: write me an email sequence
Create a drip campaign
Email nurture sequence
Affiliate email funnel
Example prompts
“write me an email sequence”
“create a drip campaign”
“email nurture sequence”
“/email-drip-sequence”
Requirements
Compatibility (from SKILL.md): Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e43bfae. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
From compatibility in the SKILL.md frontmatter.
Context cost
Email Drip Sequence loads about 3k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 1,174 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~120
When it runs· the whole SKILL.md, loaded when a task matches
~3k
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.
Safety
Auto-check passed
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); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/email-drip-sequence/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
email-drip-sequence
description
Write an email drip sequence for affiliate marketing. Triggers on: "write me an email sequence", "create a drip campaign", "email nurture sequence", "affiliate email funnel", "welcome email series", "email onboarding sequence", "write emails for my list", "set up a drip sequence", "email campaign for [product]", "nurture my subscribers", "email follow-up sequence", "build my email funnel", "write 5 emails promoting [product]", "email automation sequence".
compatibility
Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
Write a 5-7 email drip sequence that nurtures new subscribers from cold to warm to buyer. Follows the Welcome → Value → Value → Soft Sell → Hard Sell → Objection Handling → Follow-Up pattern. Each email includes subject line, preview text, body copy, and a single clear CTA.
Stage
S5: Distribution — Email is the highest-ROI channel for affiliate marketers (avg $42 return per $1 spent). This skill turns a list of subscribers into a predictable revenue stream by delivering value first and selling second.
When to Use
User has an email list and wants to promote an affiliate product
User just launched a lead magnet or opt-in form and needs a welcome sequence
User wants to automate affiliate promotions via email automation (ConvertKit, Mailchimp, Beehiiv, ActiveCampaign, etc.)
User says anything like "email sequence", "drip campaign", "email funnel", "nurture series"
User wants a sequence for a specific product or niche
Chaining from S1 (research) — user found a product and now wants an email sequence for it
Input Schema
yaml
product:
name: string # REQUIRED — product name (e.g., "HeyGen")
affiliate_url: string # REQUIRED — the affiliate link to promote
category: string # OPTIONAL — product category (e.g., "AI video tool")
reward_value: string # OPTIONAL — commission amount/percentage (e.g., "30% recurring")
key_benefits: string[] # OPTIONAL — top 3 benefits. Auto-researched if not provided.
price: string # OPTIONAL — product pricing (e.g., "$29/mo")
audience:
description: string # REQUIRED — who are the subscribers? (e.g., "content creators", "SaaS founders")
pain_point: string # OPTIONAL — main problem they want solved
awareness_level: string # OPTIONAL — "cold" | "warm" | "hot". Default: "cold"
sequence:
length: number # OPTIONAL — number of emails: 5, 6, or 7. Default: 7
send_days: number[] # OPTIONAL — days to send (e.g., [0, 1, 3, 5, 7, 10, 14])
# Default: [0, 1, 3, 5, 7, 10, 14]
sender_name: string # OPTIONAL — from name (e.g., "Alex from ContentPro")
tone: string # OPTIONAL — "conversational" | "professional" | "bold"
# Default: "conversational"
lead_magnet: string # OPTIONAL — what they opted in for (e.g., "AI tools checklist")
Chaining context: If S1 (product research) was run earlier in the conversation, pull product.name, product.affiliate_url, product.key_benefits, and product.reward_value automatically. Do not ask the user to repeat information already provided.
Workflow
Step 1: Gather Information
Collect required inputs. If product.name and product.affiliate_url are present (from user or S1 chain), proceed. Otherwise ask:
"What product are you promoting and what's your affiliate link?"
"Who are your subscribers? (e.g., freelancers, SaaS founders, content creators)"
If product.key_benefits is not provided, infer 3 benefits from the product name and category using your training knowledge. State: "Based on what I know about [product], I'm using these key benefits: [list]. Correct me if needed."
Step 2: Plan the Sequence
Map each email to its purpose using the 7-email arc. For a 5-email sequence, drop emails 6 and 7. For a 6-email sequence, drop email 7.
#
Day
Type
Purpose
1
0
Welcome
Deliver lead magnet, set expectations, build trust
2
1
Value
Teach something useful (no sell)
3
3
Value + Soft Mention
More value, casual mention of the product
4
5
Soft Sell
Introduce the product properly, benefits focus
5
7
Hard Sell
Clear CTA, urgency (limited offer / deadline if available)
6
10
Objection Handling
Answer top 3 objections, social proof
7
14
Follow-Up / Last Chance
"Did you see this?" re-engagement email
Step 3: Write Each Email
For each email, write all four components:
Subject Line: 40-60 characters. Use curiosity, specificity, or direct benefit. Avoid spam trigger words (free, guaranteed, act now).
Preview Text: 80-100 characters. Extends the subject line, adds context or intrigue. Shown in inbox preview.
Body Copy:
Email 1-2: 200-300 words. Focus on value, zero sell pressure.
Email 3-4: 250-350 words. Introduce product naturally in context.
After all emails, provide the Setup Instructions section.
Step 6: Self-Validation
Before presenting output, verify:
All 5-7 emails present with subject, preview text, body, and CTA
FTC disclosure included on every email containing affiliate links
Email spacing is logical (not all on day 1)
Value emails outnumber pitch emails in the sequence
CTA links point to correct affiliate URLs
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
Show full SKILL.md (464 more words)Show less
Output Schema
yaml
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
sequence:
product_name: string
affiliate_url: string
audience: string
email_count: number
total_days: number # span of the sequence in days
emails:
- number: number # 1-7
day: number # send delay in days from signup
type: string # welcome | value | soft-sell | hard-sell | objection | follow-up
subject: string
preview_text: string
body: string # full email body
cta_text: string # button/link text
cta_url: string # affiliate link or engagement action
setup:
recommended_esp: string[] # e.g., ["ConvertKit", "Beehiiv", "ActiveCampaign"]
automation_notes: string # how to set up the delay/trigger logic
ab_test_suggestion: string # what to A/B test first
Output Format
Present the sequence as clearly separated email blocks (as shown in Step 5). After the last email, add a Setup Instructions section:
---
SETUP INSTRUCTIONS
---
ESP Recommendations: ConvertKit, Beehiiv, or ActiveCampaign
Trigger: New subscriber joins list / completes opt-in form
Delays: Set each email to fire X days after the previous
A/B Test First: Subject lines on Email 5 (the hard sell) — highest impact
Tag to apply: Add an "affiliate-[product]" tag to track clicks in your ESP
---
Error Handling
No affiliate URL provided: "I'll write the sequence structure now. Drop in your affiliate link where I've marked [YOUR_AFFILIATE_LINK] before setting it up in your ESP."
Unknown product: Research the product using web search if possible. If not found, ask: "Can you tell me the top 2-3 benefits of [product]? I'll write the sequence around those."
Audience too vague ("everyone"): Default to "online business owners and marketers." Note: "I used a general audience. For better conversions, replace 'you' with specific language like 'as a freelancer...' or 'for SaaS founders...' throughout."
No lead magnet info: Email 1 defaults to a "welcome + what to expect" format rather than lead magnet delivery.
Request for 3 emails or fewer: "A 3-email sequence is too short to build trust before the sell. I recommend at least 5. Want me to write a 5-email version?"
Examples
Example 1: Product + audience provided
User: "Write an email sequence for HeyGen (my link: heygen.com/ref/abc123) targeting YouTube creators who opted in for my AI tools checklist."
Action: 7-email sequence, Day 0 delivers checklist, emails 2-3 teach AI video creation tips, emails 4-7 pitch HeyGen with creator-specific angles (save editing time, AI avatars, multilingual).
Example 2: Chained from S1
Context: S1 found Semrush with 30% recurring commission targeting SEO consultants.
User: "Now write an email sequence for this."
Action: Pull product details from S1 output. Write 7-email sequence targeting SEO consultants. Lead magnet assumed to be SEO-related content.
Example 3: Minimal input
User: "Write me a drip sequence for my Notion template affiliate program"
Action: Ask for affiliate URL and audience. Use Notion affiliate program knowledge for benefits. Write 5-email sequence (conservative default for shorter products with simpler buying journey).
References
shared/references/ftc-compliance.md — FTC affiliate disclosure requirements. Apply to every email containing an affiliate link.
shared/references/affitor-branding.md — Affitor footer. Include in plain text footer of each email.
Email Drip 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.
Email Drip Sequence compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Email Drip Sequence this skillAffitor/affiliate-skills
A skill your agent uses when the user wants to build an ongoing marketing engine, create a content strategy, set up social media publishing, plan influencer partnerships, or run email and paid ad…
Write an email drip sequence for affiliate marketing. An agent skill from Affitor/affiliate-skills. Email Drip Sequence is an agent skill from Affitor/affiliate-skills. Write an email drip sequence for affiliate marketing.
When should I use Email Drip Sequence?
Email Drip Sequence fits situations like: : write me an email sequence; create a drip campaign; email nurture sequence; affiliate email funnel.
How do I install Email Drip Sequence in Claude Code?
Run `npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a claude-code`. Or copy the skill folder (skills/distribution/email-drip-sequence in Affitor/affiliate-skills) into .claude/skills/email-drip-sequence in your project. Claude Code loads it when a task matches its description.
How do I install Email Drip Sequence in Codex?
Run `npx skills add Affitor/affiliate-skills --skill email-drip-sequence -a codex`. Or copy the skill folder (skills/distribution/email-drip-sequence in Affitor/affiliate-skills) into .agents/skills/email-drip-sequence in your project. Codex loads it when a task matches its description.
Can I use Email Drip Sequence in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Affitor/affiliate-skills --skill email-drip-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-drip-sequence, .gemini/skills/email-drip-sequence, .github/skills/email-drip-sequence and .opencode/skills/email-drip-sequence in your project.
What does Email Drip Sequence need to run?
SKILL.md names no scripts, command-line tools or credentials: Email Drip Sequence is instructions for the agent only. Compatibility (from SKILL.md): Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent.
Does Email Drip Sequence access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Email Drip Sequence safe to install?
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. Review the folder before installing.
What licence does Email Drip Sequence use?
Email Drip Sequence is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Email Drip Sequence use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Email Drip Sequence?
Skills that share tags, products or a category with Email Drip Sequence: Running Marketing (GTM-Strategist/gtm-strategist-skills, 261 stars), Campaign And Launch Planning (social-media-skills/skills, 125 stars), Marketing For Founders (npc-live/clawfirm, 156 stars) and Email Sequence (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Email Drip Sequence?
Affitor (a GitHub organization) maintains it in Affitor/affiliate-skills, which has 699 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on September 15, 2026.
Source: Affitor/affiliate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.