emails helps an agent create and improve automated email flows. It sets the sequence type, trigger, goal, length, timing and exit conditions, then drafts each email with a subject line, preview text, body and one call to action.
Principles keep each email to one job and put value before the ask. References cover sequence templates, a lifecycle email-type audit and copy guidelines, and a screen removes AI tells such as fake Re: subject lines.
What You Get
- A sequence overview with name, trigger, goal, length, timing and exit conditions
- Each email with send time, subject, preview text, body, CTA and segment conditions
- Suggested lengths and timing for welcome, nurture, onboarding and re-engagement flows
- A lifecycle audit of onboarding, retention, billing, usage and win-back emails
- A metrics plan with benchmarks
Common Use Cases
- Writing a seven-email welcome sequence
- Auditing which lifecycle emails a SaaS product is missing
- Building a win-back flow for inactive subscribers
- Improving subject lines and preview text on an existing flow
What Makes It Unique
It ties each sequence type to a send pattern (for example welcome emails over 12 to 14 days and re-engagement after 30 to 60 days of inactivity) and covers lifecycle categories beyond marketing flows, such as failed payment recovery and renewal reminders. Its AI-tell list adds email-specific items: fake Re: or Fwd: subjects, stock openers and sign-off filler.
Under The Hood
The SKILL.md and three references are loaded as context. It ships no scripts and runs no commands. It reads the product marketing context file in your project when present. The skill links to a registry of email tools such as Customer.io, Mailchimp, Resend, SendGrid and Kit for implementation, but it does not call them. Output is written in chat or to files you name.