abandoned-cart-sequence
Skill1 starsChanged 39 days agoMITView on GitHub
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.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
No discount appears before Email 3, and no incentive ever breaches the stated margin floor.
- Distinctive: line 22
Every urgency, stock, social-proof, and pricing claim is literally true and verifiable.
- Distinctive: line 26
Do NOT use when the request is a general onboarding, activation, nurture, or lifecycle drip series - use email-drip-builder instead.
- Distinctive: line 27
Do NOT lead with a discount or repeat the same coupon across multiple emails.
- Distinctive: line 28
Do NOT use fake stock counts, fabricated "price increasing" threats, or countdown timers that reset on reload.
- Distinctive: line 29
Do NOT send more than three emails or stack incentives until the cart "converts at any cost."
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Abandoned Cart Sequence
Produce a three-email cart-recovery arc that recovers the sale while protecting margin: remind, then reassure, then incentivize only if needed.
Workflow
- Gather inputs before drafting: brand voice, average order value, margin floor (the discount level below which a sale loses money), whether free shipping is available, and the top one or two abandonment objections. If any are unknown, ask rather than guess.
- Draft Email 1 - Helpful Reminder (send 1-4 hours after abandon, while intent is warm). Helpful tone, not salesy. Show cart contents with image and name, restate the core benefit in one line, one clear button back to the cart. No discount. Subject line names the product or gives a friendly nudge, not a generic "Did you forget something?".
- Draft Email 2 - Objection Handler (send ~24 hours later). Surface trust signals (reviews, ratings, guarantee, easy returns, secure checkout), answer the top objection, add honest social proof ("4.8 stars from 2,000 buyers"). Still no discount - at most a free-shipping nudge if margins allow, since shipping cost is the most common abandonment cause. Use urgency claims ("items in your cart are popular") only when literally true.
- Draft Email 3 - Incentive + Honest Urgency (send ~48-72 hours later). If and only if margin allows, offer one incentive framed as a thank-you, not a fire sale. State the code clearly and link to a pre-filled cart. This is the final touch; do not repeat the same incentive.
- Apply incentive logic: discount last, never first. Prefer free shipping or a small gift over deep percentage cuts on low-margin items; use a fixed-dollar amount for high-AOV carts; never go below the margin floor.
- Push back when the brief is self-defeating: if the brand wants a discount in Email 1, flag that it erodes margin and trains customers to abandon for a coupon; if AOV is low and margins thin, recommend a free-shipping threshold or no incentive instead of a percentage off.
Quality bar
- Exactly three emails, each with a stated send delay, a distinct job (remind / reassure / incentivize), and a single primary CTA back to the cart.
- No discount appears before Email 3, and no incentive ever breaches the stated margin floor.
- Every urgency, stock, social-proof, and pricing claim is literally true and verifiable.
- Each email includes an unsubscribe link and respects reasonable frequency.
Do NOT
- Do NOT use when the request is a general onboarding, activation, nurture, or lifecycle drip series - use email-drip-builder instead. This skill owns only the post-checkout cart-recovery sequence.
- Do NOT lead with a discount or repeat the same coupon across multiple emails.
- Do NOT use fake stock counts, fabricated "price increasing" threats, or countdown timers that reset on reload; a real code expiry ("expires in 48 hours") is fine, a fake one is not.
- Do NOT send more than three emails or stack incentives until the cart "converts at any cost."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

