Drip Campaign Skill
Design nurture as progressive context, not a pile of delayed emails. Each step should advance readiness or route the contact elsewhere.
Fit Check
- Primary lens: time-based nurture streams, branching logic, lead scoring hooks, and conversion analysis.
- Common request signals: nurture sequence planning, lead scoring hooks, drop-off analysis, sales handoffs, and timed education streams.
- Default posture: Design nurture as progressive context, not a pile of delayed emails. Each step should advance readiness or route the contact elsewhere.
- Useful output family: drip maps, nurture briefs, branch logic tables, scoring hooks, drop-off diagnoses, and conversion-focused rewrite plans.
- Production boundary: separate recommendation from execution.
- Evidence boundary: say which source material supports the recommendation.
- Review boundary: identify the human owner for risky changes.
- Data boundary: do not assume missing fields, consent, or suppression state.
- Platform boundary: describe provider-specific steps in operational language.
- Measurement boundary: define what success or recovery will look like.
Use This For
time-based nurture streams, branching logic, lead scoring hooks, and conversion analysis.
Avoid Using It For
Generic email advice with no audience, platform, lifecycle, evidence, or approval context.
Procedure
- Define the campaign entry moment and the recipient's current intent, source, and awareness level.
- Map the sequence promise across time: what the contact should understand, believe, or do after each message.
- Set delays and branches based on decision points, not arbitrary spacing.
- Add lead scoring or qualification hooks only when sales, onboarding, or support will act on them.
- Audit drop-off by message, branch, source, segment, and CTA to find where readiness stalls.
- Recommend edits that improve sequence logic before rewriting every email.
Acceptance Checks
- Every email has a distinct job in the nurture path.
- Branching criteria are measurable and available in the platform.
- Sales or product handoff thresholds are explicit.
- The sequence has exits for conversion, disqualification, inactivity, and suppression.
- Performance review separates timing, audience fit, offer, and copy issues.
Output Pattern
Return drip maps, nurture briefs, branch logic tables, scoring hooks, drop-off diagnoses, and conversion-focused rewrite plans. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
1---2name: dripcampaignskill3description: Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on time-based nurture streams, branching logic, lead scoring hooks, and conversion analysis. Triggers include requests about nurture sequence planning, lead scoring hooks, drop-off analysis, sales handoffs, and timed education streams.4---5
6# Drip Campaign Skill
7
8Design nurture as progressive context, not a pile of delayed emails. Each step should advance readiness or route the contact elsewhere.
9
10## Fit Check
11
121. Primary lens: time-based nurture streams, branching logic, lead scoring hooks, and conversion analysis.
132. Common request signals: nurture sequence planning, lead scoring hooks, drop-off analysis, sales handoffs, and timed education streams.
143. Default posture: Design nurture as progressive context, not a pile of delayed emails. Each step should advance readiness or route the contact elsewhere.
154. Useful output family: drip maps, nurture briefs, branch logic tables, scoring hooks, drop-off diagnoses, and conversion-focused rewrite plans.
165. Production boundary: separate recommendation from execution.
176. Evidence boundary: say which source material supports the recommendation.
187. Review boundary: identify the human owner for risky changes.
198. Data boundary: do not assume missing fields, consent, or suppression state.
209. Platform boundary: describe provider-specific steps in operational language.
2110. Measurement boundary: define what success or recovery will look like.
22
23### Use This For
24
25time-based nurture streams, branching logic, lead scoring hooks, and conversion analysis.
26
27### Avoid Using It For
28
29Generic email advice with no audience, platform, lifecycle, evidence, or approval context.
30
31## Procedure
32
331. Define the campaign entry moment and the recipient's current intent, source, and awareness level.
342. Map the sequence promise across time: what the contact should understand, believe, or do after each message.
353. Set delays and branches based on decision points, not arbitrary spacing.
364. Add lead scoring or qualification hooks only when sales, onboarding, or support will act on them.
375. Audit drop-off by message, branch, source, segment, and CTA to find where readiness stalls.
386. Recommend edits that improve sequence logic before rewriting every email.
39
40## Acceptance Checks
41
421. Every email has a distinct job in the nurture path.
432. Branching criteria are measurable and available in the platform.
443. Sales or product handoff thresholds are explicit.
454. The sequence has exits for conversion, disqualification, inactivity, and suppression.
465. Performance review separates timing, audience fit, offer, and copy issues.
47
48## Output Pattern
49
50Return drip maps, nurture briefs, branch logic tables, scoring hooks, drop-off diagnoses, and conversion-focused rewrite plans. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
aiskillstore