The Email Engine
Skills · Subagent · Command · PDF
.claude/the-email-engine/zip
skills/06
├ deliverability-checklist
├ email-qa
├ lifecycle-map
├ newsletter-issue
├ segmentation-plan
├ sequence-architect
agents/01
├ list-health-reviewer
commands/01
├ /email-qa
FIELD-GUIDE.pdf8pp
English
One payment · No account · No subscription
- ✓ Download link in your inbox in seconds
- ✓ Secure card checkout · VAT handled
- ✓ 14-day money back, no questions
- ✓ Every future revision included
- ✓ Runs in Claude Code and claude.ai
Built for Claude first, our recommended agent. Skills follow the open Agent Skills standard (SKILL.md), so they also run in any agent that reads it; subagents and slash commands are Claude Code formats.
The Email Engine
The owned audience, built and kept
six skills·one subagent·one command·8-page guide
Your agent maps which programme owns which customer moment, specifies the sequence before a word is written, and checks every send before it goes out. It never sends.
Executive summary
- The problem
- Most lists run as a monthly broadcast, so nobody can say which programme owns onboarding or win-back, and the inactive share grows quietly in the background. A broken unsubscribe link or an empty name token is found by the customer, after the send.
- What it does
- lifecycle-map finds the stage no programme owns, sequence-architect writes the spec before the copy, email-qa checks links, tokens, unsubscribe and sender identity on every draft, and the list-health-reviewer subagent reads your exports without ever sending.
- Why take it
- When the click goes, the list is the relationship you still own. Every send that goes out broken spends a little of it.
For lifecycle and CRM marketers, newsletter owners and founders running the list themselves.
In the first week you will
- 01Run /email-qa on the next send and get links, tokens, plain text, unsubscribe and subject length checked before it leaves
- 02Draw the lifecycle-map from the customer moments and data fields you actually have, and find the stage no programme owns
- 03Hand your list export to list-health-reviewer and read the inactive, bouncing and complaining share with the column each figure came from
Contents of the Kit
- 01Six installable agent skills: lifecycle-map, sequence-architect, segmentation-plan, newsletter-issue, deliverability-checklist, email-qa
- 02The list-health-reviewer subagent: reads exported list and engagement files and reports what the data shows about inactive share, bounces and complaints. Read-only, never sends
- 03An /email-qa slash command that runs the pre-send check on a pasted draft
- 04The pre-send QA that checks links, tokens, plain-text, unsubscribe, subject length and rendering notes, and flags spam heuristics as heuristics
- 05Blank templates for the lifecycle map and the sequence specification
- 06An 8-page Field Guide on the email chain, and plugin manifest included
One skill, as it ships
SKILL.md
lifecycle-map
- Use when
- Use when an email channel is one broadcast list with a monthly send, when someone asks "what emails should we be sending", when a new product, plan or subscription changes the customer journey, or before any sequence is specified.
- Requires
- The product or service and the moments a customer passes through · Consent status of the audience · The data fields available in the email platform or CRM
- Will not
- No invented list sizes, open rates, conversion rates or industry benchmarks · A trigger on a field that does not exist is a gap, not a plan · The map never plans a programme for people who did not opt in to that kind of message
- Returns
- Lifecycle map: {product or brand} · {date}
One of six skills in the kit · All of them install the same way
The contents, in full · six skills, one subagent, one command
- 01lifecycle-mapYour product, your customer moments and your data fields in, the lifecycle map out: which programme owns which stage (welcome, onboarding, nurture, renewal, win-back), what triggers each, what ends it, who owns it, and what it is measured on.
- 02sequence-architectOne automated sequence specified end to end: goal, trigger, number of messages, spacing, the job of each message, exit and suppression conditions, and the measure. Writes the spec; the copy follows the spec.
- 03segmentation-planSegments built from the fields you have, not the fields you wish you had, with suppression rules, the send cadence per segment and the question each segment is meant to answer.
- 04newsletter-issueAn issue planned around one idea: sections, the argument, subject line and preheader options, the single call to action, length, and what the issue is not about.
- 05deliverability-checklistAuthentication (SPF, DKIM, DMARC) as you report it, sending domain and warm-up, list hygiene, complaint handling and the monitoring routine, each item verified or not verified.
- 06email-qaThe pre-send check on a draft: links, personalization tokens and their fallbacks, plain-text version, unsubscribe and sender identity, subject length, alt text, rendering notes, and the heuristics that tend to trip filters.
- 07list-health-reviewer (subagent)Reads list and engagement exports and reports the share of the list that is inactive, bouncing or complaining as the data shows it, with the file and column each finding came from. Read-only.
- 08/email-qaRuns the pre-send check on a pasted draft and its context, verdict first. If the unsubscribe link or the sender identity block fails, the verdict is not ready whatever the rest says, and spam observations are reported as heuristics rather than verdicts.
The End of the Click measures the traffic collapse and concludes that the response is distinctiveness plus an audience you own. When the answer engine resolves the query on the results page, the brands that keep a direct line to their customers keep the relationship. Email is that line, and the Email Engine runs it as a system rather than a broadcast, with deliverability treated as infrastructure. The tools are strict about what they cannot see: open rates, list sizes and authentication status come from you, deliverability is reported as verified or not verified, and nothing in this kit sends.
Pairs with
The End of the Click makes the case for the owned audience. Think Like a CMO explains why a list built on distinctiveness outlasts one built on discounts. The Client Pipeline and its follow-up-sequence cover the sales follow-up after a proposal; this kit covers everything the audience receives after it has said yes to hearing from you.
Before you buy
01Do I need Claude Code?
No. Every skill uploads to claude.ai as a zip. Subagents and slash commands are the Claude Code extras.
02I am not a programmer.
Install is copying folders into a .claude directory. The Field Guide in each kit assumes nothing beyond that.
03Will it work in my agent?
Skills follow the open Agent Skills standard (SKILL.md), so any agent that reads it can run them. Built for Claude first, our recommended agent.
04Do the tools invent numbers?
Never. Every figure is supplied by you, confirmed by you, or labeled as an assumption in the output.
05How does it arrive?
Instantly. Pay by card and the download link is in your inbox within seconds, and on the confirmation screen.
06Is this a subscription?
No. One payment, lifetime access to your download, every future revision of what you bought included.
07What if it is not useful to me?
Write to info@conclusionmp.com within 14 days of purchase and you get a full refund. No questions, no forms.
Ready when you are
The Email Engine, $12.
Instant download, one payment, every future revision included. Or take The Growth Desk, five items for $39, and this kit works out at $7.80.