cro-methodology
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", "split testing", or "conversion funnel". 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.
What this skill does
# 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.** 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.
## Scoring
**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.
## The CRO Frameworks
### 1. The CRO Process
**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:**
- Define success metrics aligned with business KPIs before touching any page
- Map the entire conversion funnel to find "blocked arteries" (high-traffic underperforming paths) and "missing links" (absent funnel stages)
- Understand visitors in three dimensions: who they are (types and intentions), what blocks them (UX problems), and what stops them (objections)
- Gather market intelligence from competitors, reviews, and other industries
- Prioritize ideas using ICE scoring (Impact, Confidence, Ease) before testing
- Create bold experimental designs based on research, not "meek tweaks"
- Run experiments with proper statistical rigor (95% confidence minimum, full business cycles)
- Scale wins across landing pages, ad copy, email sequences, and offline materials
**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:**
- "What's preventing you from [action] today?" (exit survey question to discover objections)
- "Here's what [X] customers found..." (counter-objection with social proof)
- Document hypothesis: "If we [change X], then [metric Y] will improve because [reason from research]"
- Always calculate required sample size BEFORE starting any test
**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.
### 2. Customer Research & Objections
**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:**
- Primary sources (exit surveys, live chat logs, support tickets, sales call recordings) give you direct visitor language
- Secondary sources (reviews, social media, competitor analysis) reveal industry-wide objections
- Objections fall into two categories: explicit ("too expensive") and implicit ("I'm not sure I'll follow through")
- The "Big 5" universal objections are Trust, Price, Fit, Timing, and Effort
- Post-purchase surveys ("What almost stopped you from buying?") reveal the objections that matter most
- Non-converter surveys should ask ONE question for maximum response rate
- Quantitative research (analytics, heatmaps) shows WHERE problems are; qualitative research (surveys, interviews) shows WHY
**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", "however", "worried about" patterns |
| **Voice of customer** | Sales call recordings | Capture exact language customers use to describe problems |
| **Competitive gaps** | Review mining (yours and competitors') | Negative reviews = unaddressed objections |
**Copy patterns:**
- Use exact customer language in headlines and body copy (more persuasive than polished marketing copy)
- "What's the one thing we could change to make you [action]?"
- "How would you describe [product] to a friend?" (reveals positioning in customer terms)
- Ask open-ended questions for discovery; save multiple choice for validation
**Ethical boundary:** Respect customer privacy in research. Anonymize data, get consent for recordings, and don't survey so aggressively that you degrade the user experience.
See: [RESEARCH.md](references/RESEARCH.md) for tools, survey questions, and data analysis methods.
### 3. Persuasion Assets
**Core concept:** Every company has overlooked proof elements -- testimonials not displayed, awards not mentioned, statistics not highlighted, guarantees not prominent, team credentials hidden. These are "persuasion assets" that must be inventoried, acquired, and displayed.
**Why it works:** Visitors make decisions based on evidence and proof, not claims. A bold claim without proof is just noise. A modest claim with overwhelming proof is irresistible. Most companies sit on goldmines of proof they never use.
**Key insights:**
- Audit five categories: Credentials & Authority, Social Proof, Risk Reversal, Data & Specificity, Process & Methodology
- Create a "wish list" for missing assets and actively acquire them (request testimonials, apply for awards, compile statistics)
- The "proof sandwich" structure: Claim (bold promise) then Proof (evidence) then Reinforcement (secondary proof)
- Hierarchy of proof from strongest to weakest: specific results with context, named testimonials with photos, case studies, statistics, logos/badges, generic testimonials
- Place proof at points of friction, not hidden in FAQs
- Specific numbers beat round numbers ("47,832 customers" beats "About 50,000")
**Product applications:**
| Context | Persuasion Asset | Example |
|---------|-----------------|---------|
| **Landing page header** | Logo bar + rating | "Trusted by 10,000+ companies" with 5 recognizable logos |
| **Pricing page** | Risk reversal | "30-day money-back guarantee, no questions asked" |
| **Product page** | Specific testimonial | Photo + name + company + "Increased conversion Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".