IntermediateAgent Skill

CRO (formerly Page CRO)

Review ecommerce conversion rate optimization opportunities on a product, landing or signup page. Give your assistant the page, conversion goal, traffic source and known customer objections; this Skill examines the message, proof, calls to action and form friction, then proposes changes your team can test against the current experience.

Views
0
Copies
0
Favorites
0
Editorial Score
87/100
01

What this Skill does

A visitor may leave because the offer is unclear, the evidence is weak or the next step asks for too much. This Skill reviews those possibilities in the context of the page's purpose and the audience arriving there, rather than applying the same checklist to every page.

The current source combines page and form CRO guidance. Use its output to prioritize design or copy changes and define what an experiment should measure. Recommendations are hypotheses to validate; the Skill does not deploy the changes or operate an A/B testing platform.

02

What makes it different

01

Approach and advantage

The review connects messaging, proof and calls to action to one conversion goal. That helps separate a persuasive-copy problem from a usability problem, such as a form asking for unnecessary information before the visitor is ready.

02

What you can use it for

Page-specific experiment references help turn observations into testable proposals. Include baseline data and customer objections where available, then decide which change to try first and what evidence would support keeping it.

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

Copy this request into Codex or Claude Code. The assistant downloads the original repository at the specified commit, installs the complete files and checks required dependencies.

  1. Open Codex or Claude Code with local file and terminal access.
  2. Copy the request below into the app you are using. The assistant will select that app’s installation directory.
  3. Check the returned path and file checks. Start a new session if needed, then ask the assistant to use the installed Skill.
Install cro in the app I am using and carry out the file installation, not just explain it. Original repository: https://github.com/coreyhaines31/marketingskills.git Commit: e85f3cbc2e4a79bf33b2a12e9bdd9087d414735b Skill folder: skills/cro 1. Download this exact source into a new directory. Read SKILL.md and its setup references before running any bundled scripts. Do not substitute another author’s package. 2. For Codex, use ~/.agents/skills/cro; for Claude Code, use ~/.claude/skills/cro. Install only for my current app. Install the complete Skill folder, including scripts, references, assets and bundled notices. Keep any root license with the installed folder. Check all destination folders first; if any already exist, report differences before replacing them. 3. Compare the source and installed file lists and hashes. Inspect documented runtimes, dependencies and required connections. Configure only the local dependencies needed for this Skill; use an isolated environment when appropriate. Ask me to complete any account login locally, without putting credentials in chat. 4. Report the source commit, actual installation path, file-check results and any remaining runtime setup. Explain how to invoke cro in this app. Check discovery separately from file copying; start a new session if needed. Do not run production tasks or claim a successful business outcome from installation alone.
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.

---
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

Worked example: Turn landing-page and inquiry-form friction into concrete edits

A paid-social landing-page wireframe and an eight-required-field inquiry form have a 2.5% purchase baseline and 70% mobile share. The task is to clarify the product and simplify necessary actions.

Steps and prompt

  1. Prepare the attached business materials, preserving amounts, units, dates and metric definitions.
  2. Review our paid-social landing-page and inquiry-form brief. Identify the biggest obstacles to understanding the offer and completing a purchase or inquiry. Provide revised headline, CTA, shipping explanation, form fields, validation messages and success state. Separate necessary fixes from experiments and explain what to measure after implementation.
  3. Submit the exact prompt below. Read the primary deliverable on the right and download all deliverables for the team handoff.

Case input files: business-inputs.zip

Use the page-cro Skill.

Review our paid-social landing-page and inquiry-form brief. Identify the biggest obstacles to understanding the offer and completing a purchase or inquiry. Provide revised headline, CTA, shipping explanation, form fields, validation messages and success state. Separate necessary fixes from experiments and explain what to measure after implementation.

The attached business materials are:
- inputs/brief.md
- inputs/merchant.json

Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.

What the run produced

The primary file produced by this prompt is shown below in its original language.

Make the product and total cost clear before asking for a purchase

The brief describes a paid-social landing page for a $24 mug. Its headline hides the product, the first CTA sends shoppers to a form, and the information needed to judge fit sits in the footer. Correct those three issues first. This assessment uses the supplied text wireframe; it does not claim a browser inspection or observed customer interviews.

Measured baseline from the supplied fictional dataset

MeasurePriorCurrent
Orders / sessions100 / 4,000120 / 4,800
Order-to-session ratio2.50%2.50%

Sales and traffic grew together; purchase conversion did not improve. The 3% goal is a target, not a forecast.

DevicePage sessionsForm startsAccepted submissionsStart rateCompletion per start
Mobile3,360168425.00%25.00%
Desktop1,44072365.00%50.00%
Total4,800240785.00%32.50%

Mobile has more lost starts (126) than desktop (36). This prioritizes mobile investigation but does not prove which field caused abandonment. Page-to-accepted-submission rates are 1.25% mobile, 2.50% desktop and 1.625% overall.

Replacement first screen

Headline: A 500 ml stainless steel mug for your desk

Supporting copy: HarborMug holds your everyday cup in a blue insulated stainless steel mug. Check its 9 × 9 × 19 cm dimensions and care requirements before choosing it.

Price: $24 USD + $5 US shipping for one mug. $29 before applicable tax.

Primary CTA: Add to cart

Care line: Hand-wash only. Not microwave safe.

Delivery: Dispatch in 2 business days, followed by 3–5 business days in transit. US delivery only. Shipping is free on orders of $50 or more.

Returns: Unused returns within 30 days of delivery; final refunds require merchant approval.

Keep a quieter “Ask about this mug” link below the decision information. Buying remains possible without submitting a question or registering. Use a genuine product image when available; the supplied abstract illustration does not verify the product's appearance.

Alternative headline: “Meet HarborMug: 500 ml, $24.” It matches the ad's factual offer. A second alternative, “Check the fit before your next cup,” suits the dimensions section but is less clear as a cold-traffic headline. Do not replace facts with an untested superiority claim.

Inquiry form specification

Title: Have a question before ordering?

Description: “Tell us what you need to know about HarborMug. Our support team will reply to the email address you provide.” No reply-time SLA has been approved.

Order: Email (required, type=email, autocomplete=email); Your question (required textarea); Name (optional, autocomplete=name). The message remains required because support needs the actual question. Remove phone, company, role and order number from this pre-purchase flow. Keep persistent visible labels and a single column; use a comfortably tappable button of at least 44 px height.

CTA: Send my question. Pending: Sending…. Disable repeated submissions while a request is pending and use a request identifier to avoid duplicate tickets.

StateMessage and behaviour
Missing email“Enter the email address where we should reply.” Focus Email
Malformed email“Check your email address, for example shopper@example.com.” Keep entered values
Empty question“Tell us what you would like to know about the mug.” Focus question
Server/network failure“Your question was not sent. Your text is still here; please try again.” Preserve fields
Server accepted“Your question has been sent to our support team. We will reply by email.” Show Continue shopping

Show success only after server acceptance. Do not auto-subscribe to marketing. Route ordinary questions to the support owner; policy exceptions go to the escalation owner. Do not add an unapproved privacy or response-time promise.

Implementation order and experiments

The merchandiser owns factual headline, cost, care and shipping changes. The developer owns the direct purchase CTA, persistent labels, field reduction, accessible errors and reliable submission state. The analyst verifies one start and one accepted submission per session and separates attempt, failure and acceptance events without recording message text or email in analytics.

After those fixes, test a dimension image beside the purchase decision against the existing factual image. Hypothesis: shoppers can judge fit sooner. Another test can compare the two factual headlines. Define one primary purchase measure with a consistent attribution window before enrollment; track add-to-cart, accepted questions, technical errors and returns as secondary or guardrail measures. Do not bundle unrelated tests or claim field-count benchmarks predict this store's uplift.

Review mobile versus desktop completion, error category and time to accepted submission. Conduct five task-based sessions asking shoppers to find total cost, care restrictions and how to ask a question. Use observed failures to revise the page; five sessions diagnose usability and do not estimate a population conversion lift.

Merchant business data is synthetic. Website observations, when present, come from the public URLs listed in the report.

08

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: 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: GitHub e85f3cbc2e4a. Current package identifier: cro. This is a static review, not an installation or business-outcome test.

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: GitHub e85f3cbc2e4a. Current package identifier: cro. This is a static review, not an installation or business-outcome test.