Menu

Individual skill

email-sequence

0upvotes

Use this skill when designing or fixing an automated multi-email flow for people who already know you — welcome and onboarding series, lead nurture, trial conversion, re-engagement, post-purchase, or any behaviour-triggered drip. Produces the sequence spec: entry trigger, touch count, timing, per-email job, exit conditions, and what to measure. Trigger phrasings: "email sequence", "drip campaign", "nurture flow", "welcome series", "onboarding emails", "re-engagement emails", "lifecycle emails", "what emails should we send", "our nurture isn't converting".

skills/tanyo-gochev/email-sequence/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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)
237
Repository last updated
Oct 20, 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
Read excerpt

Applies to automated flows for known contacts, not cold outreach. Produces a buildable spec, not just copy.

## Trigger on behaviour, not on a clock

A fixed drip sends the same day-three email to someone who logged in twice yesterday and someone who has never logged in at all. Both get the wrong message, and the engaged one gets taught to ignore you.

Start from **the core action and its natural frequency**: the single behaviour that delivers value, and how often a satisfied person would do it. A "we miss you" email on day three to a monthly-frequency product is noise. Every trigger, delay, and exit condition keys off that frequency.

## One email, one job

Each email does exactly one thing and asks for exactly one thing. The instinct to bundle — a tip, a case study, a webinar, and an upgrade nudge in one send — is what makes sequences feel like newsletters and perform like them.

Write the *job* of each touch before writing a word of copy. If two adjacent emails have the same job, one of them shouldn't exist.
Back to top