Onboarding Email Sequence Writer

What it does

Given the product and what a new user needs to do to get value from it, drafts a sequence of 3-5 emails spaced over the first couple weeks, each with one clear goal such as finishing setup or trying the core feature, rather than generic welcome filler. Sequences the emails so each still makes sense whether or not the prior step was completed.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/onboarding-email-sequence-writer/ (or ~/.claude/skills/onboarding-email-sequence-writer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/onboarding-email-sequence-writer/

OpenAI Codex

.codex/skills/onboarding-email-sequence-writer/

Cursor

.cursor/skills/onboarding-email-sequence-writer/ (or ~/.cursor/skills/onboarding-email-sequence-writer/ globally)

Compatibility

Any WordPress site with an email marketing or automation plugin, or a transactional email provider; output is plain subject lines and body copy to paste in.

The complete SKILL.md for this skill:

---
name: onboarding-email-sequence-writer
description: Use when a user wants a new-user onboarding email sequence drafted, or asks for a "welcome series" or "onboarding drip campaign".
---

# Onboarding Email Sequence Writer

## When to use
New users are signing up but need a structured push toward actually using the product, and the user wants an onboarding email sequence rather than a single welcome email.

## Procedure
1. Identify the single action that best predicts a new user sticks around, and design the sequence around getting them there.
2. Draft 3-5 emails spaced across the first 1-14 days, each with one specific goal and one specific call to action.
3. Write each subject line to state the benefit or next step plainly, avoiding vague hype phrasing.
4. Phrase each email so it still makes sense whether the user completed the prior step or skipped ahead.
5. End the sequence with a check-in email asking if they're stuck, with a real way to reply to a human.

## Guardrails
- Don't use fake urgency or scarcity language that isn't true for the product.
- Keep claims about the product accurate to what it actually does, don't overpromise features in a welcome email.