agentleFS
fjilvvifjilvvi/growthlens/skills/email-nurture-teardown/SKILL.md

email-nurture-teardown

Skill2 starsChanged 5 months agoMITView on GitHub

Teardown of an email nurture / onboarding / sales sequence — map it email by email (timing, goal, subject line, angle, CTA), analyze the narrative arc and soft-to-hard-sell progression, spot branching and gaps, and recommend fixes. Use when the user forwards or pastes a sequence of marketing emails, or asks to "break down this email sequence", "analyze their nurture / onboarding emails", "reverse-engineer this drip campaign", or "review our welcome sequence".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't invent emails you weren't shown or fabricate open/click rates.

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Email Nurture Teardown

Reverse-engineer an email sequence into a map of goals, angles, and the soft-to-hard-sell arc — and find what's missing.

What it does

Takes a set of marketing emails (a welcome, onboarding, nurture, sales, or win-back sequence) and reconstructs how it's engineered: the cadence, each email's job, subject-line strategy, persuasion angle, CTA, and how the sequence escalates from value to offer. Ends with the gaps and a prioritized fix list.

When to use this skill

  • "Break down this email sequence" (with emails pasted/forwarded).
  • "Analyze their onboarding / nurture / drip / welcome emails."
  • "Reverse-engineer this launch sequence."
  • "Review our sequence and tell me what's weak."

Inputs needed

  • Required: the actual emails — pasted text or forwarded. The more complete the sequence (with send timing), the better.
  • Helpful: what the user opted into (lead magnet, trial, purchase), the goal of the sequence, and the audience.
  • Be honest about access: you generally cannot subscribe to an inbox and receive the emails yourself. If the user only gives an opt-in URL, analyze the opt-in/landing promise and ask them to forward the emails for the full teardown.

Method

  1. Establish the trigger & type — what starts the sequence (signup, purchase, abandonment) and its type (welcome, onboarding, nurture, sales/launch, re-engagement, win-back).
  2. Map each email in order, capturing:
    • Timing / delay from the previous email
    • Primary goal (educate, build trust, handle objection, sell, reactivate)
    • Subject line + the open-driver it uses (curiosity, benefit, urgency, personal)
    • Angle / big idea and format (story, tips, case study, hard pitch)
    • The single CTA
  3. Read the arc — does it follow a deliberate progression (value → trust → offer → urgency)? Where does it shift from soft to hard sell? Is the pacing right?
  4. Check mechanics — one clear CTA per email? Segmentation or branching (opened/clicked/bought)? Exit conditions? Mobile-friendly length?
  5. Find gaps — missing welcome, no objection-handling email, no social proof, no urgency/close, no re-engagement for non-openers, weak first subject line.
  6. Recommend — concrete additions/edits, prioritized by impact vs effort.

Output format

# Email Nurture Teardown — <Brand / sequence>

## TL;DR
- Sequence type, length, the arc in one line, and the biggest gap.

## Sequence map
| # | Timing | Goal | Subject line | Open-driver | Angle / format | CTA |
|---|--------|------|--------------|-------------|----------------|-----|

## Narrative arc
- Progression (value → offer) and where soft-sell becomes hard-sell:
- Pacing / cadence read:

## Mechanics
- CTA focus, segmentation/branching, exit conditions, length:

## Gaps
- (missing emails, objections, proof, urgency, re-engagement...)

## Prioritized recommendations
| # | Recommendation | Where | Why | Impact | Effort |
|---|----------------|-------|-----|--------|--------|

Quality bar

  • Work only from the emails actually provided; if the sequence is partial, say so.
  • Quote real subject lines and CTAs before critiquing them.
  • Don't invent emails you weren't shown or fabricate open/click rates.
  • Tie every recommendation to a specific email or a named gap.

Common mistakes to avoid

  • Reviewing individual emails in isolation instead of the sequence as a system.
  • Ignoring subject lines (the highest-leverage element for opens).
  • Missing the soft-to-hard-sell transition, which is where sequences succeed or fail.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.