For Agents · MCP

Your task.
The right skill.

The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.

No local installationNo M11 loginRead-only

Broad task

Load 5–10 and go

SEO, Sales, Agents or another broad area → one bundle call → work.

MCP endpoint: https://skills.m11.ch/mcp

Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.

Task Packs

Marketing Foundation

Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.

Marketing Launch

Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.

Agent Audit Essentials

Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.

Conversion and Activation Review

Review the journey from landing page and lead capture through registration, first value and transparent upgrades.

Campaign Content and Brand Review

Plan a campaign, draft its channel content and review the work against actual brand guidance.

Content and Launch Planning

Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.

Customer, Market and Community Research

Understand customer needs, compare competitors and plan a community around real member value.

Lead Magnet to Lifecycle Nurture

Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.

API Contract and Observability

Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.

Data Analysis Foundation

Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.

B2B Outreach Foundation

Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.

Choose an area

01 · Category

What the MCP returns at this step

131 · Marketing · Email Operations

HyperFX Email Lifecycle

Plan provider-specific lifecycle email operations across HyperFX integrations; use Email Sequence Copy and Flow for copy planning.

hyperemailbetriebemail-lifecycle

Email Lifecycle — Multi-Provider Operations · Original SKILL.md

---
name: email-lifecycle
description: Plan, build, and run lifecycle email programs through the Hyper MCP — welcome / onboarding, nurture, re-engagement, win-back, and abandoned-cart sequences across whichever provider fits (Klaviyo for ecommerce, Resend for SaaS / dev tools, Beehiiv for newsletters, Gmail for low-volume ops). Use when the user wants to build an email sequence, set up a welcome flow, recover lapsed users, send a broadcast, manage a list / audience / segment, or asks about lifecycle / drip / nurture campaigns.
requires_toolkits:
  - klaviyo
icon: klaviyo
short_description: Welcome, nurture, win-back, and cart sequences across Klaviyo, Resend, Beehiiv, and Gmail.
---

# Email Lifecycle

End-to-end lifecycle email — pick the right provider for the job, build the audience, draft the sequence, launch, and measure. Cross-provider patterns at the top; provider-specific tool calls below.

## Out of scope — defer to other skills

| Request | Send them to |
| --- | --- |
| Cold outbound to people who haven't opted in | `cold-email-outreach` |
| Generating images for email creatives | `image-generation` |
| Generating ad creatives that run alongside the lifecycle program | `ad-creative-generation` |
| SEO research / blog content for the newsletter | `seo-research` |

## Requirements

- **Hyper MCP installed and connected.** [https://app.hyperfx.ai/mcp](https://app.hyperfx.ai/mcp)
- **At least one of these providers** connected at [https://app.hyperfx.ai/apps](https://app.hyperfx.ai/apps):
  - **Klaviyo** — ecommerce, Shopify-heavy lists, behavioral triggers off purchase / browse data
  - **Resend** — product-led / SaaS / dev tools, transactional + lifecycle on the same domain
  - **Beehiiv** — newsletters, paid-tier subscriptions, content-driven lists
  - **Gmail** — small / personal lists, founder-mode broadcasts, ops emails

If none of those tool prefixes (`klaviyo_*`, `resend_*`, `beehiiv_*`, `gmail_*`) appear in the agent's tool list, stop and tell the user to enable the Hyper MCP and connect the provider they intend to use.

### How to run the tools in this skill

Every tool in this skill is named by its canonical tool name. Run it with the call your surface gives you:

| Surface | Find a tool | Run it |
| --- | --- | --- |
| MCP client (Claude, Cursor, Codex, ChatGPT) | `search("<what you want to do>")`, then `describe("<name>")` | `call("<name>", {...})` |
| Hyper CLI | `hyperai search "<what you want to do>"`, then `hyperai describe <name>` | `hyperai call <name> --json '{...}'` |

If a tool is not found, its integration is not connected or not enabled for the workspace: stop and tell the user which integration to connect.

## Provider selection

The wrong provider is the most common reason a lifecycle program fails. Pick first.

| You are… | Use | Why |
| --- | --- | --- |
| An ecommerce / DTC brand on Shopify, BigCommerce, WooCommerce | **Klaviyo** | Native ecom event listeners (Placed Order, Started Checkout, Browsed Product), mature flow editor, tight Shopify sync. |
| A SaaS / dev tool / API product sending product + lifecycle on the same domain | **Resend** | Same API for transactional + marketing, audience management, broadcasts, automation runs. Excellent deliverability for product mail. |
| Running a content-led newsletter (free + paid tiers) | **Beehiiv** | Built around the newsletter-as-product model — segments, automations, paid tiers, referral program, post stats. |
| Running a small ops list (≤500 contacts), founder-mode broadcasts | **Gmail** | Zero new infra, label-based segmentation, easy templating. Don't scale beyond ~500 — see [`cold-email-outreach`](../cold-email-outreach) for sender deliverability if you do. |

You can run more than one. The pattern is: Klaviyo for marketing, Resend for transactional + product onboarding (when the brand also runs ecom). Or Beehiiv for the newsletter and Resend for the product. Decide once per program, not per email.

## Tool surface

| Phase | Klaviyo | Resend | Beehiiv | Gmail |
| --- | --- | --- | --- | --- |
| Audience setup | `klaviyo_lists_create`, `klaviyo_list_members_add`, `klaviyo_segments_create`, `klaviyo_profiles_create`, `klaviyo_profiles_update` | `resend_audiences_create`, `resend_contacts_create`, `resend_contacts_list`, `resend_contacts_update` | `beehiiv_subscriptions_create`, `beehiiv_segments_create`, `beehiiv_tags_add`, `beehiiv_subscriptions_list` | `gmail_labels_create`, `gmail_labels_add`, `gmail_labels_remove` |
| Sequence build | `klaviyo_campaigns_create`, `klaviyo_campaign_messages_update` | `resend_automations_create`, `resend_automations_update`, `resend_automations_get` | `beehiiv_posts_create`, `beehiiv_automations_list`, `beehiiv_automations_subscribers_add` | `gmail_drafts_create`, `gmail_drafts_update` |
| Send / launch | `klaviyo_campaigns_send`, `klaviyo_campaign_send_jobs_get` | `resend_emails_send`, `resend_broadcasts_send` | `beehiiv_posts_create` (publish), `beehiiv_posts_update` | `gmail_messages_send`, `gmail_drafts_send` |
| Measure | `klaviyo_metrics_list`, `klaviyo_metrics_get`, `klaviyo_campaigns_get` | `resend_automation_runs_list`, `resend_automation_runs_get` | `beehiiv_posts_stats_get`, `beehiiv_subscriptions_get` | `gmail_messages_list` |

Full per-provider mechanics, gotchas, and concrete tool-call examples in [`references/provider-mechanics.md`](./references/provider-mechanics.md).

## Critical rules

1. **Pick the provider before writing copy.** The mechanics of how a flow gets triggered, how a segment gets defined, and what data you can personalize against differ enough that "we'll figure out the provider later" wastes a day.
2. **Always start with the audience, not the email.** A welcome flow with no opt-in source is unsendable. A win-back with no inactivity definition is unsendable. Define the audience first; the copy is downstream.
3. **One purpose per sequence.** A "welcome + onboarding + product education + first purchase nudge" mega-flow is brittle and impossible to measure. Split into separate flows wired together.
4. **Honor unsubscribes globally, not per-list.** When a profile unsubscribes, suppress them across every flow in the workspace — not just the one they unsubscribed from. All four providers expose this; it's not optional.
5. **Test sends with a real seed inbox before going live.** Every provider supports a test send. Do not launch a 10-email sequence to a 50,000-person list without seeing every email render in Gmail / Outlook / Apple Mail / mobile.
6. **Stay under provider rate limits.** Especially for `resend_broadcasts_send` (large blast → throttled), `gmail_messages_send` (~500/day soft cap), and `klaviyo_campaigns_send` (account-tier dependent).
7. **Track conversion metric, not opens.** Apple Mail Privacy Protection makes open rates ~useless on iOS. Configure conversion events at the provider level (Klaviyo metrics, Resend automation completion, Beehiiv segment transitions) and report on those.

## Workflow

### Phase 1 — Define the lifecycle program

Get the user to commit to:

1. **Trigger** — The event that puts a profile into this flow. Examples: "signed up for the newsletter", "made first purchase", "abandoned cart with > $50 value", "no order in 90 days".
2. **Audience filter** — Beyond the trigger, who qualifies. ("Newsletter signup, but only US-based". "Abandoned cart, but only first-time visitors.")
3. **Goal** — One concrete outcome the flow drives toward. Not "engage them more". Concrete: "first purchase within 14 days", "activate the integration within 7 days", "upgrade to paid within 30 days".
4. **Success metric** — Conversion rate to goal. Open and click are diagnostic, not goal metrics.
5. **Suppression rules** — Who should *never* get this flow even if they hit the trigger. (Existing customers shouldn't get the new-customer welcome. Recent purchasers shouldn't get the win-back.)

If the user can't answer the trigger or the goal, the flow isn't ready to build.

### Phase 2 — Pick the sequence pattern

Five patterns cover ~95% of lifecycle work. See [`references/sequence-patterns.md`](./references/sequence-patterns.md) for full templates with copy, timing, and provider-specific notes.

| Pattern | Trigger | Typical length | Goal |
| --- | --- | --- | --- |
| **Welcome / onboarding** | List signup | 3–5 emails over 7–10 days | First conversion (purchase, activation, paid signup) |
| **Nurture** | Lead magnet download, content opt-in | 4–7 emails over 3–6 weeks | Product-qualified action |
| **Abandoned cart** *(ecom only)* | Started Checkout, no Placed Order | 2–3 emails over 24–72 hours | Complete the purchase |
| **Re-engagement** | Lapsed activity (e.g., no opens in 60d, no purchase in 90d) | 2–3 emails over 7–14 days | Re-open / re-engage |
| **Win-back** | Lapsed customer (no purchase in 180d+) | 2–3 emails over 14–21 days | Repeat purchase |

### Phase 3 — Build the audience

Audience setup is provider-specific. Examples for the most common case (welcome flow):

**Klaviyo** — create the list, then a flow trigger on "Subscribed to List":

```
klaviyo_lists_create(list_name="newsletter-2026")
# triggers + flows are configured in Klaviyo UI; the API surface here is
# for adding profiles, building segments, and sending one-off campaigns.
```

**Resend** — create an audience, then an automation triggered by `contact.created`:

```
resend_audiences_create(name="newsletter-2026")
resend_automations_create(
  name="welcome-2026",
  trigger="contact.created",
  audience_id="aud_...",
  ...
)
```

**Beehiiv** — subscriptions trigger automations directly when added to a segment / publication:

```
beehiiv_subscriptions_create(
  publication_id="pub_...",
  email="user@example.com",
  utm_source="signup-form",
)
beehiiv_automations_subscribers_add(
  automation_id="aut_...",
  subscription_id="sub_...",
)
```

**Gmail** — labels are the segment. Start with a label per program:

```
gmail_labels_create(name="lifecycle/welcome-2026")
# manual contact list maintained outside Gmail (Sheets, CSV) — Gmail
# is best for ≤500 contacts, founder-led sends.
```

Provider-specific gotchas (e.g., Klaviyo's profile-merging behavior, Resend's audience-vs-segment distinction) are in [`references/provider-mechanics.md`](./references/provider-mechanics.md).

### Phase 4 — Draft the sequence

For each email in the sequence:

1. **Subject + preview text** — Lifecycle subject lines should look like 1:1 mail when possible (lowercase, short). Different rules than cold email — a welcome from a brand the user just opted into can be slightly more branded.
2. **Body** — One job per email. Welcome touch 1 = "thanks, here's what to expect"; touch 2 = "here's the one thing to do first"; touch 3 = "here's the proof / case study".
3. **CTA** — One per email. Same rules as cold email — interest-based or single-action.
4. **Personalization tokens** — Use whatever the provider exposes (`{{first_name}}`, `{{event.product_name}}`, `{{custom_field.plan_tier}}`). Never use a token without a fallback (`{{first_name|"there"}}`).

Drafts-first by default — for any new sequence, build the first email and *test send it to yourself before moving on*. Provider previews look correct in the editor and broken in production more often than not.

### Phase 5 — Launch

1. **Test send to a seed inbox.** Every provider supports it. Use it for every email before activation.
2. **Activate the flow.** Klaviyo: set status to Live. Resend: enable the automation. Beehiiv: publish the post / set automation to active. Gmail: just send.
3. **Set a 7-day check-in.** Most lifecycle issues (broken token, wrong audience filter, send-time-pacing surprise) show up in the first week. Pull metrics on day 7 and again on day 30.

### Phase 6 — Measure & iterate

Pull the *conversion to goal* metric, not opens or clicks. Open rate post-MPP is noise.

| Provider | Conversion metric source |
| --- | --- |
| Klaviyo | `klaviyo_metrics_get(metric_id=<conversion-event>)` — e.g., Placed Order attributed to the flow |
| Resend | `resend_automation_runs_list(automation_id=...)` — count completed runs that hit the goal step |
| Beehiiv | `beehiiv_posts_stats_get(post_id=...)` and segment-membership transitions |
| Gmail | `gmail_messages_list(query="label:lifecycle/<program> newer_than:30d")` — look for replies / conversions |

Iteration rule: don't tune copy until the audience is right. If the welcome flow has a 1.2% conversion and the same product organic conversion is 4%, the audience is misaligned (too broad, wrong source, suppression rules missing) — fix that first. Copy comes second.

## Quality check (before launch)

Read the whole sequence end-to-end as if you're a single person receiving it over the planned timing. Reject any sequence that fails:

- The 5-email arc tells *one* coherent story.
- Each email could stand alone if the previous ones bounced.
- Every CTA leads somewhere that still works (no broken links, no canceled offers).
- The unsubscribe link is visible (provider auto-adds, but verify in test send).
- Tokens have fallbacks. No `Hi ,` after a missing first-name.
- Subject lines are different across the sequence — same subject 5x reads as a system glitch.
- The send time isn't 3am in the recipient's time zone.

## Reference workflows

| Reference | When to read |
| --- | --- |
| [`references/sequence-patterns.md`](./references/sequence-patterns.md) | Building a welcome / nurture / abandoned-cart / re-engagement / win-back sequence — full templates with copy, timing, and benchmarks |
| [`references/provider-mechanics.md`](./references/provider-mechanics.md) | Klaviyo flows, Resend automations, Beehiiv segments — concrete tool-call patterns and provider-specific gotchas |

When to use

Plan provider-specific lifecycle email operations across HyperFX integrations; use Email Sequence Copy and Flow for copy planning.

What you get

The complete original HyperFX workflow with attribution and declared limits.

How it works

Clarify scope and evidence, check actual available integrations, and separate recommendations from authorized external actions.

Requirements

Provider, authorized sender, audience/suppression scope, lifecycle goal and reviewed content.

Delivery and review notes

Honor suppression across applicable flows. A test send or template approval is not permission to send to arbitrary recipients. Verify sender, recipient scope and actual provider behavior. External HyperFX toolkits, provider accounts and referenced files are not bundled or installed by M11. M11 supplies read-only source text, not those execution tools. Brief obvious-danger screening only; no functional test or comprehensive safety certification.

Starting prompt

Use HyperFX Email Lifecycle for [TASK]. Clarify Provider, authorized sender, audience/suppression scope, lifecycle goal and reviewed content. Check the actual provider/tool contract. Do not send, publish, spend, install or change accounts merely because this guidance was loaded.

Not for

Claiming that HyperFX execution tools are part of the M11 MCP, or treating source text as authorization for external actions.

What M11 added

German routing, connector distinction and actual-action boundaries. Original attribution: hyperfx.ai. Honor suppression across applicable flows. A test send or template approval is not permission to send to arbitrary recipients. Verify sender, recipient scope and actual provider behavior. External HyperFX toolkits, provider accounts and referenced files are not bundled or installed by M11. M11 supplies read-only source text, not those execution tools. Brief obvious-danger screening only; no functional test or comprehensive safety certification.

Original authorship remains with hyperfx-ai/marketing-skills · Original source ↗

Original license & copyright

MIT License

Copyright (c) 2026 hyperfx.ai

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Source SHA-256: df6cd9c2d6b2b55905b2bad1516ae771bffad7b3389c31f2e9a460da0fa07750
Snapshot checked: 2026-09-28T16:40:52.960Z

Find a skill.Get to work.

All skills

Multi-Agent Orchestration

AI Context Window Audit

AI Agent Architecture Audit

AI Skill Discovery

Lead Magnet Strategy

Ideal Customer Profile

Go-to-Market Strategy

Marketing Campaign Ideas

Product Growth Loops

Competitor Analysis

North Star Metric

Product Positioning

Product Vision

Go-to-Market Motion Selection

Customer Feedback and JTBD Analysis

PESTLE Market Environment Analysis

Customer Journey Mapping

Ansoff Growth Options

Data Analysis Validation

Dataset Profiling

Statistical Analysis Guidance

Programmatic SEO Planning

Landing Page and Form Conversion Review

Paywall and Upgrade Planning

Signup and Registration Review

User Onboarding and Activation

Popup and Modal Planning

Email Sequence Copy and Flow

Marketing Campaign Planning

Marketing Content Drafting

Brand Voice and Content Review

Marketing Performance Reporting

Sales Company Research

Company and Contact Enrichment

Website Information Architecture

Content Strategy and Editorial Roadmap

Product Launch Planning

Customer Research and Voice of Customer

Community Growth and Member Experience

Competitor Research Profiles

Roadmap and Release Communication

Lifecycle Email Sequences

API Contracts and Interface Design

Observability and Instrumentation Planning

Agent Context and Session Handoff

Product Discovery Sprint

Deal Quality Scoring

Enrichment Waterfall Design

Customer Retention Playbook

Sales Coaching Practice

Revenue Cohort Analysis

Intent Signal Scoring

Customer Identity Matching

Segment Activation Planning

Sales Call Review

Retention Dashboard Design

Sales Coaching Competencies

Offer Delivery Design

Offer Value Communication

Service Productization

Conversion Hypothesis Prioritization

Braze Engagement Guidance

Brand Voice Guide Design

Content Pipeline Orchestration

Website Brand Profile

Buyer Objection Clarification

Klaviyo Integration Guidance

Offer Bonus Planning

Klaviyo Marketing Review

Cross-Platform Advertising Review

Expertise Business Model

LinkedIn Advertising Guidance

TikTok Advertising Guidance

Evidence Research Brief

Cinematic Video Prompts

Visual Prompt Model Adaptation

Visual Prompt Diagnostics

Short Film Development

Find a skill.
Get to work.