Content · Claude Code skill

Email Sequence Builder skill and the Yalc Framework

The drafting skill for any multi-email lifecycle program. Covers cold drips, nurtures, onboarding, welcome, and re-engagement.

Yalc Fit Score
8/10
License
MIT (Yalc)
Sequence types
6 covered
Output
Markdown drafts
Last reviewed
2026-04-29
Trigger phrases

Say this to fire the Email Sequence Builder skill

Any of these natural language phrases activates the skill inside Claude Code.

create an email sequence
build a drip campaign
nurture sequence for <audience>
onboarding emails for <product>
welcome sequence
re-engagement emails
email automation
lifecycle emails
What it does

Email Sequence Builder, plainly

The Email Sequence Builder takes a brief (audience, goal, sequence type, tone) and produces a 3 to 7 email sequence with subject lines, send timing, and personalization slots. Output is markdown drafts ready for review and import into Instantly, Lemlist, or HubSpot's sequence tool.

The skill covers 6 sequence types: cold outbound drip (when prospects haven't engaged yet), nurture (post-engagement), onboarding (post-signup), welcome (immediately after signup), re-engagement (lapsed users), and lifecycle (multi-month programs). Each type has its own template structure, timing recommendations, and tone defaults.

Where it slots in

Position in the GTM operating system

Intake
Enrich
Score
Route
Draft
Send
Listen

The Email Sequence Builder sits at the **draft** node for email content. It pairs with `instantly` (for cold drip execution) or directly feeds into HubSpot's sequence tool. The skill drafts; the send tools execute.

For Yalc workflows, this skill is invoked when the operator describes a multi-email goal in natural language: "build me a 5 email re-engagement sequence for users inactive 30+ days". Output is a structured draft ready for human review.

The Yalc Framework

Running the Email Sequence Builder skill end to end

Workflow position

The email sequence drafter. Yalc takes a brief, returns a sequence. Downstream skills handle the actual send.

Required inputs

  • → Sequence type (cold drip, nurture, onboarding, welcome, re-engagement, lifecycle)
  • → Audience definition (who receives this sequence)
  • → Goal (what do you want them to do)
  • → Brand tone (formal, casual, technical, etc.)
  • → Personalization tokens available (first name, company, product, etc.)
  • → [object Object]

Outputs

  • → Markdown sequence draft with each email's subject, body, send timing, personalization slots
  • → Send schedule recommendations
  • → Subject line A B testing variants if requested
  • → Notes on which emails are gating (must open before next sends) vs evergreen

Chaining recommendations

UpstreamYalc prompt with sequence brief → email-sequence
DownstreamSequence draft → Instantly or Lemlist or HubSpot (manual import)

Anti patterns to avoid

Don't skip the goal definition. "Engagement" is too vague; specify the action you want (book a demo, complete onboarding, reactivate, etc.).
Don't run a 7-email cold drip without warmup. New domains need 2 to 4 weeks of warmup before any cold sequence sends.
Don't reuse onboarding sequences for re-engagement. Different audience state, different message arc. Each type has its own template.
Operator take

Pros, cons, who it's for

Pros

  • 6 sequence types cover most B2B lifecycle email patterns
  • Output is markdown, easy to review and edit
  • Subject line variants on demand for A B testing
  • Personalization slots clearly marked, no guesswork on imports
  • Tone customization based on brand voice files

Cons

  • Drafts only; you import to your sender of choice manually
  • No native HubSpot or Salesforce sequence-tool integration (output is meant for human review)
  • Cold drip output assumes you've done the deliverability work (warm-up, domain setup)
  • Sequence templates skew toward B2B SaaS context. B2C lifecycle works but requires more prompt customization.

Who it's for

  • GTM operators producing sequences for cold drip, nurture, or onboarding
  • Marketing functions writing lifecycle programs without a copywriter
  • Founders writing welcome and re-engagement sequences in their own voice
Dependencies

What this skill expects to find

The skill is self-contained. It produces drafts; you handle the send via your email tool of choice. For Instantly users, the linkedin-post skill conventions apply for tone (no AI tells, no em dashes, no marketing speak in cold sends).

Related

The Email Sequence Builder ecosystem inside Yalc

Alternatives

Skills that overlap

FAQ

Frequently asked

How long is a typical sequence?

Cold drip is 3 to 5 emails over 2 weeks. Nurture is 4 to 7 over a month. Onboarding is 5 to 7 over the first 2 weeks. Welcome is 1 to 3 immediate. Re-engagement is 3 to 4 over a week. Lifecycle programs are case by case.

Does the skill handle send timing?

It recommends timing (Day 1, Day 4, Day 7, etc.) and time-of-day windows for each email. Actual scheduling lives in your sender tool.

Can the skill personalize based on real prospect data?

It marks personalization slots (first name, company, role, recent action). The actual data injection happens in the sender tool. The skill assumes you have the data.

Will the output sound generic?

Only if you skip the brand voice input. Provide 2 or 3 sample emails in your voice and the skill grounds output accordingly. Without voice grounding, output skews neutral and templated.

Does it work for non-English sequences?

Yes. Specify language in the input. Quality is best for major European languages and English.

How do I A B test subject lines?

Ask for 3 to 5 variants per subject line. The skill produces variants tuned for different angles (curiosity, value-first, urgency, social proof, direct).

Get the Email Sequence Builder skill

Clone the Yalc skill set, drop in your env, run from your next Claude Code session.

gh repo clone Othmane-Khadri/YALC-the-GTM-operating-system && cp -r YALC-the-GTM-operating-system/.claude/skills/email-sequence ./.claude/skills/