Email Sequence Design workflow skill. Use this skill when the user needs You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Email Sequence Design workflow skill. Use this skill when the user needs You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/email-sequence from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Email Sequence Design You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Initial Assessment, Email Sequence Strategy, Sequence Templates, Email Audit Checklist, Personalization, Segmentation Strategies.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Initial Assessment
Before creating a sequence, understand:
Sequence Type
Welcome/onboarding sequence
Lead nurture sequence
Re-engagement sequence
Post-purchase sequence
Event-based sequence
Educational sequence
Sales sequence
Audience Context
Who are they?
What triggered them into this sequence?
What do they already know/believe?
What's their current relationship with you?
Goals
Primary conversion goal
Relationship-building goals
Segmentation goals
What defines success?
Examples
Example 1: Ask for the upstream workflow directly
Use @email-sequence to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @email-sequence against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @email-sequence for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @email-sequence using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Each email has one primary purpose
One main CTA per email
Don't try to do everything
Lead with usefulness
Build trust through content
Earn the right to sell
Fewer, better emails win
Imported Operating Notes
Imported: Core Principles
1. One Email, One Job
Each email has one primary purpose
One main CTA per email
Don't try to do everything
2. Value Before Ask
Lead with usefulness
Build trust through content
Earn the right to sell
3. Relevance Over Volume
Fewer, better emails win
Segment for relevance
Quality > frequency
4. Clear Path Forward
Every email moves them somewhere
Links should do something useful
Make next steps obvious
Imported: Email Copy Guidelines
Structure
Hook: First line grabs attention
Context: Why this matters to them
Value: The useful content
CTA: What to do next
Sign-off: Human, warm close
Formatting
Short paragraphs (1-3 sentences)
White space between sections
Bullet points for scanability
Bold for emphasis (sparingly)
Mobile-first (most read on phone)
Tone
Conversational, not formal
First-person (I/we) and second-person (you)
Active voice
Match your brand but lean friendly
Read it out loud—does it sound human?
Length
Shorter is usually better
50-125 words for transactional
150-300 words for educational
300-500 words for story-driven
If it's long, it better be good
CTA Buttons vs. Links
Buttons: Primary actions, high-visibility
Links: Secondary actions, in-text
One clear primary CTA per email
Button text: Action + outcome
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/email-sequence, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Email Types Reference
A comprehensive guide to lifecycle and campaign emails. Use this as an audit checklist and implementation reference.
Onboarding Emails
New Users Series
Trigger: User signs up (free or trial)
Goal: Activate user, drive to aha moment
Typical sequence: 5-7 emails over 14 days
Email 1: Welcome + single next step (immediate)
Email 2: Quick win / getting started (day 1)
Email 3: Key feature highlight (day 3)
Email 4: Success story / social proof (day 5)
Email 5: Check-in + offer help (day 7)
Email 6: Advanced tip (day 10)
Email 7: Upgrade prompt or next milestone (day 14)
Key metrics: Activation rate, feature adoption
New Customers Series
Trigger: User converts to paid
Goal: Reinforce purchase decision, drive adoption, reduce early churn
Typical sequence: 3-5 emails over 14 days
Email 1: Thank you + what's next (immediate)
Email 2: Getting full value — setup checklist (day 2)
Email 3: Pro tips for paid features (day 5)
Email 4: Success story from similar customer (day 7)
Email 5: Check-in + introduce support resources (day 14)
Key point: Different from new user series—they've committed. Focus on reinforcement and expansion, not conversion.
Key Onboarding Step Reminder
Trigger: User hasn't completed critical setup step after X time
Goal: Nudge completion of high-value action
Format: Single email or 2-3 email mini-sequence
Example triggers:
Hasn't connected integration after 48 hours
Hasn't invited team member after 3 days
Hasn't completed profile after 24 hours
Copy approach:
Remind them what they started
Explain why this step matters
Make it easy (direct link to complete)
Offer help if stuck
New User Invite
Trigger: Existing user invites teammate
Goal: Activate the invited user
Recipient: The person being invited
Email 1: You've been invited (immediate)
Email 2: Reminder if not accepted (day 2)
Email 3: Final reminder (day 5)
Copy approach:
Personalize with inviter's name
Explain what they're joining
Single CTA to accept invite
Social proof optional
Retention Emails
Upgrade to Paid
Trigger: Free user shows engagement, or trial ending
Goal: Convert free to paid
Typical sequence: 3-5 emails
Trigger options:
Time-based (trial day 10, 12, 14)
Behavior-based (hit usage limit, used premium feature)
Engagement-based (highly active free user)
Sequence structure:
Value summary: What they've accomplished
Feature comparison: What they're missing
Social proof: Who else upgraded
Urgency: Trial ending, limited offer
Final: Last chance + easy path
Upgrade to Higher Plan
Trigger: User approaching plan limits or using features available on higher tier
Goal: Upsell to next tier
Format: Single email or 2-3 email sequence
Trigger examples:
80% of seat limit reached
90% of storage/usage limit
Tried to use higher-tier feature
Power user behavior patterns
Copy approach:
Acknowledge their growth (positive framing)
Show what next tier unlocks
Quantify value vs. cost
Easy upgrade path
Ask for Review
Trigger: Customer milestone (30/60/90 days, key achievement, support resolution)
Goal: Generate social proof on G2, Capterra, app stores
Format: Single email
Best timing:
After positive support interaction
After achieving measurable result
After renewal
NOT after billing issues or bugs
Copy approach:
Thank them for being a customer
Mention specific value/milestone if possible
Explain why reviews matter (help others decide)
Direct link to review platform
Keep it short—this is an ask
Offer Support Proactively
Trigger: Signs of struggle (drop in usage, failed actions, error encounters)
Goal: Save at-risk user, improve experience
Format: Single email
Key point: Make them feel good and remind them of value delivered.
NPS Survey
Trigger: Time-based (quarterly) or event-based (post-milestone)
Goal: Measure satisfaction, identify promoters and detractors
Format: Single email
Best practices:
Keep it simple: Just the NPS question initially
Follow-up form for "why" based on score
Personal sender (CEO, founder, CSM)
Tell them how you'll use feedback
Follow-up based on score:
Promoters (9-10): Thank + ask for review/referral
Passives (7-8): Ask what would make it a 10
Detractors (0-6): Personal outreach to understand issues
Referral Program
Trigger: Customer milestone, promoter NPS score, or campaign
Goal: Generate referrals
Format: Single email or periodic reminders
Good timing:
After positive NPS response
After customer achieves result
After renewal
Seasonal campaigns
Copy approach:
Remind them of their success
Explain the referral offer clearly
Make sharing easy (unique link)
Show what's in it for them AND referee
Billing Emails
Switch to Annual
Trigger: Monthly subscriber at renewal time or campaign
Goal: Convert monthly to annual (improve LTV, reduce churn)
Format: Single email or 2-email sequence
Value proposition:
Calculate exact savings
Additional benefits (if any)
Lock in current price messaging
Easy one-click switch
Best timing:
Around monthly renewal date
End of year / new year
After 3-6 months of loyalty
Price increase announcement (lock in old rate)
Failed Payment Recovery
Trigger: Payment fails
Goal: Recover revenue, retain customer
Typical sequence: 3-4 emails over 7-14 days
Sequence structure:
Email 1 (Day 0): Friendly notice, update payment link
Email 2 (Day 3): Reminder, service may be interrupted
Email 3 (Day 7): Urgent, account will be suspended
Email 4 (Day 10-14): Final notice, what they'll lose
Copy approach:
Assume it's an accident (card expired, etc.)
Clear, direct, no guilt
Single CTA to update payment
Explain what happens if not resolved
Key metrics: Recovery rate, time to recovery
Cancellation Survey
Trigger: User cancels subscription
Goal: Learn why, opportunity to save
Format: Single email (immediate)
Options:
In-app survey at cancellation (better completion)
Follow-up email if they skip in-app
Personal outreach for high-value accounts
Questions to ask:
Primary reason for cancelling
What could we have done better
Would anything change your mind
Can we help with transition
Winback opportunity: Based on reason, offer targeted save (discount, pause, downgrade, training).
Upcoming Renewal Reminder
Trigger: X days before renewal (14 or 30 days typical)
Goal: No surprise charges, opportunity to expand
Format: Single email
