sequence-best-practices
Email sequence design and optimization best practices
Best use case
sequence-best-practices is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Email sequence design and optimization best practices
Teams using sequence-best-practices should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sequence-best-practices/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sequence-best-practices Compares
| Feature / Agent | sequence-best-practices | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Email sequence design and optimization best practices
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
plugin: instantly
updated: 2026-01-20
# Sequence Best Practices
## Sequence Structure
### Standard 5-Step Sequence
| Step | Day | Purpose | Email Type |
|------|-----|---------|------------|
| 1 | 0 | Initial outreach | Problem + value prop |
| 2 | 3 | Social proof | Case study / results |
| 3 | 7 | Alternative angle | Different value prop |
| 4 | 10 | Soft breakup | "If not a fit..." |
| 5 | 14 | Breakup | Last attempt, value-add |
### Extended 7-Step Sequence
| Step | Day | Purpose | Email Type |
|------|-----|---------|------------|
| 1 | 0 | Initial outreach | Problem + value prop |
| 2 | 2 | Quick follow-up | Bump + new angle |
| 3 | 5 | Social proof | Case study |
| 4 | 8 | Value-add | Free resource |
| 5 | 12 | Alternative angle | Different ICP pain |
| 6 | 16 | Soft breakup | Check-in |
| 7 | 21 | Breakup | Final attempt |
## Timing Guidelines
### Optimal Delays
| Between Emails | Recommended | Reasoning |
|----------------|-------------|-----------|
| Email 1 -> 2 | 2-3 days | Stay top of mind |
| Email 2 -> 3 | 3-4 days | Let social proof sink in |
| Email 3 -> 4 | 3-4 days | Give time to consider |
| Email 4 -> 5 | 4-5 days | Breakup needs space |
| After breakup | 30+ days | Cool-off period |
### Send Time Optimization
```
Best Days: Tuesday, Wednesday, Thursday
Best Times:
- 8-10am recipient local time (start of day)
- 2-4pm recipient local time (post-lunch)
Worst Days: Monday morning, Friday afternoon
Worst Times: After 6pm, before 7am
```
## Email Copy Guidelines
### Length Guidelines
| Email Type | Word Count | Lines | Reason |
|------------|------------|-------|--------|
| Cold outreach | 50-100 | 5-8 | Scannable |
| Follow-up | 30-60 | 3-5 | Quick bump |
| Case study | 100-150 | 8-12 | Tell story |
| Breakup | 40-80 | 4-6 | Clear finale |
### Structure Template
```
[Personalized opening - 1 line]
[Problem statement or insight - 2-3 lines]
[Brief value proposition - 1-2 lines]
[CTA - 1 line]
[Signature]
```
### Subject Line Best Practices
| Do | Don't |
|----|-------|
| Keep 3-7 words | Write novel-length subjects |
| Use {{first_name}} or {{company}} | Over-personalize ("Saw you on LinkedIn...") |
| Create curiosity | Mislead with clickbait |
| Be specific when possible | Use generic templates |
| Test lowercase | Use ALL CAPS |
**Examples:**
- Good: "{{first_name}}, quick question"
- Good: "idea for {{company}}'s Q2"
- Bad: "RE: Our meeting" (fake reply)
- Bad: "FREE TRIAL INSIDE!!!" (spam trigger)
### CTA Best Practices
| CTA Type | Example | When to Use |
|----------|---------|-------------|
| Soft | "Thoughts?" | Early in sequence |
| Medium | "Worth a quick chat?" | Middle of sequence |
| Direct | "15 min this week?" | After engagement signals |
| Breakup | "Should I close the loop?" | Final email |
**One CTA Per Email:** Never give multiple options.
## Personalization Strategy
### Personalization Tokens
| Token | Example | Priority |
|-------|---------|----------|
| {{first_name}} | "Hey Sarah," | Required |
| {{company}} | "saw {{company}}'s recent..." | Recommended |
| {{title}} | "As a {{title}}, you..." | If relevant |
| {{industry}} | "In {{industry}}, we see..." | For segmented |
### Custom Personalization
| Level | Effort | Impact |
|-------|--------|--------|
| Basic | Low | {{first_name}}, {{company}} |
| Medium | Medium | + recent company news, role-specific |
| High | High | + mutual connections, specific insight |
**Rule:** Personalize opening line at minimum. Rest can be templated.
## Avoiding Spam Triggers
### Words to Avoid
```
FREE, GUARANTEE, WINNER, CASH, URGENT
Click here, Act now, Limited time, Don't miss
!!!!, ALL CAPS, $$$$
```
### Technical Best Practices
| Practice | Reason |
|----------|--------|
| No images in cold emails | Trigger spam filters |
| Max 1 link per email | Multiple links = spam |
| No HTML formatting | Plain text performs better |
| Short sentences | Looks more personal |
| No attachments | Major spam trigger |
## Sequence Psychology
### Email 1: The Opening
**Goal:** Establish relevance, create curiosity
**Approach:** Problem-focused, not product-focused
**Length:** 50-80 words
### Email 2: The Follow-Up
**Goal:** Add credibility via social proof
**Approach:** "Here's what happened when..."
**Length:** 60-100 words
### Email 3: The Pivot
**Goal:** Try different angle
**Approach:** Different pain point or benefit
**Length:** 50-80 words
### Email 4: The Soft Breakup
**Goal:** Create scarcity without desperation
**Approach:** "If this isn't a priority..."
**Length:** 40-60 words
### Email 5: The Breakup
**Goal:** Last attempt, leave door open
**Approach:** Value-add (resource) + clear close
**Length:** 50-80 wordsRelated Skills
test-skill
A test skill for validation testing. Use when testing skill parsing and validation logic.
bad-skill
This skill has invalid YAML in frontmatter
release
Plugin release process for MAG Claude Plugins marketplace. Covers version bumping, marketplace.json updates, git tagging, and common mistakes. Use when releasing new plugin versions or troubleshooting update issues.
openrouter-trending-models
Fetch trending programming models from OpenRouter rankings. Use when selecting models for multi-model review, updating model recommendations, or researching current AI coding trends. Provides model IDs, context windows, pricing, and usage statistics from the most recent week.
Claudish Integration Skill
**Version:** 1.0.0
transcription
Audio/video transcription using OpenAI Whisper. Covers installation, model selection, transcript formats (SRT, VTT, JSON), timing synchronization, and speaker diarization. Use when transcribing media or generating subtitles.
final-cut-pro
Apple Final Cut Pro FCPXML format reference. Covers project structure, timeline creation, clip references, effects, and transitions. Use when generating FCP projects or understanding FCPXML structure.
ffmpeg-core
FFmpeg fundamentals for video/audio manipulation. Covers common operations (trim, concat, convert, extract), codec selection, filter chains, and performance optimization. Use when planning or executing video processing tasks.
statusline-customization
Configuration reference and troubleshooting for the statusline plugin — sections, themes, bar widths, and script architecture
technical-audit
Technical SEO audit methodology including crawlability, indexability, and Core Web Vitals analysis. Use when auditing pages or sites for technical SEO issues.
serp-analysis
SERP analysis techniques for intent classification, feature identification, and competitive intelligence. Use when analyzing search results for content strategy.
schema-markup
Schema.org markup implementation patterns for rich results. Use when adding structured data to content for enhanced SERP appearances.