mcpField
C
checkout-conversion-review

checkout-conversion-review

github.com/sylphxaiMarketing & growth152 installsUpdated today
Repository

About checkout-conversion-review

A checkout review skill for product and payment teams that maps friction from offer exposure through payment and entitlement delivery. It creates a prioritized plan with measurement, safeguards, and rollback criteria.

Key features

  1. 01Map checkout stages and states
  2. 02Separate trust, speed, and reliability issues
  3. 03Review payment recovery and entitlements
  4. 04Set metrics and rollback criteria

Use cases

  1. 01Diagnose checkout conversion bottlenecks
  2. 02Verify entitlement after payment
  3. 03Review pricing and renewal clarity
  4. 04Plan and measure payment improvements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill checkout-conversion-review

After installing, type/checkout-conversion-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/checkout-conversion-systems.md

Details

From the project README

Checkout Conversion Review

Use this skill to improve checkout revenue without adding dark patterns, payment fragility, or support debt.

Workflow

  1. Identify the product type, buyer intent, price model, payment channels, and entitlement granted after purchase.
  2. Read references/checkout-conversion-systems.md.
  3. Map the funnel from pricing/offer exposure to payment confirmation, entitlement grant, receipt, and support trace.
  4. Separate trust, clarity, speed, payment reliability, recovery, and measurement issues.
  5. Produce a prioritized conversion plan with guardrails, instrumentation, and rollback criteria.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not hide price, renewal, tax, cancellation, or refund consequences.
  • Do not optimize click-through at the cost of refund rate, chargeback risk, or support load.
  • Treat payment success and entitlement grant as separate states; both need evidence.

Output format

Checkout context:
Primary conversion constraint:

Funnel map:
- <step> -> user intent, system state, failure/recovery

Findings:
- P0 <issue> -> fix, metric, risk
- P1 <issue> -> fix, metric, risk

Instrumentation:
- <event> with key properties

Experiment/rollout:
- hypothesis, segment, success metric, guardrail metric, stop rule

Comments

Markdown supported