ワンクリックで
email-marketing
Email marketing automation — drip sequences, deliverability, template patterns, provider APIs (Resend, SendGrid, Postmark)
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Email marketing automation — drip sequences, deliverability, template patterns, provider APIs (Resend, SendGrid, Postmark)
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Funnel diagnostics engine — bottleneck detection, cross-data correlation, AARRR benchmarks by vertical
High-Velocity Advertising (HVA) — the discipline for creative discovery at machine speed. CLEAR decision rule, the five-layer Stack, the Read Ladder, the two-clocks asymmetry, Benjamini-Hochberg correction, the Vault moat, and the Fit Boundary. The spec behind /hva, /hva-forge, /hva-lint, /hva-review, /hva-vault and the hva-desk agent.
Direct response copywriting framework for paid ads — Hormozi offers, PAS, AIDA, variation generation, LATAM hooks
Synthetic Demand Validation (SDV) — predict purchase intent, price tolerance, and objections for ad creatives, offers, and landing copy by eliciting free-text reactions from a synthetic persona panel and mapping them to Likert distributions. Comparative ranking is the headline signal. Use for "will this convert", "which variant wins", "is $X the right price", "pre-test this creative/offer/copy before spend".
Cross-channel GTM orchestration — channel sequencing, attribution models, retargeting chains, multi-touch journeys
Google Ads expertise — read/measure via the google-ads-open CLI + REST :mutate deploy, signal-first architecture (Hagakure, brand isolation, intent ladder, 5-pillar budget), Performance Max control + Moran feeder, Smart Bidding migration ladder, Enhanced Conversions + Consent Mode v2 + GCLID-to-CRM, broad-match-era keywords + n-gram mining, AI Max for Search, RSA/YouTube creative, policy/reinstatement. Ethical scores (whitehat/grayhat/blackhat 1-10) from the Google Ads Atlas 2026.
| name | email-marketing |
| description | Email marketing automation — drip sequences, deliverability, template patterns, provider APIs (Resend, SendGrid, Postmark) |
Design, build, and optimize email marketing flows for SaaS GTM. This skill covers drip sequence architecture, deliverability engineering, template design patterns, and provider API integration.
Email System
├── Transactional Emails (account confirmations, password resets, receipts)
│ └── Triggered by user actions, must send immediately
├── Marketing Emails (newsletters, announcements, product updates)
│ └── Sent to segments on a schedule
├── Drip Sequences (automated multi-email flows)
│ └── Triggered by events, sent on a delay schedule
└── Lifecycle Emails (onboarding, activation, retention, win-back)
└── Triggered by user state changes or inactivity
Day 0 (immediate): Welcome + quick-start guide
Day 1: Key feature highlight + "try this" CTA
Day 3: Social proof (testimonials, case studies)
Day 5: "Need help?" with support links + community invite
Day 7: Activation check — if not activated, branch to re-engagement
Day 2: "You're 1 step away" — focus on the activation action
Day 4: Video walkthrough of the core feature
Day 7: Success story of someone who activated
Day 10: Direct offer — "Reply to this email and I'll help you set up"
Day 14: Final nudge — "Is [Product] right for you?"
Day 0: Trial confirmation + what to expect
Day 3: Feature highlight #1 (most valuable)
Day 5: Feature highlight #2 + comparison to alternatives
Day 7 (mid-trial): Progress check + premium feature preview
Day 10: Customer success story + ROI data
Day 12 (2 days before): Urgency — "Your trial ends in 2 days"
Day 13 (1 day before): Last chance — clear pricing, FAQ
Day 14 (expiry): "Your trial has ended" — extend offer or discount
Day 16 (grace): "We saved your data" — final conversion attempt
Day 7 inactive: "We miss you" + new feature announcement
Day 14 inactive: "Here's what you're missing" + activity digest
Day 21 inactive: Re-engagement offer (discount, extended trial)
Day 30 inactive: "Is everything okay?" — personal outreach feel
Day 45 inactive: Win-back offer (significant discount)
Day 60 inactive: Final email — "Should we close your account?"
Day 0: "You're hitting limits" — data on their usage
Day 2: Feature comparison (current plan vs next tier)
Day 5: ROI calculator or case study of upgrade
Day 7: Limited-time upgrade offer
Day 10: Follow-up if no action taken
| Metric | Healthy Range | Action if Below |
|---|---|---|
| Open Rate | 25-45% | Fix subject lines, sender name, send time |
| Click Rate | 3-8% | Fix CTA, content relevance, design |
| Reply Rate | 1-3% | More personal tone, ask questions |
| Unsubscribe Rate | <0.5% per email | Reduce frequency, improve segmentation |
| Bounce Rate | <2% | Clean list, verify emails at signup |
| Spam Complaint Rate | <0.1% | Critical — fix immediately or domain gets blacklisted |
| Segment | Criteria | Use For |
|---|---|---|
| Power Users | 5+ logins/week, multiple features used | Upsell, referral asks, testimonial requests |
| Engaged | 2-4 logins/week | Feature education, community building |
| At Risk | 1 login/week, declining | Re-engagement, value reminders |
| Dormant | 0 logins for 14+ days | Win-back sequences |
| Churned | Cancelled or expired | Win-back with offers |
| Segment | Stage | Primary Goal |
|---|---|---|
| New Signups | Onboarding | Activation (complete key action) |
| Activated | Using product | Engagement + habit formation |
| Trial Users | Pre-payment | Conversion to paid |
| Paying Customers | Retention | Expansion + advocacy |
| Churned | Lost | Win-back |
Behavioral and lifecycle segments above tell you what a user is doing; the shared persona substrate (.gtm/personas/, schemas/persona.schema.json) and SDV forecasts (.gtm/sdv/forecasts/*.forecast.yml) tell you what they object to and what price they tolerate — build the persona once, consume it here. Cross the two axes:
pain_points, and each SDV forecast carries structured top_objections[] (segment + objection + severity + blocker_tier B0/B1/B2 + revenue_at_risk). Map the highest-severity objection for the persona(s) in a segment to a specific email: the email that names and dissolves that exact objection. A B0 demand-blocker for a paying persona earns its own dedicated email; a B2 polish objection is a PS line. This is the routing rule — one SDV-discovered objection, one email that answers it — not generic benefit copy.price_sensitivity (low/medium/high) and any SDV willingness_to_pay band (Van Westendorp / Gabor-Granger range) set how an upsell/trial-to-paid email frames price: lead with value and a guarantee for high-sensitivity personas (and the lower offer tier), lead with the premium outcome for low-sensitivity personas. Never send the same discount framing to a low and a high price_sensitivity segment.revenue_pct and the objection's revenue_at_risk — handle the objection costing the most revenue first.If .gtm/personas/ is empty, recommend /gtm-personas derive; if no SDV forecast exists yet, recommend /gtm-validate to discover objections before writing the objection-handling emails (the forecast's top_objections[] is the input, not a guess).