Individual skill
email-drip-builder
Designs automated onboarding and activation drip sequences with behavior-gated sends, exit triggers on conversion, and per-email jobs and timing. Use when someone asks "build an onboarding email sequence", "design a drip campaign for new signups", "why isn't our onboarding flow activating users", or is extending an existing drip series. Do NOT use for recurring content newsletters - use email-newsletter-pro; for recovering abandoned checkouts use abandoned-cart-sequence; for re-engaging dormant users use win-back-campaign; for cold outreach to prospects use outreach-sequence-designer or cold-email-craft.
skills/email-drip-builder/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,834 bytes
Read excerpt
# Email Drip Builder
A drip sequence is a contract with the user: they gave their attention, and the sequence returns it with value at the right moment. Sequences that read like mail merges get unsubscribes; sequences timed to behavior build habits. The costly mistake this skill prevents is the fixed-timer drip that keeps selling activation to users who already activated - the fastest way to teach a new user that these emails can be ignored.
## Inputs to collect
1. **The activation milestone** - the one action that means the user is activated (first invoice sent, first project shared). This is the exit trigger for the entire sequence. If undefined, define it first - a drip without an exit condition is a leak, not a funnel. Pull it from lifecycle-journey-map if that map exists.
2. **The intermediate milestones** - 2-4 steps between signup and activation, each trackable as an event.
3. **Current activation rate and where users stall** - determines which email gets the most work.
4. **Independently useful assets** - tips, benchmarks, shortcuts, case studies each email can deliver.
5. **Sending constraints** - ESP capabilities for event-based triggers vs. timers; if only timers exist, flag the sequence as degraded and say which rules cannot be enforced.
## Operating procedure