Marketing EmailSequencesAutomation

Email Sequence

Create and optimize email sequences, drip campaigns, and lifecycle flows.

$skillfish add ~skills/email-sequence

Real Examples Get Started Models & Context

Real Conversations

See how the Email Sequence skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

We need to build an email sequence for Nucleus PM trial users. Trial is 14 days. Goal is to get them to 'activated' — which means creating a sprint with 3+ tickets and running it. We have a 30% activation rate and want to improve it. What emails should we send and when?

Agent

Here's a 7-email behavioral trial sequence — triggered by actions (or inaction), not just days:

Email 1 — Immediately after signup Subject: Your Nucleus PM trial starts now — here's what to do first Goal: Get them into the product in the first hour Content: One action only — "Create your first sprint. Takes 2 minutes." → [Create a sprint]

Email 2 — 4 hours after signup (if no sprint created) Subject: Quick tip: start with a sample sprint Goal: Reduce blank-page paralysis Content: "Most teams start by importing their Jira backlog or using our Engineering template. Here's the 2-minute setup." → [Use the Engineering template]

Email 3 — After sprint created, before tickets added (behavioral trigger) Subject: Your sprint is empty — here's the fast way to fill it Goal: Get tickets added Content: "Now add 3 tickets to your sprint. You can type them in, import from Jira, or paste from a doc." → [Add tickets]

Email 4 — Day 3 (if not yet activated) Subject: The feature that saves engineering managers the most time Goal: Surface the AI Estimation aha moment Content: Show AI Estimation in a GIF. "Click any ticket → click 'AI Suggest' → see a story point recommendation. Teams using this average 40% less planning time." → [Try AI Estimation]

Email 5 — Day 7 (mid-trial check-in) Subject: 7 days in — what's working for you? Goal: Re-engage and surface objections Content: Personal-feeling email from a real person. "You've been in Nucleus PM for a week. What's getting in the way of making it your team's main tool?" — invite reply

Email 6 — Day 11 (pre-expiry nudge) Subject: 3 days left on your trial Goal: Urgency without pressure Content: "Your trial expires Friday. If you want to keep your sprint boards and ticket history, upgrade before then. We can also extend your trial if you need more time — just reply." → [Upgrade now]

Email 7 — Day 14 (trial expiry) Subject: Your trial ended — your work is still here Goal: Recover churned trials Content: "Your Nucleus PM account is paused. Your sprints, tickets, and AI suggestions are saved — they'll be waiting when you upgrade. Or if it wasn't the right fit, I'd love to know why." → [Reactivate]

Sequence rules:

Emails 1–3 are behavioral (triggered by actions/inaction) — not calendar-based
Stop the sequence when a user reaches 'activated' status
All emails come from a real person's email, not a no-reply address

You

We have 800 trial users who signed up in the last 90 days but never activated (never created a sprint). We want to try to re-engage them with a 3-email sequence. These users have been cold for 30–90 days. What should we send?

Agent

Re-engaging cold trial users requires a different approach than standard nurture — they've already ignored your onboarding emails. Here's a 3-email sequence that doesn't feel like a re-engagement campaign:

Email 1 — The honest check-in Subject: Did Nucleus PM miss the mark for you? From: [Real person, CEO or Head of Product]

Hey [First name],

You signed up for Nucleus PM a while back but never set up a sprint. I'm not going to pretend that's not a signal.

I'd genuinely like to know why — was the setup too complicated? Not the right fit for your team? You just got busy?

One reply is all it takes. I read every one.

[Your name]

P.S. If you want another shot at the trial, reply and I'll reset it.

Email 2 — Sent 5 days later (if no reply) Subject: We shipped something that might change your mind Goal: Give them a new reason to try

Body: Highlight the most compelling feature you've shipped in the last 60 days. Frame it as the specific thing that addresses the most common reason for not activating.

"The most common reason people don't finish setup: starting from a blank board is overwhelming. So we added a 1-click Engineering Team template. Your entire sprint structure is ready in 90 seconds." → [Try the template]

Email 3 — Sent 7 days after Email 2 (final) Subject: Last email from me on this Goal: Either convert or get a clear signal

"I'll stop emailing after this — but I wanted to leave the door open. If you ever want to give Nucleus PM another try, your account is still there. And if it just wasn't the right tool, that's useful to know too — hit reply and tell me why."

Expected re-engagement rate: 3–8% of cold trials typically reactivate from a sequence like this. The honest email (Email 1) generates the most replies and often reveals product feedback worth acting on.

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best

Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2

Good

Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only

32K+ Skill + conversation

100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Email Sequence?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.

$skillfish add ~skills/email-sequence

← Browse all 169 skills