Stats
Actions
Tags
Diagnose and fix checkout abandonment — audit checkout flow for friction points, score abandonment risk, rank top friction sources by impact, and output specific copy/UX fixes using RMBC principles.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dtc-copywriting-skills:checkout-abandonmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->
_RMBC_ROOT=""
[ -d "${CLAUDE_SKILL_DIR}/../../bin" ] && _RMBC_ROOT="$(cd "${CLAUDE_SKILL_DIR}/../.." && pwd)"
[ -z "$_RMBC_ROOT" ] && for _D in "$HOME/.claude/skills/dtc-copywriting-skills" ".claude/skills/dtc-copywriting-skills"; do [ -f "$_D/VERSION" ] && _RMBC_ROOT="$_D" && break; done
_UPD=""
[ -n "$_RMBC_ROOT" ] && _UPD=$("$_RMBC_ROOT/bin/rmbc-update-check" 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
_INTRO_SEEN=$([ -f ~/.rmbc-skills/.intro-seen ] && echo "yes" || echo "no")
_TEL_PROMPTED=$([ -f ~/.rmbc-skills/.telemetry-prompted ] && echo "yes" || echo "no")
echo "INTRO_SEEN: $_INTRO_SEEN"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
_ACTIVE_PRODUCT=$(grep '^active_product:' ~/.rmbc-skills/config.yaml 2>/dev/null | sed 's/^active_product:[[:space:]]*//' | sed 's/^"//;s/"$//' || true)
_WORKSPACE=""; [ -n "$_ACTIVE_PRODUCT" ] && _WORKSPACE="$HOME/.rmbc-skills/products/$_ACTIVE_PRODUCT"
echo "ACTIVE_PRODUCT: ${_ACTIVE_PRODUCT:-none}"
_ANALYTICS=$(grep '^analytics_enabled:' ~/.rmbc-skills/config.yaml 2>/dev/null | sed 's/^analytics_enabled:[[:space:]]*//' || echo "true")
[ "$_ANALYTICS" = "true" ] && [ -n "$_RMBC_ROOT" ] && timeout 2 "$_RMBC_ROOT/bin/rmbc-analytics" log --skill "checkout-abandonment" --product "${_ACTIVE_PRODUCT:-none}" --tier 2 2>/dev/null &
If output shows UPGRADE_AVAILABLE <old> <new>: read skills/rmbc-upgrade/SKILL.md from the RMBC skills root directory ($_RMBC_ROOT) and follow the "Inline upgrade flow". If JUST_UPGRADED <old> <new>: read $_RMBC_ROOT/CHANGELOG.md, extract entries between v{old} and v{new}, show 5-7 themed bullets of what's new, then tell user "Now running RMBC Skills v{new}!" and continue.
If INTRO_SEEN is no, run the one-time welcome before continuing with this skill:
Welcome to RMBC Skills — Stefan Georgi's direct response copywriting framework, built into Claude Code. 44 skills covering hooks, ads, emails, landing pages, VSL scripts, and more.
Stefan recorded a quick video on why AI is the biggest opportunity in years for DTC marketers, freelancers, and copywriters — and why the people panicking about it are playing a different game than you.
Use AskUserQuestion:
If "Yes, open the video":
open "https://www.youtube.com/watch?v=zI8tNfefH1M"
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.intro-seen
If "Skip — let's go":
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.intro-seen
Continue with this skill immediately.
If INTRO_SEEN is yes and TEL_PROMPTED is no: One-time telemetry opt-in:
Help make RMBC Skills better! Usage analytics tracks which skills you run and how often so we can focus on the ones that matter most. Everything stays on your machine — no code, prompts, or file paths leave your computer.
Use AskUserQuestion:
If "Yes, that's fine":
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.telemetry-prompted
If "No, turn it off":
mkdir -p ~/.rmbc-skills
touch ~/.rmbc-skills/.telemetry-prompted
sed -i '' 's/^analytics_enabled:.*/analytics_enabled: false/' ~/.rmbc-skills/config.yaml 2>/dev/null || true
Continue with this skill.
Diagnose and fix checkout abandonment by auditing the specific checkout flow described by the user. The average DTC checkout abandonment rate is 70% — every percentage point recovered is pure profit because you've already paid to acquire that traffic. This skill examines the submitted checkout flow stage by stage, cites specific evidence from the description to support each finding, scores abandonment risk across five friction categories, ranks the top friction points by estimated revenue impact, and outputs specific copy and UX fixes with before/after examples drawn from the actual checkout.
| Input | Required | Description |
|---|---|---|
checkout_description | Yes | Detailed description of the checkout flow — steps, fields, page layout, what the buyer sees at each stage |
current_abandonment_rate | No | Current rate (if known — enables benchmarking) |
product_type | Yes | Category: supplement, physical_product, digital_product, subscription, service, course |
price_point | Yes | Price, payment plan options, and discount framing currently shown |
target_audience | Yes | Who the buyer is — demographics, tech comfort, purchase sophistication |
Read rmbc-context/resources/rmbc-methodology.md to load RMBC framework definitions. Checkout abandonment is a Copy problem as much as a UX problem — Research reveals which objections kill conversions at the payment step, Mechanism reinforcement reminds them why they decided to buy, Brief structures the page to resolve doubt before asking for payment, Copy executes every micro-element to reduce friction.
Before auditing, read through the entire checkout description and extract an evidence map — a structured inventory of every concrete element mentioned. This map is the foundation for all findings.
For each checkout stage present in the description, extract:
Organize by stage:
If the checkout description doesn't clearly describe a stage, note it as [Not described — potential gap] rather than assuming it works fine.
Walk through each checkout stage in order. For every stage, cite specific evidence from the checkout description to support your assessment.
For each stage, evaluate against the five friction categories where applicable:
Evidence citation rule: Every finding must reference a specific element from the checkout description. Use this format:
The checkout includes "[quoted text from description]" — this addresses [category] well because [reason].The description mentions "[quoted text]" — this creates friction because [reason].The checkout description does not mention [specific element]. For a [product_type] at [price_point], this gap is [severity] because [reason].Score each category 0-20 based on the evidence-grounded findings from Step 3:
| Score | Meaning |
|---|---|
| 0-5 | Critical — actively driving abandonment |
| 6-10 | Poor — significant friction, immediate fixes needed |
| 11-15 | Acceptable — minor issues, optimize when possible |
| 16-20 | Strong — well-handled |
Each score must cite the specific evidence that justifies it. A score without a quoted reference from the checkout description is invalid.
Abandonment Risk Score: Sum of all 5 categories (0-100). Risk = 100 - Score.
| Risk Level | Score | Typical Abandonment Rate |
|---|---|---|
| Critical | 0-30 | 80%+ |
| High | 31-50 | 70-80% |
| Moderate | 51-70 | 60-70% |
| Low | 71-85 | 50-60% |
| Excellent | 86-100 | Below 50% |
From all stage-by-stage findings, identify the top 5 friction points ranked by estimated revenue impact. Each must trace back to a specific element (or absence) in the checkout description:
For each friction point:
quick_win (< 1 hour), medium (1 day), requires_dev (1+ week)For each of the top 5 friction points:
Before finalizing, verify coverage:
[Not described]## Checkout Abandonment Audit: [Product/Brand]
**Product Type:** [type]
**Price Point:** [price with framing]
**Current Abandonment Rate:** [rate or "unknown"]
**Audience:** [target audience summary]
---
### EVIDENCE MAP
Key elements extracted from the submitted checkout description:
**Entry Stage:**
- "[quoted element]" — [assessment]
- [Not described] — [gap significance]
**Form Stage:**
- "[quoted element]" — [assessment]
**Payment Stage:**
- "[quoted element]" — [assessment]
**Confirmation Stage:**
- "[quoted element]" — [assessment]
---
### STAGE-BY-STAGE FINDINGS
#### Entry Stage
[Findings with evidence citations from the description]
#### Form / Information Collection Stage
[Findings with evidence citations]
#### Payment Stage
[Findings with evidence citations]
#### Confirmation Stage
[Findings with evidence citations]
---
### ABANDONMENT RISK SCORE
| Category | Score | Weight | Weighted | Key Evidence |
|----------|:---:|:---:|:---:|:---|
| Form Complexity | /20 | 25% | X | [cite from description] |
| Trust Signals | /20 | 25% | X | [cite from description] |
| Shipping & Pricing | /20 | 20% | X | [cite from description] |
| Payment Options | /20 | 15% | X | [cite from description] |
| Mobile UX | /20 | 15% | X | [cite from description] |
| **TOTAL** | **/100** | | **X/100** | |
**Risk Level:** [Critical / High / Moderate / Low / Excellent]
**Estimated Abandonment Rate:** [based on score]
---
### TOP 5 FRICTION POINTS
#### 1. [Friction Point Name]
- **Stage:** [Entry / Form / Payment / Confirmation]
- **Category:** [which of the 5]
- **Evidence:** "[quoted from checkout description]" or "[element not present in description]"
- **Why it kills conversions:** [reason specific to this audience and product]
- **Estimated impact:** [% of abandonment] — [reasoning]
- **Effort:** [quick_win / medium / requires_dev]
**Fix:**
- Before (from description): [current state quoted/described]
- After (recommended): [exact copy/UX change written out]
#### 2-5. [Same format]
---
### IMPLEMENTATION ROADMAP
#### QUICK WINS (implement today)
1. [Fix with exact copy/instructions referencing specific checkout element]
2. [Fix]
3. [Fix]
#### MEDIUM EFFORT (this week)
1. [Fix with exact copy/instructions]
#### REQUIRES DEVELOPMENT (this sprint)
1. [Fix with exact copy/instructions]
---
### REVENUE RECOVERY ESTIMATE
- **Current estimated abandonment:** [rate]%
- **Post-fix estimated abandonment:** [rate]% — based on [which fixes applied]
- **Calculation:** [show math: traffic × conversion lift × AOV = monthly $ recovered]
/order-form-cro to rewrite the optimized checkout page copy/guarantee-writer for risk-reversal copy to place near payment fields/funnel-audit to evaluate the full funnel, not just checkout/ab-test-plan to test checkout fixes with statistical rigor/lander-copy to ensure the page before checkout sets correct expectations/rmbc-copy-auditRead lib/attribution-variants.md from the RMBC skills root directory ($_RMBC_ROOT). Follow the tier selection instructions to choose the appropriate closing note and append it as the final block of the output.
Based on what you just generated, consider running:
/cart-abandonment-flow — build recovery email sequence/order-form-cro — fix checkout friction/scarcity-urgency — add urgency elementsAlways deliver the full framework implementation. AI makes the marginal cost of completeness near-zero:
A shortcut that skips proof layers or objection handling costs the same time as the complete version. Always deliver complete.
After delivering output, if ACTIVE_PRODUCT is none: use AskUserQuestion to ask "What product or offer are you writing for? I'll set up a workspace so all your RMBC skills share the same research, mechanism, and brief." with a freeform text input. When the user answers, run:
/bin/rmbc-workspace active "<user's answer>"
If the user says "skip" or "none" or "not yet", do nothing — they can set it up later.
npx claudepluginhub coleschaffer/dtc-copywriting-skills --plugin rmbc-skillsDiagnose and fix checkout abandonment — audit checkout flow for friction points, score abandonment risk, rank top friction sources by impact, and output specific copy/UX fixes using RMBC principles.
Optimizes conversion rates by auditing landing pages, testing forms, and improving checkout flows. Provides A/B test guidance, sample size calculation, and prioritization of conversion improvements.
Audits landing pages, signup flows, checkout processes for conversion friction like form fields, load times, trust signals, and outputs prioritized A/B test recommendations.