page-cro

Trigger phrases

Phrases that activate this skill when typed to Claude Code:

• CRO
• this page is not converting
• improve conversions
• low conversion rate
• why is this page not working

What it does

page-cro is a Claude Code skill from Corey Haines’s marketing-skills repo. It turns Claude into a conversion-rate consultant who fetches a live page and produces a structured teardown — hero clarity, value prop, social proof, friction, CTA hierarchy — with specific changes to test, not vague “improve clarity” advice. The skill activates when you mention “CRO”, “this page isn’t converting”, “improve conversions”, or shares a URL with “what’s wrong with this page”.

The output of a session is a page audit: scored dimensions, top 3 quick wins, per-section recommendations with copy alternatives, friction inventory, and a prioritized A/B-test backlog.

When to use it

Reach for it when:

• You have a page with traffic and want a structured opinion before iterating
• A landing page launched and didn’t convert; you need a diagnosis
• You’re refreshing pricing and want pressure-tested recommendations

When not to reach for it:

• The page has no traffic — fix the funnel upstream first
• The conversion problem is product-fit, not page; CRO can’t paper over that

Install

The skill is distributed via Corey Haines’s marketing-skills repo. Install via the repo’s recommended path — copy the page-cro SKILL.md into your project’s .claude/skills/page-cro/ directory, or use the repo’s plugin install if you’ve set it up.

Once installed, the skill activates on the trigger phrases above. The first time it runs, it will check for .agents/product-marketing-context.md (or .claude/product-marketing-context.md) — populating that file with your product context first dramatically improves output quality across all of Haines’s marketing skills.

What a session looks like

A typical session has three phases:

1. Page fetch + read. WebFetch pulls the page; the skill identifies what conversion job the page actually has and who it’s serving (problem-aware vs solution-aware vs product-aware).
2. Per-section audit. Hero, value props, social proof, features, pricing, FAQ, CTA. Each section scored, with specific copy and structural recommendations.
3. Test backlog. Top 3 quick wins for this week, plus a prioritized A/B-test list ranked by impact-vs-effort.

The discipline that makes it work: specificity. The skill refuses to output “improve clarity” without showing the line that’s unclear and a rewrite. Every recommendation is testable.

Receipts

Honest reporting on what page-cro produces and where it has limits:

Where it works well:

• The audience-stage check catches the most common error — writing product-aware copy for problem-aware visitors
• Per-section scoring makes prioritization mechanical instead of vibes
• Test backlog is genuinely usable as input to ab-test-setup

Where it backfires:

• It can over-recommend on a page that’s already lean; not every page needs a rewrite
• Without analytics it can’t see actual drop-off; structural recommendations may not match the real bleeder

Pattern that works: trigger on a fresh page (early in iteration cycle, before you’ve already responded to feedback five times). Diminishing returns on a heavily-iterated page are real.

Source and attribution

Originally written by Corey Haines. The canonical SKILL.md and any supporting files live in the page-cro folder of his marketing-skills repository.

License: MIT. You can install, adapt, and redistribute the skill, with attribution preserved.

This page documents the skill from a practitioner’s perspective. For the formal spec and any updates, defer to the source repo.