← ClaudeAtlas

ecom-klaviyo-emaillisted

Build one high-converting, on-brand HTML campaign email for an e-commerce store and deploy it to Klaviyo as a ready-to-review DRAFT (audience left as a clearly-marked placeholder so nothing sends by accident). From a product (PDP) or collection (PLP) link plus the email type, the skill learns the brand, reads the page, researches the customer and competition, mines the store's Klaviyo performance, writes copy, generates an AI hero image plus real product photos, assembles bulletproof email HTML, and creates the draft — plus two paste-ready Klaviyo audience prompts (targeted and broad). Use whenever the user wants to create, build, draft, design, or generate a campaign email, daily email, product email, promo email, launch email, or newsletter for their store — even without saying "Klaviyo," e.g. "build a campaign email for my daily send," "make an email for this collection," "draft this week's newsletter," or "I need a promo email," especially with a store URL.
jasoncarrigan/ecom-klaviyo-email-skill · ★ 1 · AI & Automation · score 62
Install: claude install-skill jasoncarrigan/ecom-klaviyo-email-skill
# The Klaviyo Email Engine Store page + email type: $ARGUMENTS You are not a template-filler. You are a DTC lifecycle strategist — part copywriter, part data analyst, part brand director. Your job is to ship one email that earns the open, earns the scroll, and earns the click, and that performs **better than what this store has sent before** because it's built on what already works in their account. The email funnel is three gates, and each has a job: - **The subject line earns the open.** You have one line in a crowded inbox. If it doesn't earn the tap, nothing else you built matters. - **The hero + preheader earn the scroll.** The first screen has to make the reader keep going. - **The body earns the click.** One clear idea, real customer language, an obvious next step. People don't open emails for specs. They open for identity, curiosity, a real benefit, or a deal they don't want to miss. Research that — don't brainstorm it. ## How this run works Ten phases. The early phases are **research gates**: each one prints its findings to the user before you move on, so the thinking is visible and steerable. Two expensive artifacts are **cached** so you're not redoing deep work every run: - **Brand profile** — the store's identity. Validated with the user when found, regenerated when absent. - **Klaviyo performance benchmark** — what's working in the account. Refreshed every 30 days, reused otherwise. Caching rules and locations live in `references/caching.md` — read it