AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Email Nurture Teardown

skill-fjilvi-afk-growthlens-email-nurture-teardown · by fjilvvi

>-

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-fjilvi-afk-growthlens-email-nurture-teardown

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fjilvi-afk-growthlens-email-nurture-teardown)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Email Nurture Teardown? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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).

  1. 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
  1. 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?

  1. Check mechanics — one clear CTA per email? Segmentation or branching

(opened/clicked/bought)? Exit conditions? Mobile-friendly length?

  1. Find gaps — missing welcome, no objection-handling email, no social proof,

no urgency/close, no re-engagement for non-openers, weak first subject line.

  1. Recommend — concrete additions/edits, prioritized by impact vs effort.

Output format

# Email Nurture Teardown — 

## 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.