Checkout Friction Audit
Skill Card
- Category: Conversion
- Core problem: Which checkout steps are leaking intent and killing purchase completion?
- Best for: Conversion rate recovery projects
- Expected input: Checkout flow notes, abandonment signals, user complaints, policy constraints
- Expected output: Friction map with severity, likely cause, and fix priority
- Creatop handoff: Push fixes into sprint board and rerun after implementation
Browser-first guidance
If the checkout flow is accessible by URL or staging page, prefer OpenClaw managed browser for direct observation before producing recommendations.
Recommended order:
- Use any funnel notes, complaints, or screenshots the user already has.
- If live checkout pages are available, inspect them in OpenClaw managed browser.
- Use Browser Relay only when the user explicitly wants to inspect their current Chrome session.
Workflow
- Clarify where the drop appears to happen.
- cart?
- shipping step?
- payment step?
- mobile-specific issue?
- Map checkout path and identify complaint-linked touchpoints.
- Score friction by impact on completion and fix complexity.
- Separate UX friction from trust/compliance friction.
- Output top quick wins and structural fixes.
Output format
Return in this order:
- Executive summary (max 5 lines)
- Priority actions (P0/P1/P2)
- Evidence table (signal, confidence, risk)
- 7-day execution plan
Quality and safety rules
- Tie each recommendation to observed evidence, not guesswork.
- Prioritize reversible low-risk fixes first.
- Avoid recommendations that violate platform/payment policies.
- If the observed flow is partial, state that clearly.
License
Copyright (c) 2026 Razestar.
This skill is provided under CC BY-NC-SA 4.0 for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license.
Commercial use requires a separate paid commercial license from Razestar. No trademark rights are granted.