Claude skill

Welcome flow

A Claude skill that turns a one-email welcome into a 3-7 email architecture with a bought-vs-not split, copy angles, and subject lines. For email leads whose welcome is a greeting, not a first segmentation pass.

What it does

Give it list context. It gives you four things:

  1. Architecture table. Number of emails, delay, and the one job of each email. Three to seven emails. Not a greeting sequence.
  2. Segment routing. A bought-vs-not split at minimum. More splits only if the context justifies them. It will say so if it does not.
  3. Copy angles. Per segment, per email: hook, body note, subject (under 50 characters), preview text, and one primary CTA.
  4. Filter sketch. Plain-language description of what the Klaviyo or platform filter should check.

Works in: Claude (claude.ai Projects or the desktop app), Cursor

Rules inside the skill: no invented statistics, no fake urgency, no dark patterns, no em dashes, no discount in email one unless the opt-in offered one

Sample input / output

You give it

"Our welcome is one generic email, then campaigns. About 20 percent of the list has already bought. Most people came from Instagram ads."

It produces

Architecture: 5 emails, delays, one job each

Routing: bought vs not-yet from email one

Copy angles: hook, subject, preview, one CTA per email per track

Filter sketch: what the platform should check

How to install

  1. Subscribe below. The SKILL.md file link arrives in the first email.
  2. Download the file. Create a folder: .claude/skills/margarita-welcome-flow/
  3. Put SKILL.md inside that folder.
  4. In Claude, start a new project and use "Add to project knowledge" to include the skill folder.
  5. Begin with: "Use the margarita-welcome-flow skill" and paste your list context.

Cursor users: place the folder at .agents/skills/margarita-welcome-flow/.

Who it is for

  • Email lead whose welcome is still one generic email
  • Founder who runs their own Klaviyo and wants routing before they write copy
  • Operator who knows the list leaks at welcome, not at the campaign

It is not a full copy deck. It produces architecture and direction. You (or we) write the emails from that.