Page Cro
Diagnose why a marketing URL under-converts and get prioritized CRO fixes for hero, proof, CTA, and page structure.
Overview
Page CRO is an agent skill most often used in Validate (also Launch, Grow) that analyzes marketing pages and recommends concrete changes to improve conversion rates on homepages, landings, pricing, and feature pages.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill page-croWhat is this skill?
- Analyzes homepage, landing, pricing, feature, blog, and other marketing URLs for conversion blockers
- Classifies page type and primary conversion goal before recommending changes
- Loads product marketing context from `.agents/product-marketing-context.md` when available
- Explicitly defers signup flows, onboarding, forms, and popups to sibling CRO skills
- Treats a pasted URL plus “feedback” as an implicit CRO request per skill triggers
Adoption & trust: 57.7k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your marketing page gets visits but almost nobody signs up, requests a demo, or clicks the primary CTA, and you cannot tell which section is killing trust or clarity.
Who is it for?
Indie SaaS founders tuning a landing or pricing page before ads, launches, or investor demos when you can share the URL and goal.
Skip if: Multi-step signup wizards, in-app onboarding, generic form fields, or modal popups—use signup-flow-cro, onboarding-cro, form-cro, or popup-cro respectively.
When should I use this skill?
User wants CRO on marketing pages, says conversion rate optimization, low conversions, high bounce, or shares a URL for conversion feedback.
What do I get? / Deliverables
You receive a prioritized CRO assessment tied to page type and conversion goal so you can rewrite hero, proof, and CTAs with confidence before spending on ads or SEO scale-up.
- Page-type and goal assessment
- Prioritized CRO recommendation list
- Section-level copy and layout improvement notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate is the canonical shelf because landing and pre-launch pages are where solo builders first test message-market fit and signup intent before scaling traffic. Landing subphase matches homepage, landing, pricing, and feature pages whose primary job is persuasion and conversion—not in-app onboarding flows.
Where it fits
Stress-test a waitlist landing hero and social proof before you buy your first ad spend.
Improve a feature page that ranks but fails to convert organic visitors to trials.
Re-audit homepage CTAs after positioning pivot when signup rate drops week over week.
Clarify pricing page value metric and plan comparison tables when trials stall at the paywall click.
How it compares
An audit-and-recommendation skill for page copy and structure, not a heatmap tool or automated A/B testing platform.
Common Questions / FAQ
Who is page-cro for?
Solo builders and small teams responsible for their own marketing site who need expert-style CRO feedback without hiring an agency for every URL.
When should I use page-cro?
Use it in Validate while testing landing and pricing pages, in Launch when polishing homepage or feature pages before distribution, and in Grow when conversion slips after messaging changes—even if you only paste a URL and ask if the page works.
Is page-cro safe to install?
The skill is advisory text; it may encourage sharing public URLs and context files locally—confirm trust via the Security Audits panel on this Prism catalog page.
SKILL.md
READMESKILL.md - Page Cro
# Page 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. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` 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 experie