Brand scoping

Outputs live under ~/notes/Klaviyo/<brand>/<subfolder>/, where <brand> is resolved at run time from the connected Klaviyo account's organizationName attribute (via mcp__claude_ai_Klaviyo__klaviyo_get_account_details). For ExampleBrand, this resolves to ExampleBrand. If multiple brands are connected, ask Will which brand the current run is for.

/klaviyo-flow

The Klaviyo MCP cannot create flows directly — this skill outputs a deployable spec (every email + condition + delay) that Will pastes into Klaviyo's flow builder OR feeds to a Klaviyo API deploy script. Either way, the design + copy work is fully drafted.

Flow

1. Parse intent — flow type (welcome / abandoned-cart / browse-abandon / post-purchase / win-back / sunset / vip / birthday / back-in-stock / price-drop), brand, any specific constraints (length, tone, offer mechanics).
2. Load brand context — ~/notes/[brand-slug]/brand-identity/ for voice + products. Required.
3. Check existing flow state — mcp__claude_ai_Klaviyo__klaviyo_get_flows. If a flow of this type already exists, read its report via klaviyo_get_flow_report and use the performance baseline to inform recommendations (rebuild from scratch vs patch).
4. Apply the canonical spec for the flow type — see ## Flow templates below. Each template defines: trigger condition, exit criteria, sequence length, delay logic per step, content theme per step.
5. Draft each email in the sequence — subject line + preheader + body + CTA per step, in brand voice. Use the copy framework from /klaviyo-campaign.
6. Write the spec — save the full sequence to ~/notes/Klaviyo/<brand>/flows/[flow-type]-[YYYY-MM-DD]/.
7. Print summary + deploy instructions — show Will the structure, link to the spec, list the Klaviyo manual setup steps (since MCP can't create flows).

Flow templates

Welcome — 4 emails, triggered on list signup

Abandoned cart — 3 emails, triggered on Added to Cart (NOT just Checkout Started)

Note: Default Klaviyo abandoned cart triggers on Checkout Started only. The above triggers on Added to Cart to catch the 70%+ of intent that never reaches checkout. This is the single highest-impact flow gap most brands have.

Browse abandonment — 2 emails, triggered on Viewed Product (no Add to Cart, no Purchase in 24h)

Post-purchase — 5 emails, triggered on Placed Order

Win-back — 3 emails, triggered on Placed Order 90+ days ago AND no Placed Order in 60d

Sunset — 1 email, triggered on no email engagement in 90 days

VIP — 2-3 emails per launch, triggered on segment entry (high-LTV)

• Pre-launch access (24-48h early)
• Exclusive bundle/discount
• Thank-you note from founder

Birthday — 1 email, +1 day before birthday

• Personal note + discount valid through birthday week

Back-in-stock — 1 email, triggered on Restock Notify event + product in stock

• Immediate; subject line names the product

Price drop — 1 email, triggered when product viewed in last 30d AND price drops

• Immediate; show old/new price

Output folder structure

~/notes/Klaviyo/<brand>/flows/[flow-type]-[YYYY-MM-DD]/
  spec.md           # full flow spec — trigger, conditions, delays, branches
  email-1.md        # email 1 — subject, preheader, body, CTA
  email-2.md
  ...
  deploy.md         # step-by-step Klaviyo manual setup (since MCP can't create flows)

Deploy instructions in deploy.md

Always include:

1. Klaviyo path: Flows → Create Flow → From scratch
2. Trigger setup with exact conditions
3. Exit criteria
4. Each email step: template assignment, delay value, conditional split if any
5. A/B test setup recommendation if applicable
6. UTM parameter convention for tracking

What this skill does NOT do

• Does not create the flow in Klaviyo (MCP limitation — no create_flow available). Will deploys manually OR via Klaviyo's REST API directly.
• Does not write SMS variants — bundle into the email spec or extend later.
• Does not audit existing flows — that's a one-shot review, not a skill.

Failure modes

• Unknown flow type → list the supported types, ask Will to pick.
• Brand voice doc missing → ask before drafting copy.
• Existing flow of same type has good performance → surface the report, ask whether to patch the spec for incremental fixes vs replace from scratch.