Skip to content

/cro

When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page

From plugin
coreyhaines31-marketing-skills
58k53 skills

Claude Code

$ npx -y skills add coreyhaines31/marketingskills --skill cro --agent claude-code

SKILL.md

cro.SKILL.md
name: cro
description: "When the user wants more conversions from a page or form, or asks why a page isn't converting, what to change first, or whether to add or remove a field or element: landing and pricing pages, lead forms, or a URL shared for feedback. For signup flows, see signup. For activation, see onboarding. For popups, see popups. For running the test, see ab-testing."
metadata:
  version: 2.0.6

Conversion Rate Optimization (CRO)

You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.

Reference Routing

Load the matching reference before recommending changes in these areas. Use the page analysis below for the initial diagnosis; references supply the detailed recommendations.

| User intent | Load | Covers | |---|---|---| | Lead, contact, demo, or quote form abandonment; fields, validation, mobile forms | [form.md](references/form.md) | Field decisions, form layouts, errors, trust, measurement, and form-specific experiments | | Experiment ideas for a homepage, pricing, demo, landing, feature, or resource page | [experiments.md](references/experiments.md) | Hypotheses organized by page type and cross-page tests; use **ab-testing** for test design and measurement |

Initial Assessment

**Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, identify:

1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other 2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales 3. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)

---

CRO Analysis Framework

Analyze the page across these dimensions, in order of impact:

1. Value Proposition Clarity (Highest Impact)

**Check for:**

  • Can a visitor understand what this is and why they should care within 5 seconds?
  • Is the primary benefit clear, specific, and differentiated?
  • Is it written in the customer's language (not company jargon)?

**Common issues:**

  • Feature-focused instead of benefit-focused
  • Too vague or too clever (sacrificing clarity)
  • Trying to say everything instead of the most important thing

2. Headline Effectiveness

**Evaluate:**

  • Does it communicate the core value proposition?
  • Is it specific enough to be meaningful?
  • Does it match the traffic source's messaging?

**Strong headline patterns:**

  • Outcome-focused: "Get [desired outcome] without [pain point]"
  • Specificity: Include numbers, timeframes, or concrete details
  • Social proof: "Join 10,000+ teams who..."

3. CTA Placement, Copy, and Hierarchy

**Primary CTA assessment:**

  • Is there one clear primary action?
  • Is it visible without scrolling?
  • Does the button copy communicate value, not just action?
  • Weak: "Submit," "Sign Up," "Learn More"
  • Strong: "Start Free Trial," "Get My Report," "See Pricing"

**CTA hierarchy:**

  • Is there a logical primary vs. secondary CTA structure?
  • Are CTAs repeated at key decision points?

4. Visual Hierarchy and Scannability

**Check:**

  • Can someone scanning get the main message?
  • Are the most important elements visually prominent?
  • Is there enough white space?
  • Do images support or distract from the message?

5. Trust Signals and Social Proof

**Types to look for:**

  • Customer logos (especially recognizable ones)
  • Testimonials (specific, attributed, with photos)
  • Case study snippets with real numbers
  • Review scores and counts
  • Security badges (where relevant)

**Placement:** Near CTAs and after benefit claims

6. Objection Handling

**Common objections to address:**

  • Price/value concerns
  • "Will this work for my situation?"
  • Implementation difficulty
  • "What if it doesn't work?"

**Address through:** FAQ sections, guarantees, comparison content, process transparency

7. Friction Points

**Look for:**

  • Too many form fields
  • Unclear next steps
  • Confusing navigation
  • Required information that shouldn't be required
  • Mobile experience issues
  • Long load times

---

Output Format

Structure your recommendations as:

Quick Wins (Implement Now)

Easy changes with likely immediate impact.

High-Impact Changes (Prioritize)

Bigger changes that require more effort but will significantly improve conversions.

Test Ideas

Hypotheses worth A/B testing rather than assuming.

Copy Alternatives

For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.

---

Page-Specific Frameworks

Homepage CRO

  • Clear positioning for cold visitors
  • Quick path to most common conversion
  • Handle both "ready to buy" and "still researching"

Landing Page CRO

  • Message match with traffic source
  • Single CTA (remove navigation if possible)
  • Complete argument on one page

Pricing Page CRO

  • Clear plan comparison
  • Recommended plan indication
  • Address "which plan is right for me?" anxiety

Feature Page CRO

  • Connect feature to benefit
  • Use cases and examples
  • Clear path to try/buy

Blog Post CRO

  • Contextual CTAs matching content topic
  • Inline CTAs at natural stopping points

---

Experiment Ideas

When recommending experiments, consider tests for:

  • Hero section (headline, visual, CTA)
  • Trust signals and social proof placement
  • Pricing presentation
  • Form optimization
  • Navigation and UX

**For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md)

---

Task-Specific Questions

1. What's your current conversion rate and goal? 2. Where is traffic coming from? 3. What does your signup/purchase flow look like after this page? 4. Do you have user research, heatmaps, or session recordings? 5.

Read more
@coreyhaines31
Ships withcoreyhaines31-marketing-skills

A collection of AI agent skills focused on marketing tasks. Built for technical marketers and founders who want AI coding agents to help with conversion optimization, copywriting, SEO, analytics, and growth engineering.

Stars on GitHub

Momentum

stars in total
57.5k
Star history of coreyhaines31/marketingskills on GitHub, a chart by star-history.com

More skills from other plugins.

seo

seo

Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability,…

@agricidaniel@agricidanielInstall Skill
brag

brag

Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag",…

brag2w21k
@latent-spaces@latent-spacesInstall Skill
geo-audit

geo-audit

Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit…

scroll-world

scroll-world

Build an immersive scroll-scrubbed "fly through the world" landing page for any industry or brand using Higgsfield. As the…

@oso95@oso95Install Skill

Questions about cro.

Which coding agents can use cro?
cro installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.