Creator · Affitor
Last updated · Sep 3, 2026
Build multi-sequence email automation flows with branching logic. Triggers on: "build email automation", "create email funnel", "email automation flow", "welcome series with branches", "conditional email sequence", "set up automation", "email workflow builder", "segmented email f
Sandbox only
Install targets
Codex install prompt
Install the "email-automation-builder" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/automation/email-automation-builder. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Build multi-sequence email automation flows with branching logic. Triggers on: "build email automation", "create email funnel", "email automation flow", "welcome series with branches", "conditional email sequence", "set up automation", "email workflow builder", "segmented email flow", "advanced email sequence", "nurture funnel", "cart abandonment sequence", "win-back email flow". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"affitor-email-automation-builder","task":"Install email-automation-builder","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Design assets, images, video, audio, multimodal media, presentation, and creative production skills.
Scenario
Design and creative
I need my agent to produce design assets, UI directions, presentations, or creative media workflows.
Agent fit
Claude Code + OpenAI Agents + Cursor
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Affitor/affiliate-skills --skill email-automation-builder
Maintenance
active
3mo since push
Risk
Needs review
Quality score needs review
GitHub quality
639
73/100 Quality · 80/100 Trust
Coverage tags
Review notes
Quality score needs review · Needs review
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
639 GitHub stars
Repo activity
639 stars, 199 forks
Maintenance
3mo since push
License
MIT
Install
npx skills add Affitor/affiliate-skills --skill email-automation-builder
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add Affitor/affiliate-skills --skill email-automation-builderDo not use when
Alternative
175.1K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
85.2K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
1.8K Stars
npx skills add Alisa0808/vox-director --skill vox-director
Alternative
175.1K Stars
npx skills add anthropics/skills --skill canvas-design
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20email-automation-builder%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20email-automation-builder%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/affitor-email-automation-builder/install
Agent should check
Copy prompt
Task: Use email-automation-builder in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20email-automation-builder%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/affitor-email-automation-builder/install
Install command: npx skills add Affitor/affiliate-skills --skill email-automation-builder
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/affitor-email-automation-builder/install
LLM text format
/api/skills/affitor-email-automation-builder/install?format=text
Find alternatives
/api/skills/search?q=email-automation-builder&limit=3
Agent prompt
Use email-automation-builder for this task. Review https://www.openagentskill.com/api/skills/affitor-email-automation-builder/install, then install with: npx skills add Affitor/affiliate-skills --skill email-automation-builderRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/affitor-email-automation-builder
LLM text
/api/registry/manifest/affitor-email-automation-builder?format=text
Install alias
/api/registry/install/affitor-email-automation-builder
Recommend
/api/registry/recommend?task=Use%20email-automation-builder%20in%20an%20agent%20workflow&limit=3
Agent fit
Browser automation
Platforms
Claude Code, OpenAI Agents, Cursor
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Browser automation
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO639 GitHub stars
Stars/forks activity
INFO639 stars, 199 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Grow distribution
I need my agent to research keywords, improve SEO, analyze growth channels, and prepare marketing workflows.
Workflow fit
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Design, build, test, and ship interfaces
A practical workflow for agents that turn product briefs or Figma designs into polished frontend code, review the result, test it in a browser, and prepare a safe deployment.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
--- name: email-automation-builder description: > Build multi-sequence email automation flows with branching logic. Triggers on: "build email automation", "create email funnel", "email automation flow", "welcome series with branches", "conditional email sequence", "set up automation", "email workflow builder", "segmented email flow", "advanced email sequence", "nurture funnel", "cart abandonment sequence", "win-back email flow". license: MIT version: "1.0.0" tags: ["affiliate-marketing", "automation", "scaling", "workflow", "email"] compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent" metadata: author: affitor version: "1.0" stage: S7-Automation ---
# Email Automation Builder
Build multi-sequence email automation flows with branching logic, segmentation, triggers, and tool-specific setup. More advanced than S5 email-drip-sequence: this skill creates conditional flows that respond to subscriber behavior (opened, clicked, purchased). Output includes ASCII flow diagrams, email content, and platform setup instructions.
## Stage
S7: Automation — S5's email-drip-sequence is a linear 7-email series. Real email marketing uses branching flows: if they opened → send X, if they didn't → send Y, if they clicked the affiliate link → move to a different sequence. This skill builds the automation system, not just the emails.
## When to Use
- User needs email flows with conditional logic (if/then branches) - User wants welcome series, nurture flows, win-back campaigns, or cart abandonment - User says "email automation", "branching email", "conditional sequence" - User wants to set up flows in ConvertKit, Mailchimp, ActiveCampaign, or Beehiiv - User already has an S5 drip sequence and wants to upgrade it to a full automation - Chaining: upgrade S5 `email-drip-sequence` output to a branching automation
## Input Schema
```yaml product: name: string # REQUIRED — product being promoted affiliate_url: string # REQUIRED — affiliate link reward_value: string # OPTIONAL — commission info (e.g., "30% recurring")
audience: description: string # REQUIRED — who the subscribers are segments: # OPTIONAL — audience segments for branching - string # e.g., ["cold_leads", "warm_leads", "buyers"]
flow_type: string # OPTIONAL — "welcome" | "nurture" | "winback" # | "reengagement" | "cart_abandon" # Default: "welcome"
email_tool: string # OPTIONAL — "convertkit" | "mailchimp" # | "activecampaign" | "beehiiv" # Default: generic (works with any ESP)
num_emails: number # OPTIONAL — total emails in the flow (5-12) # Default: 7
lead_magnet: string # OPTIONAL — what they opted in for ```
**Chaining context**: If S5 email-drip-sequence was run earlier, offer to upgrade it: "I see you have a 7-email drip sequence. Want me to upgrade it with branching logic and segments?"
## Workflow
### Step 1: Map Flow Type to Template
Select automation template based on `flow_type`:
**Welcome Flow**: Trigger → Welcome email → Wait 1 day → Value email → Branch (opened? → Soft sell / didn't open? → Re-engagement) → Continue selling to openers, re-engage non-openers
**Nurture Flow**: Trigger → Educational series → Branch (clicked affiliate link? → Move to sales sequence / didn't click? → Continue nurturing) → Post-purchase thank you for converters
**Win-back Flow**: Trigger (inactive 30+ days) → "We miss you" → Wait 3 days → Value reminder → Branch (re-engaged? → Move to nurture / still inactive? → Last chance) → Sunset after no response
### Step 2: Define Triggers and Entry Conditions
For each flow, specify: - **Entry trigger**: What starts the flow (new subscriber, tag added, purchase, inactivity) - **Exit conditions**: What removes someone (purchase, unsubscribe, entered different flow) - **Branch conditions**: Opens, clicks, purchases, time-based
### Step 3: Design Branching Logic
Create decision points: - After email N: Did they open? (Branch A: opened, Branch B: not opened) - After email N: Did they click affiliate link? (Branch A: clicked, Branch B: didn't) - After email N: Did they purchase? (Branch A: buyer → thank you, Branch B: non-buyer → continue)
### Step 4: Write Each Email
For each email in each branch, write: - Subject line (40-60 chars) - Preview text (80-100 chars) - Body copy (200-400 words) - CTA (single, clear) - FTC disclosure (for emails with affiliate links)
### Step 5: Add Wait Times
Between emails: - Welcome flow: 0, 1, 2, 3, 5, 7, 10 days - Nurture flow: 2, 4, 7, 10, 14 days - Win-back flow: 0, 3, 7, 14 days - Adjust based on audience engagement patterns
### Step 6: Output Flow + Setup
Present: - ASCII flow diagram showing the full automation - Each email's content - Tool-specific setup instructions (if email_tool specified)
### Step 7: Self-Validation
Before presenting output, verify:
- [ ] Every branch path leads to a valid next step (no dead ends) - [ ] All emails are complete in each branch (subject, body, CTA) - [ ] Wait times between emails sum correctly to total flow duration - [ ] FTC disclosure present on all emails containing affiliate links - [ ] Branch conditions are clear boolean logic (opened/clicked/didn't)
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
## Output Schema
```yaml output_schema_version: "1.0.0" # Semver — bump major on breaking changes automation: flow_type: string product: string total_emails: number total_branches: number estimated_days: number # total span of the flow
flow: - step: number type: string # "email" | "wait" | "branch" | "exit" email: # present if type is "email" subject: string preview: string body: string cta: string has_affiliate_link: boolean wait_days: number # present if type is "wait" branch: # present if type is "branch" condition: string # e.g., "opened previous email?" yes_path: number # step number for yes no_path: number # step number for no
setup: tool: string steps: string[] # tool-specific setup instructions tags: string[] # recommended tags to apply segments: string[] # recommended segments ```
## Output Format
1. **Flow Overview** — flow type, total emails, total days, branch count 2. **ASCII Flow Diagram** — visual representation of the automation with branches 3. **Email Content** — each email with subject, preview, body, CTA (grouped by branch) 4. **Setup Instructions** — tool-specific steps to build this automation 5. **Tags & Segments** — recommended tagging strategy for tracking
## Error Handling
- **No product info**: "What affiliate product are you promoting? I need the product name and your affiliate link to write the email content." - **Unknown email tool**: "I don't have specific setup instructions for [tool]. I'll provide generic automation logic that works with any ESP — just map the triggers, waits, and branches to your tool's interface." - **Too many emails requested (>12)**: "12+ emails in one flow is usually too many. I'll create a 7-email flow with branches. For longer nurture, consider chaining two separate flows." - **Upgrading from S5**: "I see your existing 7-email drip. I'll keep the email content and add branching logic: opened/not-opened splits after emails 2 and 4, and a purchase detection branch after email 5."
## Examples
### Example 1: Welcome flow with branches
**User**: "Build a welcome email automation for HeyGen (affiliate link: heygen.com/ref/abc123) for content creators who downloaded my AI tools guide." **Action**: 7-email welcome flow. Email 1: Deliver guide. Email 2: Value (AI video tip). Branch: Did they open email 2? Yes → Email 3 (soft sell HeyGen). No → Email 3b (re-engagement with different subject). Continue branching through to email 7. ASCII diagram + all email content + ConvertKit setup.
### Example 2: Upgrade existing S5 drip
**User**: "Take my email drip sequence from earlier and add automation logic." **Action**: Keep the 7 emails from S5 output. Add branches: After email 2 (opened → continue / not opened → resend with new subject). After email 4 (clicked affiliate link → skip to email 5 hard sell / didn't click → add extra value email). After email 5 (purchased → exit + thank you / didn't purchase → continue to email 6-7).
### Example 3: Win-back flow
**User**: "Create a win-back sequence for subscribers who haven't opened emails in 30 days. I promote Semrush." **Action**: 4-email win-back flow. Trigger: 30 days no opens. Email 1: "Still interested in SEO?" (curiosity). Wait 3 days. Email 2: Value piece (SEO tip). Branch: Opened? Yes → Move to nurture flow. No → Email 3: "Last chance" (urgency). No response after 7 days → Sunset (remove from list).
## References
- `shared/references/ftc-compliance.md` — FTC disclosure for emails with affiliate links. Read in Step 4. - `shared/references/affitor-branding.md` — Branding guidelines for email footers. Referenced in Step 4. - `shared/references/flywheel-connections.md` — master flywheel connection map
## Revenue & Action Plan
### Expected Outcomes - **Revenue potential**: Email automation is the closest thing to passive income in affiliate marketing. A well-built welcome flow converts 5-15% of subscribers to affiliate clicks. With 500 new subscribers/month × 10% click rate × 3% conversion × $50 commission = $750/month on autopilot - **Benchmark**: Email marketing delivers $42 return per $1 spent. Branching flows outperform linear sequences by 25-40% because they send the right message to the right person at the right time - **Key metric to track**: Revenue per subscriber per month. Industry benchmark for affiliate email: $0.50-2.00/subscriber/month. Below $0.50 = weak offer or poor segmentation
### Do This Right Now (15 min) 1. **Set up Email 1 (Welcome/Deliver) in your ESP today** — this is the highest-open-rate email (60-80% open rate). Get it live immediately 2. **Create the first branch trigger** — "opened Email 2?" — in your ESP's automation builder 3. **Schedule remaining emails** in the flow — most ESPs let you build the full automation in one session 4. **Test the flow** — subscribe with a test email address and verify every branch works
### Track Your Results After 30 days: what's the open rate on each email? Click rate on affiliate links? Revenue attributed to the flow? If Email 3+ have <15% open rate, test new subject lines. If affiliate CTR is <2%, strengthen the CTA or add bonuses.
> **Next step — copy-paste this prompt:** > "Set up conversion tracking for my email automation affiliate links" → runs `conversion-tracker`
## Flywheel Connections
### Feeds Into - `conversion-tracker` (S6) — automated email links to track
### Fed By - `email-drip-sequence` (S5) — drip sequence to upgrade with automation logic - `conversion-tracker` (S6) — conversion data for branch conditions
### Feedback Loop - `conversion-tracker` (S6) provides email conversion data → optimize branch conditions and timing
```yaml chain_metadata: skill_slug: "email-automation-builder" stage: "automation" timestamp: string suggested_next: - "conversion-tracker" - "performance-report" ```
Source provenance
Decision snapshot
639 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for email-automation-builder, ready for a manual X post.
email-automation-builder: Build multi-sequence email automation flows with branching logic. Triggers on: "build email a... 639 stars https://www.openagentskill.com/skills/affitor-email-automation-builder?ref=x
Listing + install path for email-automation-builder: https://www.openagentskill.com/skills/affitor-email-automation-builder?ref=x Install: npx skills add Affitor/affiliate-skills --skill email-automation-builder
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to Affitor but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/affitor-email-automation-builder?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/affitor-email-automation-builder?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/affitor-email-automation-builder/audit)
[](https://www.openagentskill.com/skills/affitor-email-automation-builder?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Affitor
@affitor
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
175.1K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
85.2K StarsVox Director
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
1.8K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
175.1K StarsPermission surface
shell or command execution, database access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness