Page Cro logo

Page Cro

Community
L-LesterYu
page-cro

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

Overview

PublisherL-LesterYu
RepositoryOpenClaw-hot-skills-zh
Skill namepage-cro
Stars
57
Forks
9
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by L-LesterYu on GitHub. Read the source before you install it.

Installation

Install the Page Cro AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/L-LesterYu/OpenClaw-hot-skills-zh/tree/main/skills/marketing-skills-zh/references/page-cro
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/L-LesterYu/OpenClaw-hot-skills-zh.git /tmp/OpenClaw-hot-skills-zh
mkdir -p .claude/skills
cp -r /tmp/OpenClaw-hot-skills-zh/skills/marketing-skills-zh/references/page-cro .claude/skills/page-cro
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Page Cro in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Page Cro on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Page Cro is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Before providing recommendations, identify:

  1. Page Type: What kind of page is this?

    • Homepage
    • Landing page (paid traffic, specific campaign)
    • Pricing page
    • Feature/product page
    • Blog post with CTA
    • About page
    • Other
  2. Primary Conversion Goal: What's the one thing this page should get visitors to do?

    • Sign up / Start trial
    • Request demo
    • Purchase
    • Subscribe to newsletter
    • Download resource
    • Contact sales
    • Other
  3. Traffic Context: If known, where are visitors coming from?

    • Organic search (what intent?)
    • Paid ads (what messaging?)
    • Social media
    • Email
    • Referral
    • Direct

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?
  • Does it address a real pain point or desire?
  • Is it written in the customer's language (not company jargon)?

Common issues:

  • Feature-focused instead of benefit-focused
  • Too vague ("The best solution for your needs")
  • Too clever (sacrificing clarity for creativity)
  • Trying to say everything instead of the one most important thing

2. Headline Effectiveness

Evaluate:

  • Does it communicate the core value proposition?
  • Is it specific enough to be meaningful?
  • Does it create curiosity or urgency without being clickbait?
  • Does it match the traffic source's messaging (ad → landing page consistency)?

Strong headline patterns:

  • Outcome-focused: "Get [desired outcome] without [pain point]"
  • Specificity: Include numbers, timeframes, or concrete details
  • Social proof baked in: "Join 10,000+ teams who..."
  • Direct address of pain: "Tired of [specific problem]?"

3. CTA Placement, Copy, and Hierarchy

Primary CTA assessment:

  • Is there one clear primary action?
  • Is it visible without scrolling (above the fold)?
  • Does the button copy communicate value, not just action?
    • Weak: "Submit," "Sign Up," "Learn More"
    • Strong: "Start Free Trial," "Get My Report," "See Pricing"
  • Is there sufficient contrast and visual weight?

CTA hierarchy:

  • Is there a logical primary vs. secondary CTA structure?
  • Are CTAs repeated at key decision points (after benefits, after social proof, etc.)?
  • Is the commitment level appropriate for the page stage?

4. Visual Hierarchy and Scannability

Check:

  • Can someone scanning get the main message?
  • Are the most important elements visually prominent?
  • Is there clear information hierarchy (H1 → H2 → body)?
  • Is there enough white space to let elements breathe?
  • Do images support or distract from the message?

Common issues:

  • Wall of text with no visual breaks
  • Competing elements fighting for attention
  • Important information buried below the fold
  • Stock photos that add nothing

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)
  • "As seen in" media mentions
  • Team/founder credibility

Placement:

  • Near CTAs (to reduce friction at decision point)
  • After benefit claims (to validate them)
  • Throughout the page at natural break points

6. Objection Handling

Identify likely objections for this page type:

  • Price/value concerns
  • "Will this work for my situation?"
  • Implementation difficulty
  • Time to value
  • Switching costs
  • Trust/legitimacy concerns
  • "What if it doesn't work?"

Check if the page addresses these through:

  • FAQ sections
  • Guarantee/refund policies
  • Comparison content
  • Feature explanations
  • Process transparency

7. Friction Points

Look for unnecessary friction:

  • Too many form fields
  • Unclear next steps
  • Confusing navigation
  • Required information that shouldn't be required
  • Broken or slow elements
  • Mobile experience issues
  • Long load times

Output Format

Structure your recommendations as:

Quick Wins (Implement Now)

Changes that are easy to make and likely to have 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, value props), provide 2-3 alternative versions with rationale.


Page-Specific Frameworks

Homepage CRO

Homepages serve multiple audiences. Focus on:

  • Clear positioning statement that works for cold visitors
  • Quick path to most common conversion action
  • Navigation that helps visitors self-select
  • Handling both "ready to buy" and "still researching" visitors

Landing Page CRO

Single-purpose pages. Focus on:

  • Message match with traffic source
  • Single CTA (remove navigation if possible)
  • Complete argument on one page (minimize clicks to convert)
  • Urgency/scarcity if genuine

Pricing Page CRO

High-intent visitors. Focus on:

  • Clear plan comparison
  • Recommended plan indication
  • Feature clarity (what's included/excluded)
  • Addressing "which plan is right for me?" anxiety
  • Easy path from pricing to checkout

Feature Page CRO

Visitors researching specifics. Focus on:

  • Connecting feature to benefit
  • Use cases and examples
  • Comparison to alternatives
  • Clear CTA to try/buy

Blog Post CRO

Content-to-conversion. Focus on:

  • Contextual CTAs that match content topic
  • Lead magnets related to article subject
  • Inline CTAs at natural stopping points
  • Exit-intent as backup

Experiment Ideas by Page Type

Homepage Experiments

Hero Section

  • Test headline variations (specific vs. abstract, benefit vs. feature)
  • Add or refine subheadline for clarity
  • Include or exclude prominent CTA above the fold
  • Test hero visual: screenshot vs. GIF vs. illustration vs. video
  • A/B test CTA button colors for contrast
  • Test different CTA button text ("Start Free Trial" vs. "Get Started" vs. "See Demo")
  • Add interactive demo to engage visitors immediately

Trust & Social Proof

  • Test placement of customer logos (hero vs. below fold)
  • Showcase case studies or testimonials in hero section
  • Add trust badges (security, compliance, awards)
  • Test customer count or social proof in headline

Features & Content

  • Highlight key features with icons and brief descriptions
  • Test feature section order and prominence
  • Add or remove secondary CTAs throughout page

Navigation & UX

  • Add sticky navigation bar with persistent CTA
  • Test navigation menu order (high-priority items at edges)
  • Add prominent CTA button in nav bar
  • Live chat widget vs. AI chatbot for instant support
  • Optimize footer for clarity and secondary conversions

Pricing Page Experiments

Price Presentation

  • Highlight annual billing discounts vs. show monthly only vs. show both
  • Test different pricing points ($99 vs. $100 vs. $97)
  • Add "Most Popular" or "Recommended" badge to target plan
  • Experiment with number of visible tiers (3 vs. 4 vs. 2)
  • Use price anchoring strategically

Pricing UX

  • Add pricing calculator for complex/usage-based pricing
  • Turn complex pricing table into guided multistep form
  • Test feature comparison table formats
  • Add toggle for monthly/annual with savings highlighted
  • Test "Contact Sales" vs. showing enterprise pricing

Objection Handling

  • Add FAQ section addressing common pricing objections
  • Include ROI calculator or value demonstration
  • Add money-back guarantee prominently
  • Show price-per-user breakdowns for team plans
  • Include "What's included" clarity for each tier

Trust Signals

  • Add testimonials specific to pricing/value
  • Show customer logos near pricing
  • Display review scores from G2/Capterra

Demo Request Page Experiments

Form Optimization

  • Simplify demo request form (fewer fields)
  • Test multi-step form with progress bar vs. single-step
  • Test form placement: above fold vs. after content
  • Add or remove phone number field
  • Use field enrichment to hide known fields

Page Content

  • Optimize demo page content with benefits above form
  • Add product video or GIF showing demo experience
  • Include "What You'll Learn" section
  • Add customer testimonials near form
  • Address common objections in FAQ

CTA & Routing

  • Test demo button CTAs ("Book Your Demo" vs. "Schedule 15-Min Call")
  • Offer on-demand demo alongside live option
  • Personalize demo page messaging based on visitor data
  • Remove navigation to reduce distractions
  • Optimize routing: calendar link for qualified, self-serve for others

Resource/Blog Page Experiments

Content CTAs

  • Add floating or sticky CTAs on blog posts
  • Test inline CTAs within content vs. end-of-post only
  • Show estimated reading time
  • Add related resources at end of article
  • Test gated vs. free content strategies

Resource Section

  • Optimize resource section navigation and filtering
  • Add search functionality
  • Highlight featured or popular resources
  • Test grid vs. list view layouts
  • Create resource bundles by topic

Questions to Ask the User

If you need more context, ask:

  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 any user research, heatmaps, or session recordings?
  5. What have you already tried?

Related Skills

  • signup-flow-cro: If the issue is in the signup process itself, not the page leading to it
  • form-cro: If forms on the page need optimization
  • popup-cro: If considering popups as part of the conversion strategy
  • copywriting: If the page needs a complete copy rewrite rather than CRO tweaks
  • ab-test-setup: To properly test recommended changes

Frequently asked questions

What does the Page Cro AI skill do?

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

Why use Page Cro on TypingMind?

Because you install it once and use it with any model. Page Cro is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Page Cro in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/L-LesterYu/OpenClaw-hot-skills-zh/tree/main/skills/marketing-skills-zh/references/page-cro. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Page Cro?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Page Cro?

As many as you like. As long as a model supports skills, you can use Page Cro with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Page Cro AI skill free?

Yes. It is published on GitHub by L-LesterYu under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇