When the user needs to design, write, or optimize email sequences -- including welcome series, nurture campaigns, re-engagement flows, onboarding emails, or newsletter strategy.
63
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No known issues
Fix and improve this skill with Tessl
tessl review fix ./skills/email-marketing/SKILL.mdcold-outreach -- when emails are going to prospects who have not opted in (different rules, different approach)content-strategy -- when email content needs to be part of a broader content distribution planonboarding-flow -- when the email sequence is part of product onboarding and needs to align with in-app messagingExample 1: Welcome sequence for lead magnet
"We launched a free template as a lead magnet. Need a welcome sequence to convert downloads to free trial signups."
Good output: A 6-email sequence over 12 days. Email 1 delivers the template with a quick-start tip. Email 2 shares the founder story. Email 3 teaches a technique related to the template topic. Email 4 shares a customer case study. Email 5 addresses the "I don't have time for another tool" objection. Email 6 offers a free trial with a specific reason to start this week. Each email includes 3 subject line variants, full copy (100-400 words), and a single CTA.
Example 2: Re-engagement campaign
"We have 3,000 subscribers who haven't opened an email in 60 days. What do we do?"
Good output: A 3-email re-engagement sequence. Email 1 (day 0): "Still interested?" with a high-value resource, no hard sell. Email 2 (day 3): Direct question asking what content they want, reply-based engagement. Email 3 (day 7): "Last email unless you want to stay" with a clear re-opt-in link. Anyone who does not engage after email 3 goes to a suppression list. Includes list cleaning guidance and re-engagement benchmarks.
4ad31b4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.