菜单
When the user wants to create or optimize an email sequence, drip campaign, or lifecycle email program — "nurture sequence," "onboarding emails," "welcome series," "re-engagement," "email automation," "email cadence," or any multi-email automated flow. For cold outreach, see cold-email. For in-app onboarding, see onboarding-cro.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When the user wants to write, rewrite, or improve marketing copy for any page — homepage, landing, pricing, feature, about, or product pages; "headline help," "CTA copy," "value proposition," "tagline," "hero section," "make this more compelling," "conversion copy," or complete Figma-ready full-page copy (see Full-Page Mode below). For email copy, see email-sequence. For popups, see popup-cro. For editing existing copy, see copy-editing.
When the user wants to increase conversions on any marketing page — homepage, landing, pricing, feature, or blog; "CRO," "this page isn't converting," "low conversion rate," "bounce rate," "my landing page sucks" — or just shares a URL asking for feedback. For signup flows, see signup-flow-cro; post-signup activation, onboarding-cro; forms, form-cro; popups, popup-cro.
When the user wants to audit or diagnose SEO issues — "technical SEO," "why am I not ranking," "meta tags review," "my traffic dropped," "Google update hit me," "core web vitals," "crawl errors," "indexing issues," or even a vague "my SEO is bad." For pages at scale, see programmatic-seo. For structured data, see schema-markup. For AI search, see ai-seo.
Coder<->reviewer handoff loop (Claude<->Codex, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
| name | email-sequence |
| description | When the user wants to create or optimize an email sequence, drip campaign, or lifecycle email program — "nurture sequence," "onboarding emails," "welcome series," "re-engagement," "email automation," "email cadence," or any multi-email automated flow. For cold outreach, see cold-email. For in-app onboarding, see onboarding-cro. |
| category | marketing |
| tier | on-demand |
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Establish:
One primary purpose and 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. Segment for relevance. Quality > frequency.
Every email moves them somewhere. Links should do something useful. Make next steps obvious.
Welcome 3-7 emails; lead nurture 5-10; onboarding 5-10; re-engagement 3-5 — scaled by sales cycle length, product complexity, and relationship stage.
Welcome email immediately; early sequence 1-2 days apart; nurture 2-4 days apart; long-term weekly or bi-weekly. B2B: avoid weekends. B2C: test weekends. Send at local time.
Clear > clever. Specific > vague. Benefit or curiosity-driven. 40-60 characters ideal. Test emoji (they're polarizing).
Patterns that work:
Extends the subject line, ~90-140 characters. Don't repeat the subject — complete the thought or add intrigue.
Length: 5-7 emails over 12-14 days. Goal: Activate, build trust, convert.
Length: 6-8 emails over 2-3 weeks. Goal: Build trust, demonstrate expertise, convert.
Length: 3-4 emails over 2 weeks. Trigger: 30-60 days of inactivity. Goal: Win back or clean list.
Length: 5-7 emails over 14 days. Goal: Activate, drive to aha moment, upgrade. Coordinate with in-app onboarding — email supports, doesn't duplicate.
Detailed templates: references/sequence-templates.md
Detailed email type reference: references/email-types.md
Short paragraphs (1-3 sentences), white space between sections, bullets for scanability, bold sparingly, mobile-first (most read on phone).
Conversational, not formal. First-person (I/we) and second-person (you). Active voice. Read it out loud — does it sound human?
50-125 words transactional; 150-300 educational; 300-500 story-driven.
Buttons for primary actions, links for secondary. One clear primary CTA per email. Button text: action + outcome.
Detailed copy, personalization, and testing guidelines: references/copy-guidelines.md
Sequence Name: [Name]
Trigger: [What starts the sequence]
Goal: [Primary conversion goal]
Length: [Number of emails]
Timing: [Delay between emails]
Exit Conditions: [When they leave the sequence]
Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]
What to measure and benchmarks.
For implementation, see the tools registry. Key email tools:
| Tool | Best For | MCP | Guide |
|---|---|---|---|
| Customer.io | Behavior-based automation | - | customer-io.md |
| Mailchimp | SMB email marketing | ✓ | mailchimp.md |
| Resend | Developer-friendly transactional | ✓ | resend.md |
| SendGrid | Transactional email at scale | - | sendgrid.md |
| Kit | Creator/newsletter focused | - | kit.md |