メニュー
Designs automated drip and onboarding email sequences that activate users. Use when building a new onboarding flow, extending a drip series, or diagnosing low activation rates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | Email Drip Builder |
| description | Designs automated drip and onboarding email sequences that activate users. Use when building a new onboarding flow, extending a drip series, or diagnosing low activation rates. |
A drip sequence is a contract with the user: they gave you their attention, and you will return it with value at the right moment. Sequences that read like mail merges get unsubscribes. Sequences timed to behavior build habits.
Email 1 sends immediately on signup and has one job: show the user the fastest path to the product's core value. No feature tour. No company history. One action, one link. Subject line states the outcome, not the product name.
Emails 2 through 5 fire based on what the user has not done, not on a fixed timer. If the user completed the target action from Email 1, skip Email 2 and advance to the next milestone. Fixed-timer sequences waste sends on users who are already activated.
Every email in the sequence must deliver something independently useful: a tip, a benchmark, a shortcut, a case study. If a user unsubscribes after reading Email 3, they should still have gotten value from the sequence. This reduces unsubscribe rates and builds sender trust.
A subject line is a promise about what is inside. Match the promise exactly. Bait-and-switch subjects boost open rates and tank click rates. The best subject lines are specific and slightly incomplete: the body finishes the thought.
Define one milestone action that means the user is activated. Once they hit it, stop the onboarding drip immediately and move them to the engagement track. Sending onboarding emails to already-activated users erodes trust and skews engagement metrics.
If a user has not activated after eight emails, a ninth will not fix it. Move them to a dormant segment and address them with a win-back campaign instead. Endless drips that never resolve create unsubscribe pressure across the entire list.
Drafts a margin-aware 3-email cart-recovery sequence that reminds, handles objections, then incentivizes only as a last touch. Use when a checkout is started but not completed and you need cart-recovery (abandoned-cart) emails, when wiring an abandoned-cart flow in Shopify, Klaviyo, or similar, or when asked to recover lost carts without overspending on discounts.
Writes an Amazon product title, five bullets, and backend search terms that obey Amazon's character, byte, and keyword rules while staying click-worthy in the search grid. Use when drafting or fixing a Seller Central listing, rewriting an Amazon title or bullet points, packing backend search terms, or recovering a listing flagged or suppressed for content. Do NOT use when writing on-site product-detail-page copy for your own storefront or marketing site — use product-description-writer instead.
Write the intro and lower-page copy for an ecommerce collection or category page so it ranks for a commercial query while pushing shoppers toward a product fast. Use when you have a collection/category page (e.g. "women's merino base layers", "standing desks") and need the above-grid intro blurb, the H1, and the supporting SEO content below the product grid. Do NOT use for standalone marketing or campaign landing pages — use landing-page-copy instead; do NOT use for a single product's description — use product-description-writer instead.
Builds an honest "X vs Y" or "best alternative to X" comparison page — scannable table plus use-case routing copy — for high-intent commercial searches. Use when the user wants to create a "vs" or "alternative-to" page, a competitor comparison table, or copy that names a rival and asks which product to choose.
Writes the single on-site PDP master copy — a benefit-led, scannable product detail page in the brand's voice — from a raw spec sheet or feature list. Use when you have a spec list, feature bullets, or a bare template description for one product and need conversion copy for its on-site product detail page. Do NOT use for Amazon or marketplace listings — use amazon-listing-optimizer instead; do NOT use to spin one master into many size/color variants — use variant-copy-scaler instead.
Mines customer reviews and Q&A into a pre-purchase PDP FAQ and objection-handling block that answers shopper hesitation before it forms. Use when you have a review or Q&A export and want to write or rebuild a product page FAQ, reduce returns from preventable surprises, or shoppers keep asking the same pre-purchase questions. Do NOT use when analyzing support tickets or CSAT/NPS verbatims to find quality root causes — use CSAT Root Cause Analysis instead.
