Generated banner for Cro
Generated logo for Cro

Cro

Corey HainesCommunityCreated by Corey Haines

  • Skill
  • Guidelines
  • Business and productivity
  • MIT
  • No issues found

From the author

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 isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.
— the description by Corey Haines

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The CRO skill provides a systematic approach to diagnosing and improving the performance of marketing pages, including homepages, landing pages, and forms. It utilizes a multi-dimensional analysis framework that prioritizes value proposition clarity, headline effectiveness, CTA hierarchy, and trust signals. The skill guides users through an initial assessment of page type, goals, and traffic context, followed by actionable recommendations categorized into quick wins, high-impact changes, and A/B test hypotheses. It integrates specialized guidance for form optimization and experiment design to ensure data-driven improvements.

What it does

  • Analyzes page elements for value proposition clarity and messaging effectiveness.
  • Evaluates CTA placement, copy, and visual hierarchy to reduce friction.
  • Identifies opportunities for trust signals and social proof to overcome user objections.
  • Provides a structured framework for diagnosing form abandonment and improving completion rates.
  • Suggests specific A/B test hypotheses based on page type and user intent.
  • Offers copy alternatives for headlines and calls-to-action.

When to use it

  • When a marketing page or form is underperforming or experiencing low conversion rates.
  • When you need to audit a landing page or homepage for clarity and conversion potential.
  • When users report issues like form abandonment or unclear value propositions.
  • When planning A/B tests to optimize specific page sections like hero areas or pricing tables.

Advantages

  • Systematic, high-impact analysis framework.
  • Actionable, prioritized recommendations.
  • Integrates specialized knowledge for forms and experiment design.
  • Focuses on both immediate quick wins and long-term testing strategies.

Usage examples

“My landing page isn't converting. Can you take a look?”
The agent will ask for the URL, page goal, and traffic source, then perform a structured analysis of the value proposition, CTA, and visual hierarchy.
“We are seeing high abandonment on our demo request form. How can we fix it?”
The agent will evaluate the form's field count, layout, and labels, providing specific recommendations to reduce friction and improve completion rates.
“What should we A/B test on our pricing page to increase signups?”
The agent will suggest hypotheses regarding price presentation, plan comparison formats, and trust signals based on the pricing page CRO framework.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/coreyhaines31/cro/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip cro.zip -d .agents/skills

Documentation by Corey Haines

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 intentLoadCovers
Lead, contact, demo, or quote form abandonment; fields, validation, mobile formsform.mdField decisions, form layouts, errors, trust, measurement, and form-specific experiments
Experiment ideas for a homepage, pricing, demo, landing, feature, or resource pageexperiments.mdHypotheses 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


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. What have you already tried?


  • signup: If the issue is in the signup process itself

  • popups: If considering popups as part of the strategy

  • copywriting: If the page needs a complete copy rewrite

  • ab-testing: To properly test recommended changes


Form Optimization

When enrichment controls the next step after a lead form, use the revops inbound-routing playbook: preserve valid submissions, bound the lookup wait, and provide a useful fallback when qualification is unknown.

For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see references/form.md.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Corey Haines
Publisher
Corey Haines (Community)
Source
coreyhaines31/marketingskills · skills/cro · commit 96798cf
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Corey Haines or Corey Haines.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cro.zip