Individual skill
email-lifecycle
Lifecycle email, SMS and push: audits the list and deliverability, then writes the flows this kind of business needs first, loadable as-is in your own tool, plus segments, cadence and this week's broadcasts. Never sends anything. Use when: set up my welcome and abandoned-cart emails; trial onboarding or waitlist launch emails; win back lapsed customers; plan this week's emails and texts; push notifications for my app; why are my emails going to spam; plan our Black Friday email and SMS sends; a send went wrong. Not for cold outreach to prospects — use write-outreach; not the editorial newsletter issue — use make-content; not the whole cross-channel Black Friday plan — use plan-campaign.
skills/marketing/email-lifecycle/SKILL.md
Source commit df8298140d434a6363de0c265eb6af2e571d97a5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- 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)
- 1,315
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- claudecode Repository topic
- claudecode-skills Repository topic
- codex Repository topic
- cursor Repository topic
- gtm Repository topic
- skills Repository topic
- marketing Derived category
- writing Derived category
- sales Derived category
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 · 18,035 bytesreferences/benchmarks.mddoc · 1,902 bytesreferences/copy-craft.mddoc · 3,615 bytesreferences/deliverability.mddoc · 5,877 bytesreferences/flow-library.mddoc · 14,418 bytesreferences/intake.mddoc · 6,700 bytesreferences/loadable-flow-format.mddoc · 8,407 bytesreferences/modes-and-incidents.mddoc · 5,615 bytesreferences/run-memory.mddoc · 9,124 bytesreferences/segments-cadence-offers.mddoc · 5,258 bytesreferences/sms-push-whatsapp.mddoc · 3,146 bytesreferences/worked-flows.mddoc · 9,075 bytesskill.meta.jsonasset · 5,562 bytestests/test-by-hand.mddoc · 9,269 bytes
Read excerpt
# email-lifecycle
One marketer want: "Cart and welcome emails make money while I sleep — mine do not exist." The playbook drafts and stages a lifecycle program; the marketer loads it into their own tool and presses send.
## What you get
1. **Deliverability and list report** — every plumbing item green / red / unknown, each marked *verified* (the agent saw it), *from you* or *unknown*. Never a green the agent did not see. Red and unknown items come with the exact fix and who does it.
2. **Flow pack** — the flows you asked for, or else the top two this business can load today (a third is offered), each a build sheet in your tool's own terms: trigger, filters, exit, re-entry, consent per market, priority and suppressions, timing, and every message finished, plus its goal metric, its test, a holdout where one fits, and the result it should beat. Each flow is marked **ready to load** or **not ready**, with the blocker in plain words ("waiting on your answer about returns", "needs your app to tell the email tool who installed", "your current plan can't run this — here are the options").
3. **Segments, priority and cadence** — segment definitions in the company's own terms (clicks, orders, activity — not opens), the flow priority map and frequency cap, the proposed send cadence.
4. **This week's broadcasts and the month's calendar** — broadcasts finished and ready to schedule (email; SMS only where consent exists and the moment is high-intent); the calendar as one table of dates and ideas.
5. **Proposals awaiting a yes** — offer depth with margin math, cadence, sunset slice, tool or plan changes, a tracking plan for missing events, any high-stakes send.
## Before you start