IntermediateAgent Skill

CRO (formerly Page CRO)

Review marketing pages and forms for conversion friction and propose testable changes.

Views
0
Copies
0
Favorites
0
Editorial Score
87/100
Supported Platforms
Claude Code · Codex
01

What this Skill does

Review marketing pages and forms for conversion friction and propose testable changes. The current cro skill combines the former page-cro and form-cro workflows with page-specific experiment references.

02

What makes it different

01

Approach and advantage

The current cro skill combines the former page-cro and form-cro workflows with page-specific experiment references.

02

What you can use it for

Audit the value proposition and CTA on a landing page; Reduce friction in a lead or contact form; Prepare prioritized page experiments with evidence.

03

Before you install

Inputs to prepare

Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.

Agent and runtime

Use a compatible agent that can discover the installed Skill and read its supporting files. Any external service or creative runtime must be configured separately.

Scope to confirm

Recommendations are hypotheses, not measured uplift. The Skill does not deploy changes or run an A/B platform by itself.

04

Install and get started

Skills CLI

Run with Node.js/npm available and select the agent you use. This fetches the current upstream package, which may be newer than the reviewed commit.

  1. Choose the method for your agent and install the complete package, not just the displayed SKILL.md.
  2. Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.
  3. Start a new agent session and explicitly ask to use cro. Try one use case below with a small sample and review the output.
npx skills add coreyhaines31/marketingskills --skill cro
05

Original Skill.md

This is the unchanged source SKILL.md for the reviewed version. Install the complete package to retain referenced scripts, assets, and instructions. Starter prompts below are EcomAgentTools examples.

Source and package files reviewed on October 25, 2026: GitHub e85f3cbc2e4a. Current package identifier: cro. This is a static review, not an installation or business-outcome test.

View the reviewed source · MIT

License notice
MIT License

Copyright (c) 2025 Corey Haines

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
---
name: cro
description: "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."
metadata:
  version: 2.0.3
---

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

---

## Related Skills

- **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](https://github.com/coreyhaines31/marketingskills/blob/main/skills/revops/references/inbound-routing.md): 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](references/form.md).
06

Get started

Starter prompts for the main use cases—copy and use them directly.

01

Audit the value proposition and CTA on a landing page

Audit the value proposition and CTA on a landing page Use for: Audit the value proposition and CTA on a landing page. Prepare: Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.

Show prompt and variablesHide prompt and variables
Use the installed cro Skill. Task: Audit the value proposition and CTA on a landing page. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. Recommendations are hypotheses, not measured uplift. The Skill does not deploy changes or run an A/B platform by itself.

Replace these variables

[INPUT]
Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.
[CONSTRAINTS]
Scope, allowed actions, output format, and review requirements.
02

Reduce friction in a lead or contact form

Reduce friction in a lead or contact form Use for: Reduce friction in a lead or contact form. Prepare: Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.

Show prompt and variablesHide prompt and variables
Use the installed cro Skill. Task: Reduce friction in a lead or contact form. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. Recommendations are hypotheses, not measured uplift. The Skill does not deploy changes or run an A/B platform by itself.

Replace these variables

[INPUT]
Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.
[CONSTRAINTS]
Scope, allowed actions, output format, and review requirements.
03

Prepare prioritized page experiments with evidence

Prepare prioritized page experiments with evidence Use for: Prepare prioritized page experiments with evidence. Prepare: Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.

Show prompt and variablesHide prompt and variables
Use the installed cro Skill. Task: Prepare prioritized page experiments with evidence. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. Recommendations are hypotheses, not measured uplift. The Skill does not deploy changes or run an A/B platform by itself.

Replace these variables

[INPUT]
Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections.
[CONSTRAINTS]
Scope, allowed actions, output format, and review requirements.
07

Risks and operating notes

Known limits

Recommendations are hypotheses, not measured uplift. The Skill does not deploy changes or run an A/B platform by itself.

Evidence and review

Source and package files reviewed on October 25, 2026: GitHub e85f3cbc2e4a. Current package identifier: cro. This is a static review, not an installation or business-outcome test.

Before acting on the result

Use authorized inputs and keep secrets out of prompts. Review customer-facing claims, calculations, code changes, and any proposed external action before applying them.

Frequently asked questions

What does it do, and what is the advantage?

Review marketing pages and forms for conversion friction and propose testable changes. The current cro skill combines the former page-cro and form-cro workflows with page-specific experiment references.

How do I install it and start?

Choose the method for your agent and install the complete package, not just the displayed SKILL.md. Page URL or screenshot, conversion goal, traffic source, baseline data, and customer objections. Start a new agent session and explicitly ask to use cro. Try one use case below with a small sample and review the output.

Which situations is it useful for?

Audit the value proposition and CTA on a landing page; Reduce friction in a lead or contact form; Prepare prioritized page experiments with evidence

What limitations should I know?

Recommendations are hypotheses, not measured uplift. The Skill does not deploy changes or run an A/B platform by itself.

What was checked for this page?

Source and package files reviewed on October 25, 2026: GitHub e85f3cbc2e4a. Current package identifier: cro. This is a static review, not an installation or business-outcome test.

Community rating results

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result

No reviews yet.

Leave a review

Rate every dimension, then share your real experience.

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result
Author / maintainer

Corey Haines

Source and package files reviewed on October 25, 2026: GitHub e85f3cbc2e4a. Current package identifier: cro. This is a static review, not an installation or business-outcome test.

Content checked: