page-cro

Overview of page-cro skill

What the page-cro skill does

The page-cro skill is a structured prompt workflow for reviewing a marketing page and finding practical ways to improve conversion performance. It is designed for pages like homepages, landing pages, pricing pages, feature pages, blog posts, and demo pages where the job is not just “give feedback,” but “help more visitors take the next step.”

Who page-cro is best for

This page-cro skill fits marketers, founders, growth teams, product marketers, agencies, and operators who already have a page, traffic, and a desired action such as signup, demo request, purchase, subscription, or download. It is especially useful when someone shares a URL and asks why the page is underperforming.

The real job-to-be-done

Users do not just want a critique. They want a conversion-focused diagnosis that turns a vague concern like “this page is not converting” into:

• likely causes
• prioritized fixes
• stronger messaging ideas
• testable experiments

That makes page-cro more useful than a generic “review this page” prompt.

What makes page-cro different

The main differentiator is its decision frame. The skill pushes analysis through CRO-relevant dimensions such as:

• value proposition clarity
• headline effectiveness
• CTA placement and copy
• visual hierarchy
• trust signals
• objection handling
• friction points
• message match by traffic source

It also encourages outputs organized into quick wins, higher-impact changes, and experiment ideas, which is closer to how teams actually ship improvements.

When to choose another skill instead

Use a different skill if the main problem is not the page itself:

• signup or registration flow issues: use signup-flow-cro
• post-signup activation problems: use onboarding-cro
• standalone form optimization: use form-cro
• popup or modal performance: use popup-cro

How to Use page-cro skill

page-cro install options

If you use the Skills ecosystem, install page-cro from the repository with:

npx skills add https://github.com/coreyhaines31/marketingskills --skill page-cro

If you are reviewing before install, inspect:

• skills/page-cro/SKILL.md
• skills/page-cro/evals/evals.json
• skills/page-cro/references/experiments.md

These three files tell you most of what matters: scope, expected output shape, and test ideas.

What to read first before using page-cro

Start with SKILL.md to understand trigger conditions and the analysis flow. Then read:

• evals/evals.json for concrete examples of what good outputs include
• references/experiments.md for page-type-specific A/B test ideas

This reading order reduces guesswork more than skimming the whole repo.

The minimum input page-cro needs

The page-cro skill works best when you provide:

• page URL or pasted page copy
• page type
• primary conversion goal
• traffic source
• target audience
• current conversion issue or benchmark
• any constraints such as brand, legal, pricing, or dev limits

Without those inputs, the analysis can still be useful, but it becomes more speculative.

Best input format for page-cro usage

A strong prompt usually looks like this:

• “Analyze this pricing page for conversion: [URL]”
• “Primary goal: demo requests”
• “Traffic source: branded search and retargeting”
• “Audience: IT managers at mid-market SaaS companies”
• “Problem: lots of visits, low form starts”
• “Constraint: we cannot change pricing model this quarter”

This gives the skill enough context to judge message match, intent alignment, and likely objections.

Turn a rough request into a complete prompt

Weak prompt:

• “Can you improve this page?”

Better prompt:

• “Use the page-cro skill to review [URL]. This is a landing page for cold Google Ads traffic. Primary conversion is free trial signup. Audience is operations leaders at ecommerce brands. Current signup rate is 1.2% from 5,000 monthly visits. Please identify the biggest conversion blockers, then give quick wins, high-impact changes, and 5 A/B test ideas. Include 3 alternative headlines and 3 CTA variations.”

The stronger version produces better recommendations because it anchors the analysis to traffic quality, user intent, and conversion economics.

The most important context page-cro checks first

The upstream skill explicitly tells the agent to check for .agents/product-marketing-context.md or .claude/product-marketing-context.md before asking extra questions. If you have one of those files in your workspace, keep it updated. It can prevent repetitive questioning and improve recommendation quality by supplying positioning, audience, and product context up front.

Recommended page-cro workflow

A practical workflow is:

1. identify page type and conversion goal
2. note traffic source and message match
3. review hero, headline, subhead, CTA, and above-the-fold clarity
4. inspect trust, proof, objections, and friction
5. prioritize fixes by effort and likely impact
6. turn recommendations into experiments

This matters because many bad page reviews jump to copy tweaks before checking whether the offer, audience fit, or CTA path is wrong.

What page-cro seems optimized to output

Based on the evals, good page-cro usage should produce:

• diagnosis by CRO dimension
• quick wins
• high-impact changes
• test ideas
• headline or CTA alternatives
• notes about message match when traffic comes from ads or campaigns

That output shape is helpful if you need something your team can act on immediately.

How to use page-cro for different page types

The page-cro skill is broad, but your prompt should narrow the page type:

• homepage: clarify product, audience, and primary next step
• landing page: focus on message match and conversion focus
• pricing page: evaluate plan framing, comparison clarity, and objections
• feature page: check value translation from feature to outcome
• blog/resource page: optimize content-to-conversion path

The references/experiments.md file is especially useful here because it organizes ideas by page type instead of treating every page the same.

Practical tips that improve output quality

To get better results from page-cro for Conversion, include:

• screenshots if the page may change or be personalized
• exact CTA text
• whether traffic is warm or cold
• what visitors expected before arriving
• mobile vs desktop priority
• known objections from sales or support
• any analytics signal such as bounce, scroll depth, or click-through

These inputs help the skill separate messaging problems from UX friction and prioritization errors.

Common adoption blockers

The biggest blockers are usually not installation. They are:

• unclear conversion goal
• no traffic context
• no audience definition
• asking for “best practices” without the actual page
• using page-cro for flows that need a different CRO skill

If your use case is vague, the output will sound smart but be harder to act on.

page-cro skill FAQ

Is page-cro only for landing pages?

No. The page-cro skill covers homepages, pricing pages, feature pages, blog posts, demo pages, and other marketing pages. It is best whenever a page should drive a measurable next action.

Is page-cro beginner-friendly?

Yes, as long as you can provide the page and the goal. You do not need deep CRO expertise to use it, but better context leads to much better recommendations. Beginners should start with one URL, one conversion goal, and one audience.

How is page-cro different from a normal AI page review?

A normal prompt often gives generic design or copy advice. page-cro is more conversion-oriented: it asks what the page is, what action matters, where visitors come from, and what likely blocks action. That structure usually produces more usable prioritization.

Does page-cro help with experiments, not just critique?

Yes. The repository includes references/experiments.md, which adds concrete A/B testing ideas by page type. That makes the page-cro guide more useful for teams that want hypotheses to validate, not just recommendations to debate.

When should I not use page-cro?

Do not use page-cro when the issue is mainly:

• onboarding after signup
• registration flow optimization
• popup or modal performance
• form-specific tuning outside page context

Those cases have better-fit skills in the same repository.

Do I need analytics data to use page-cro?

No, but it helps. Even simple metrics like conversion rate, bounce rate, and traffic source make the recommendations more credible and more specific. Without data, the skill can still identify likely blockers, but confidence is lower.

Can page-cro work from a URL alone?

Yes, and the skill is explicitly meant to trigger even when a user just shares a URL and asks for feedback. Still, page-cro usage improves a lot if you also provide audience, traffic source, and conversion goal.

How to Improve page-cro skill

Give page-cro sharper business context

The highest-leverage improvement is better context, not longer prompts. Include:

• target customer
• traffic intent
• desired action
• offer details
• business constraints

This helps the skill judge whether a page problem is really about copy, trust, positioning, CTA fit, or offer mismatch.

Use stronger evidence in your prompt

Instead of saying “conversion is low,” say:

• “1.2% free trial conversion from cold Google Ads”
• “30% bounce on pricing page”
• “middle plan underselected”
• “mobile visitors drop before form start”

Specific evidence changes the analysis from generic critique to a more credible diagnosis.

Ask for prioritized output, not a brainstorm

If you want actionability, ask the page-cro skill to separate:

• quick wins
• high-impact changes
• experiments
• copy alternatives

That structure is supported by the evals and leads to outputs you can assign, test, and review.

Provide message-match context for paid traffic

One common failure mode is evaluating the page in isolation. If traffic comes from ads, email, affiliates, or a campaign, include the source copy or promise. page-cro for Conversion is notably stronger when it can compare the incoming promise with the page headline, CTA, and offer.

Improve headline and CTA requests

If you want the skill to write alternatives, be explicit:

• ask for 3 headline options
• ask for CTA variants by intent level
• ask for rationale for each option
• ask for the audience objection each option addresses

This produces better outputs than “rewrite the copy.”

Iterate after the first page-cro pass

A good second-round prompt is:

• “Now narrow to the top 3 blockers only.”
• “Rewrite the hero section based on your diagnosis.”
• “Turn your recommendations into an A/B test plan.”
• “Rank these ideas by expected impact and implementation effort.”

The first pass finds issues; the second pass turns them into execution.

Watch for common failure modes

The page-cro skill will be less useful when:

• the page has multiple competing goals
• there is no defined audience
• traffic quality is poor and the page gets blamed
• you ask for CRO help without sharing the actual page
• you expect deep funnel diagnosis from a single-page review

In those cases, tighten scope before rerunning.

Use repository files to deepen page-cro output

If the first result feels too high level, use the repository deliberately:

• SKILL.md for the core framework
• evals/evals.json for target output quality
• references/experiments.md for test ideas by page type

This is the fastest way to improve page-cro guide quality without reinventing the workflow.

Combine critique with implementation-ready deliverables

For better adoption, ask page-cro to produce:

• a revised hero section
• reordered page sections
• trust signal recommendations
• objection-handling copy
• test hypotheses with success metrics

That turns diagnosis into something a marketer, designer, or copywriter can actually ship.