用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/MadAppGang/claude-code --skill sequence-best-practices命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
Use when starting isolated feature work or before executing implementation plans. Manages full worktree lifecycle from creation through cleanup with safety checks and error recovery.
Configuration reference and troubleshooting for the statusline plugin — sections, themes, bar widths, and script architecture
Common agent patterns and templates for Claude Code. Use when implementing agents to follow proven patterns for Tasks integration, quality checks, and external model invocation via claudish CLI.
正在显示 SKILL.md
| name | sequence-best-practices |
| version | 1.0.0 |
| description | Email sequence design and optimization best practices |
plugin: instantly updated: 2026-01-20
| 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 |
| 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 |
| 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 |
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 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 |
[Personalized opening - 1 line]
[Problem statement or insight - 2-3 lines]
[Brief value proposition - 1-2 lines]
[CTA - 1 line]
[Signature]
| 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:
| 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.
| 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 |
| 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.
FREE, GUARANTEE, WINNER, CASH, URGENT
Click here, Act now, Limited time, Don't miss
!!!!, ALL CAPS, $$$$
| 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 |
Goal: Establish relevance, create curiosity Approach: Problem-focused, not product-focused Length: 50-80 words
Goal: Add credibility via social proof Approach: "Here's what happened when..." Length: 60-100 words
Goal: Try different angle Approach: Different pain point or benefit Length: 50-80 words
Goal: Create scarcity without desperation Approach: "If this isn't a priority..." Length: 40-60 words
Goal: Last attempt, leave door open Approach: Value-add (resource) + clear close Length: 50-80 words