copywriter-email-sequences

Design lifecycle email sequences with triggers, timing, branching, and per-email copy.

6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/lookatitude/guild --skill copywriter-email-sequences
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: copywriter-email-sequences
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/copywriter-email-sequences
Command: npx skills add https://github.com/lookatitude/guild --skill copywriter-email-sequences

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes lifecycle, onboarding, transactional, re-engagement, and drip email sequences — the sequence plan (triggers, timing, branching) plus per-email subject, preview, and body copy. Pulled by the copywriter specialist. Trigger examples include onboarding sequence, welcome drip, re-engagement for dormant users, trial-ending sequence, transactional email copy for X, and lifecycle flow design. Do not trigger for cold outbound or prospecting sequences (use sales-cold-outreach), sales follow-up after a booked call (use sales-follow-up-sequence), long-form blog content (use copywriter-long-form), in-product strings (use copywriter-product-microcopy), launch announcement strategy (marketing-launch-plan), or social media posts (social-media-platform-post).

Core Features & Use Cases

  • Define concrete entry triggers (e.g., onboarding sequence, user inactivity) and specify timing with offsets (e.g., +0h, +24h, +7d) to shape when each email sends.
  • Build branching logic to handle cases like opened-but-didn't-click vs never-opened vs completed-action, determining the next step in the sequence.
  • Produce the full per-email content: subject (including A/B variants where relevant), preview text, body copy, a single CTA, and unsubscribe/footer compliance.
  • Output a two-layer Markdown plan: a sequence table (step · delay · trigger · goal · branch-out) and per-email blocks with the actual copy, stored under .guild/runs/<run-id>/copy/emails-<slug>.md for traceability.

Quick Start

Provide the onboarding sequence target and ask the AI to generate the full plan and email copy.

Frequently Asked Questions about copywriter-email-sequences

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate lifecycle email sequences with branching logic and timing?▼

Automate lifecycle email sequences by defining entry triggers, applying time offsets like +0h or +7d for send timing, and building branch logic for opened-but-didn't-click or completed-action cases to route users through the flow.

What is the best way to write a re-engagement email sequence for dormant users?▼

Write a re-engagement email sequence by specifying a user inactivity trigger, setting sequential delays between emails, and generating per-email copy with subject lines, preview text, body content, and a single CTA to win back dormant users.

Can I generate onboarding drip email copy with A/B subject line variants?▼

Generate onboarding drip email copy with A/B subject line variants by providing your onboarding target, which produces a sequence plan and per-email blocks including subject variants, preview text, body copy, CTAs, and unsubscribe footer compliance.

Does this email sequence copywriting tool work for cold outbound prospecting campaigns?▼

This email sequence copywriting tool does not work for cold outbound prospecting campaigns. It is designed exclusively for existing users covering onboarding, transactional, re-engagement, and lifecycle flows, avoiding cold sales outreach.

How do I structure a transactional email sequence for trial-ending reminders?▼

Structure a transactional email sequence for trial-ending reminders by defining a trial expiration trigger, applying time offsets for pre-expiration alerts, and outputting a step-by-step sequence table alongside the per-email copy.

What format does the generated email sequence plan use for deployment readiness?▼

The generated email sequence plan uses a two-layer Markdown format: a sequence table detailing step, delay, trigger, goal, and branch-out, followed by per-email copy blocks, stored under a specific run directory for traceability.