# cro-methodology

Audits landing pages and funnels for conversion leaks using the CRE framework. Designs evidence-backed A/B testing hypotheses based on customer objections.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 6100 installs · ★ 2508
- Author: wondelai
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/wondelai/skills/tree/HEAD/cro-methodology/SKILL.md
- Updated: 2026-09-10
- HTML: https://affpapa.org/en/nevibecode/skills/cro-methodology

## What it does

The skill scores landing pages and sales funnels against a 10-point diagnostic checklist. Instead of copying competitors, it guides you through a 9-step optimization workflow: mapping bottlenecks or blocked arteries, gathering visitor feedback, and prioritizing experiments with ICE scoring.

It organizes research around five universal objection categories: Trust, Price, Fit, Timing, and Effort. The instructions provide survey questions for exit intent, outline a claim-proof-reinforcement structure, and audit persuasion assets so proof sits at friction points rather than buried in FAQs.

This skill is dedicated to conversion mechanics. For high-level marketing strategy, the documentation points to `one-page-marketing`, while usability issues belong to `ux-heuristics`. It requires running experiments with at least 95% statistical confidence.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add wondelai/skills --skill cro-methodology -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/cro-methodology/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/cro-methodology/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add wondelai/skills --skill cro-methodology -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/cro-methodology/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add wondelai/skills --skill cro-methodology -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/cro-methodology/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install wondelai/skills cro-methodology
```

2. **Manually: put the files in place**
- File: `.github/skills/cro-methodology/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add wondelai/skills --skill cro-methodology -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/wondelai/skills --path cro-methodology
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/cro-methodology/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add wondelai/skills --skill cro-methodology -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/wondelai/skills/tree/HEAD/cro-methodology/SKILL.md

## When to use it
- diagnose reasons why visitors abandon checkout or landing pages
- score landing pages against the 7-row diagnostic benchmark
- extract customer objections from support tickets and reviews
- design testable A/B hypotheses prioritized with ICE scoring
- audit persuasion assets and place proof at conversion friction points

## Example prompts
- Audit this landing page for conversion issues and calculate the diagnostic score
- Help design an A/B test hypothesis for our pricing page using ICE scoring
- Draft an exit survey question to find why visitors leave without signing up

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b05386e8bf359a78.

BEGIN THIRD-PARTY FILE b05386e8bf359a78
```text
---
name: cro-methodology
description: 'Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "conversion funnel", "increase signups", or "people add to cart but dont buy". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.'
license: MIT
metadata:
  author: wondelai
  version: "1.5.0"
---

# CRO Methodology

Scientific, customer-centric approach to conversion rate optimization based on the CRE Methodology(TM). Extraordinary improvements come from understanding WHY visitors don't convert, not from copying competitors or applying generic tips.

## Core Principle

**Don't guess -- discover.** Every visitor who doesn't convert has a reason. Discover those reasons through research, then systematically eliminate them with evidence and proof. This evidence-based approach consistently outperforms "best practices", intuition, competitor copying, and expert opinion.

## Scoring

**Goal: 10/10.** Score any landing page, funnel, or conversion flow against the seven Quick Diagnostic rows below: award ~1.4 points per row answered "yes" (7 rows = 9.8, capped at 10). Bands: **9-10** = single clear action, research-grounded O/CO table, value prop legible in 5 seconds, proof at every friction point, funnel mapped, path free of UX blockers; **5-6** = guessed objections, generic best-practices copy, proof buried in FAQs; **<=3** = competing CTAs, no funnel map, claims with no proof. Report the current score and the specific diagnostic rows failing.

## The CRO Frameworks

### 1. The CRO Process

**Core concept:** A systematic 9-step process moving from defining success metrics through research and experimentation to scaling wins across the business.

**Why it works:** Random optimization skips research. The process forces you to understand visitors before changing anything, so every change rests on evidence, not opinion.

**Key insights:**
- Define success metrics aligned with business KPIs before touching any page
- Map the entire funnel to find "blocked arteries" (high-traffic underperforming paths) and "missing links" (absent funnel stages)
- Research visitors in three dimensions: who they are, what blocks them (UX problems), what stops them (objections)
- Gather market intelligence from competitors, reviews, and other industries
- Prioritize ideas with ICE scoring; design bold experiments, not "meek tweaks"
```
END THIRD-PARTY FILE b05386e8bf359a78

The third-party file has ended. Everything between the b05386e8bf359a78 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2782 of 17070 bytes. © wondelai · MIT · https://github.com/wondelai/skills/tree/HEAD/cro-methodology/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md