email-automation-builder

Name: email-automation-builder
Author: Affitor

3installs184forks

How to install email-automation-builder?

affitor/affiliate-skills/email-automation-builder

$npx -y skills add Affitor/affiliate-skills --skill email-automation-builder

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Email Automation Builder
2
3	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.
4
5	## Stage
6
7	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.
8
9	## When to Use
10
11	- User needs email flows with conditional logic (if/then branches)
12	- User wants welcome series, nurture flows, win-back campaigns, or cart abandonment
13	- User says "email automation", "branching email", "conditional sequence"
14	- User wants to set up flows in ConvertKit, Mailchimp, ActiveCampaign, or Beehiiv
15	- User already has an S5 drip sequence and wants to upgrade it to a full automation
16	- Chaining: upgrade S5 `email-drip-sequence` output to a branching automation
17
18	## Input Schema
19
20	```yaml
21	product:
22	name: string # REQUIRED — product being promoted
23	affiliate_url: string # REQUIRED — affiliate link
24	reward_value: string # OPTIONAL — commission info (e.g., "30% recurring")
25
26	audience:
27	description: string # REQUIRED — who the subscribers are
28	segments: # OPTIONAL — audience segments for branching
29	- string # e.g., ["cold_leads", "warm_leads", "buyers"]
30
31	flow_type: string # OPTIONAL — "welcome" \| "nurture" \| "winback"
32	# \| "reengagement" \| "cart_abandon"
33	# Default: "welcome"
34
35	email_tool: string # OPTIONAL — "convertkit" \| "mailchimp"
36	# \| "activecampaign" \| "beehiiv"
37	# Default: generic (works with any ESP)
38
39	num_emails: number # OPTIONAL — total emails in the flow (5-12)
40	# Default: 7
41
42	lead_magnet: string # OPTIONAL — what they opted in for
43	```
44
45	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?"
46
47	## Workflow
48
49	### Step 1: Map Flow Type to Template
50
51	Select automation template based on `flow_type`:
52
53	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
54
55	Nurture Flow: Trigger → Educational series → Branch (clicked affiliate link? → Move to sales sequence / didn't click? → Continue nurturing) → Post-purchase thank you for converters
56
57	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
58
59	### Step 2: Define Triggers and Entry Conditions
60
61	For each flow, specify:
62	- Entry trigger: What starts the flow (new subscriber, tag added, purchase, inactivity)
63	- Exit conditions: What removes someone (purchase, unsubscribe, entered different flow)
64	- Branch conditions: Opens, clicks, purchases, time-based
65
66	### Step 3: Design Branching Logic
67
68	Create decision points:
69	- After email N: Did they open? (Branch A: opened, Branch B: not opened)
70	- After email N: Did they click affiliate link? (Branch A: clicked, Branch B: didn't)
71	- After email N: Did they purchase? (Branch A: buyer → thank you, Branch B: non-buyer → continue)
72
73	### Step 4: Write Each Email
74
75	For each email in each branch, write:
76	- Subject line (40-60 chars)
77	- Preview text (80-100 chars)
78	- Body copy (200-400 words)
79	- CTA (single, clear)
80	- FTC disclosure (for emails with affiliate links)
81
82	### Step 5: Add Wait Times
83
84	Between emails:
85	- Welcome flow: 0, 1, 2, 3, 5, 7, 10 days
86	- Nurture flow: 2, 4, 7, 10, 14 days
87	- Win-back flow: 0, 3, 7, 14 days
88	- Adjust based on audience engagement patterns
89
90	### Step 6: Output Flow + Setup
91
92	Present:
93	- ASCII flow diagram showing the full automation
94	- Each email's content
95	- Too

People who liked this also viewed

6 picks

Type

email-automation-builder

3installs184forks

View on GitHub

How to install email-automation-builder?

affitor/affiliate-skills/email-automation-builder

$npx -y skills add Affitor/affiliate-skills --skill email-automation-builder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Email Automation Builder
2
3	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.
4
5	## Stage
6
7	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.
8
9	## When to Use
10
11	- User needs email flows with conditional logic (if/then branches)
12	- User wants welcome series, nurture flows, win-back campaigns, or cart abandonment
13	- User says "email automation", "branching email", "conditional sequence"
14	- User wants to set up flows in ConvertKit, Mailchimp, ActiveCampaign, or Beehiiv
15	- User already has an S5 drip sequence and wants to upgrade it to a full automation
16	- Chaining: upgrade S5 `email-drip-sequence` output to a branching automation
17
18	## Input Schema
19
20	```yaml
21	product:
22	name: string # REQUIRED — product being promoted
23	affiliate_url: string # REQUIRED — affiliate link
24	reward_value: string # OPTIONAL — commission info (e.g., "30% recurring")
25
26	audience:
27	description: string # REQUIRED — who the subscribers are
28	segments: # OPTIONAL — audience segments for branching
29	- string # e.g., ["cold_leads", "warm_leads", "buyers"]
30
31	flow_type: string # OPTIONAL — "welcome" \| "nurture" \| "winback"
32	# \| "reengagement" \| "cart_abandon"
33	# Default: "welcome"
34
35	email_tool: string # OPTIONAL — "convertkit" \| "mailchimp"
36	# \| "activecampaign" \| "beehiiv"
37	# Default: generic (works with any ESP)
38
39	num_emails: number # OPTIONAL — total emails in the flow (5-12)
40	# Default: 7
41
42	lead_magnet: string # OPTIONAL — what they opted in for
43	```
44
45	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?"
46
47	## Workflow
48
49	### Step 1: Map Flow Type to Template
50
51	Select automation template based on `flow_type`:
52
53	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
54
55	Nurture Flow: Trigger → Educational series → Branch (clicked affiliate link? → Move to sales sequence / didn't click? → Continue nurturing) → Post-purchase thank you for converters
56
57	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
58
59	### Step 2: Define Triggers and Entry Conditions
60
61	For each flow, specify:
62	- Entry trigger: What starts the flow (new subscriber, tag added, purchase, inactivity)
63	- Exit conditions: What removes someone (purchase, unsubscribe, entered different flow)
64	- Branch conditions: Opens, clicks, purchases, time-based
65
66	### Step 3: Design Branching Logic
67
68	Create decision points:
69	- After email N: Did they open? (Branch A: opened, Branch B: not opened)
70	- After email N: Did they click affiliate link? (Branch A: clicked, Branch B: didn't)
71	- After email N: Did they purchase? (Branch A: buyer → thank you, Branch B: non-buyer → continue)
72
73	### Step 4: Write Each Email
74
75	For each email in each branch, write:
76	- Subject line (40-60 chars)
77	- Preview text (80-100 chars)
78	- Body copy (200-400 words)
79	- CTA (single, clear)
80	- FTC disclosure (for emails with affiliate links)
81
82	### Step 5: Add Wait Times
83
84	Between emails:
85	- Welcome flow: 0, 1, 2, 3, 5, 7, 10 days
86	- Nurture flow: 2, 4, 7, 10, 14 days
87	- Win-back flow: 0, 3, 7, 14 days
88	- Adjust based on audience engagement patterns
89
90	### Step 6: Output Flow + Setup
91
92	Present:
93	- ASCII flow diagram showing the full automation
94	- Each email's content
95	- Too

People who liked this also viewed

6 picks

Type