cm-autopilot
Easy-to-use conversational CLI (Claude Code style) for non-technical users to spawn parallel AI tasks supervised by a visual web…
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isn''t converting", "conversion rate", "A/B test", "why visitors leave", or "objection handling". Covers funnel mapping, persuasion assets, and
Claude Code
$ npx -y skills add tody-agent/codymaster --skill cm-cro-methodology --agent claude-code
Codex
$ npx skills add tody-agent/codymaster --skill cm-cro-methodology -a codex -y
Cursor
$ npx skills add tody-agent/codymaster --skill cm-cro-methodology -a cursor -y
Gemini CLI
$ npx skills add tody-agent/codymaster --skill cm-cro-methodology -a gemini-cli -y
GitHub Copilot
$ npx skills add tody-agent/codymaster --skill cm-cro-methodology -a github-copilot -y
OpenCode
$ npx skills add tody-agent/codymaster --skill cm-cro-methodology -a opencode -y
Windsurf
$ npx skills add tody-agent/codymaster --skill cm-cro-methodology -a windsurf -y
name: cm-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 isn''t converting", "conversion rate", "A/B test", "why visitors leave", or "objection handling". 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.1.1"
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.
**Don't guess -- discover.** The methodology rejects "best practices" and "magic buttons" in favor of evidence-based optimization. Most websites underperform not because of bad design, but because no one has systematically researched why visitors leave without converting.
**The foundation:** Every visitor who doesn't convert has a reason. Your job is to discover those reasons through research, then systematically eliminate them with evidence and proof. This customer-centric approach consistently outperforms intuition, competitor copying, and "expert" opinions.
**Goal: 10/10.** When reviewing or creating landing pages, funnels, or conversion flows, rate them 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.
**Core concept:** A systematic 9-step process for optimizing conversion rates, moving from defining success metrics through research, experimentation, and scaling wins across the business.
**Why it works:** Random optimization efforts fail because they skip the critical research steps. The CRE process forces you to understand visitors before changing anything, ensuring changes are based on evidence rather than opinion.
**Key insights:**
**Product applications:**
| Context | CRO Process Step | Example | |---------|-----------------|---------| | **Landing page audit** | Steps 1-3: Define goals, map funnel, research visitors | Identify that 70% of traffic bounces because value prop is unclear | | **Checkout optimization** | Step 2: Map funnel for blocked arteries | Discover shipping cost shock causes 40% cart abandonment | | **New feature launch** | Steps 6-8: Strategize, design, experiment | A/B test two positioning approaches before full rollout | | **Email sequence** | Step 9: Scale wins | Apply winning objection-handling copy from landing page to drip emails | | **Competitor response** | Step 4: Market intelligence | Transfer proven strategies from adjacent industries |
**Copy patterns:**
**Ethical boundary:** Never manipulate test results or cherry-pick data. Report all tests, including failures, and wait for genuine statistical significance.
See: [testing-methodology.md](references/testing-methodology.md) for detailed ICE scoring, A/B vs. multivariate guidance, and statistical rigor.
**Core concept:** Visitors don't convert for specific, discoverable reasons. Research methods -- exit surveys, chat logs, support tickets, sales calls, reviews -- reveal the "voice of the customer" and their real objections.
**Why it works:** Companies guess why visitors leave, but guesses are almost always wrong. Direct research consistently uncovers objections that teams never anticipated, and the language customers use is more persuasive than any copywriter's invention.
**Key insights:**
**Product applications:**
| Context | Research Method | Example | |---------|---------------|---------| | **Exit intent** | On-site survey (Hotjar, Qualaroo) | "What's preventing you from signing up today?" | | **Post-purchase** | Email survey within 7 days | "What almost stopped you from buying?" | | **Objection mining** | Support ticket analysis | Search for "but",
"I can't write code. But in 6 months, I shipped 12 real products using AI. CodyMaster is everything I learned — so you don't have to repeat my mistakes." — Tody Le, Head of Product, Creator of CodyMaster 50+ skills. One install.
Easy-to-use conversational CLI (Claude Code style) for non-technical users to spawn parallel AI tasks supervised by a visual web…
Strategic analysis gate for existing products — multi-dimensional evaluation (tech, product, design, business) using Design…
Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native…
Code hygiene gate — detect and eliminate dead code, duplicates, naming mess, and code smells. TRIZ-powered. Run after features,…
Full review lifecycle — request reviews, handle feedback with technical rigor, and complete branch integration. Use when…
Unified code intelligence — routes to Skeleton Index, CodeGraph, Architecture Diagram, or Smart Context Builder based on task…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.