SkillAgentSearch skills...

page-cro

Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and structured A/B testing.

Install / Use

npx skills add borghei/Claude-Skills --skill page-cro

Installs into whichever agent you are using.

About this skill
๐Ÿ“„

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Our assessment of page-cro

page-cro scores 92/100 on our quality scale, 317th of 1,156 Content & Media skills we index (top 28%).

Its SKILL.md is 23 KB long, well organised into 50 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so page-cro is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit โ€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk โ€” read a skill before letting an agent act on it.

page-cro compared with similar skills

All 4 of these similar skills score higher than page-cro; compare them before choosing.

SkillScoreStarsUpdatedFormat
page-cro (this skill)by borghei9281757d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install page-cro?
Run npx skills add borghei/Claude-Skills --skill page-cro. The install tabs above show the steps for each supported agent.
Which AI agents does page-cro work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is page-cro safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is page-cro still maintained?
The repository was last updated about 2 months ago, so page-cro is actively maintained.

name: page-cro description: > Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and structured A/B testing. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: [cro, landing-page, conversion-optimization, copywriting, ux]

Page CRO

Production-grade conversion rate optimization framework for marketing pages. Covers the 7-dimension analysis framework, page-type-specific playbooks, copy alternatives methodology, above-the-fold engineering, social proof hierarchy, objection handling patterns, and structured A/B test design.


Table of Contents


Clarify First

Before optimizing the page, confirm these inputs. If any is unknown or vague, ASK โ€” do not assume:

  • [ ] Page type โ€” homepage, landing page, pricing, feature, or blog (selects the page-type playbook and benchmark)
  • [ ] Traffic source โ€” organic, paid, email, or social (drives message-match requirements)
  • [ ] Primary conversion goal + current rate โ€” focuses the 7-dimension analysis and sets the baseline
  • [ ] Behavioral data available โ€” heatmaps / session recordings (reveals friction that analytics alone cannot)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit.

Initial Assessment

Required Context

| Question | Why It Matters | |----------|---------------| | What page type? (homepage, landing page, pricing, feature, blog) | Determines the CRO framework to apply | | What is the primary conversion goal? | Focuses the analysis | | Where is traffic coming from? (organic, paid, email, social) | Drives message-match requirements | | What is the current conversion rate? | Establishes the baseline | | What does the post-click flow look like? | The page may convert fine but the next step fails | | Do you have heatmaps or session recordings? | Behavioral data reveals what analytics cannot | | What have you already tried? | Avoids re-testing failed experiments |


The 7-Dimension CRO Framework

Analyze every marketing page across these 7 dimensions, in order of typical impact.

Dimension 1: Value Proposition Clarity (Highest Impact)

The 5-second test: Can a first-time visitor understand what this is, who it is for, and why they should care within 5 seconds?

| Signal | Pass | Fail | |--------|------|------| | Primary benefit is stated explicitly | "Save 10 hours/week on reporting" | "Next-generation analytics platform" | | Written in customer language | "See which campaigns drive revenue" | "Multi-touch attribution solution" | | Differentiator is clear | "The only CRM built for agencies" | "A better CRM" | | Specificity | Includes numbers, timeframes, outcomes | Vague superlatives ("powerful", "innovative") |

Dimension 2: Headline Effectiveness

Headline scoring rubric:

| Criteria | Score 0 | Score 1 | Score 2 | |----------|---------|---------|---------| | Communicates core value | No | Partially | Clearly | | Specific (numbers, outcomes) | Generic | Somewhat specific | Very specific | | Addresses target audience | Generic | Implied | Explicit | | Matches traffic source | No connection | Loose match | Exact message match | | Emotional or logical hook | Neither | One | Both |

Total: 0-10. Score < 6 = rewrite needed.

Dimension 3: CTA Hierarchy and Placement

| Check | Pass | Fail | |-------|------|------| | One clear primary CTA | Single, prominent action | Multiple competing CTAs | | CTA visible without scrolling | Above the fold | Below the fold only | | CTA copy communicates value | "Start Free Trial" | "Submit" | | CTA repeated at decision points | After benefits, after social proof, at bottom | Only at top or only at bottom | | Secondary CTA is clearly secondary | Smaller, different color, text link | Same visual weight as primary |

Dimension 4: Visual Hierarchy and Scannability

| Check | Pass | Fail | |-------|------|------| | Most important element is most prominent | Headline + CTA dominate | Navigation or image dominates | | Scannable in 10 seconds | Key points visible via headings, bold, bullets | Wall of text | | Adequate white space | Breathing room between sections | Cluttered, dense layout | | Images support the message | Product screenshots, relevant imagery | Stock photos, decorative graphics | | F-pattern or Z-pattern layout | Content follows natural eye flow | Random placement |

Dimension 5: Social Proof and Trust

| Check | Pass | Fail | |-------|------|------| | Customer logos visible | Recognizable logos above the fold | No logos or unknown companies | | Testimonials are specific | "Increased revenue by 40%" | "Great product!" | | Testimonials are attributed | Full name, title, company, photo | Anonymous or first-name-only | | Trust badges present (where relevant) | Security, compliance, awards | No trust indicators | | Numbers-based proof | "10,000+ teams use..." | No scale indicators |

Dimension 6: Objection Handling

| Check | Pass | Fail | |-------|------|------| | Price/value objection addressed | ROI calculation, "starts at $X" | No pricing context | | "Will this work for me?" answered | Use cases, industry examples | Generic positioning only | | Risk reduction offered | Free trial, guarantee, no CC required | No risk reversal | | Implementation concern addressed | "Set up in 5 minutes" | No setup/complexity context | | FAQ section present | Addresses top 5 objections | No FAQ or irrelevant questions |

Dimension 7: Friction Points

| Check | Pass | Fail | |-------|------|------| | Form is optimized | Minimal fields, clear labels | Too many fields, unclear purpose | | Next step is clear | Obvious path forward from every section | Confusing navigation or dead ends | | Mobile experience | Fully responsive, touch-friendly | Desktop-only design | | Load time | < 3 seconds | > 5 seconds | | No distracting elements | Clean, focused design | Popups, auto-play video, chat widget on load |


Above-the-Fold Engineering

The above-the-fold area is the most valuable real estate on any page. It determines whether visitors scroll or bounce.

Required Elements (Above the Fold)

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  [Nav: Logo + 3-5 links + Primary CTA]  โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚                                          โ”‚
โ”‚  HEADLINE: Primary value proposition     โ”‚
โ”‚                                          โ”‚
โ”‚  SUBHEADLINE: Supporting detail          โ”‚
โ”‚                                          โ”‚
โ”‚  [PRIMARY CTA BUTTON]                   โ”‚
โ”‚  [Secondary CTA: text link]             โ”‚
โ”‚                                          โ”‚
โ”‚  [Social proof: logos or stat]           โ”‚
โ”‚                                          โ”‚
โ”‚  [Hero image or product screenshot]      โ”‚
โ”‚                                          โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Above-the-Fold Rules

  • Headline is the largest text on the page
  • CTA button is the most visually prominent interactive element
  • Social proof appears above the fold (even just logo strip)
  • Hero image shows the product in use (not abstract graphics)
  • No auto-play video or animation that distracts from the CTA
  • Navigation is minimal (3-5 items max, CTA in nav)

Social Proof Hierarchy

Not all social proof is equal. Use the right type at the right location.

Social Proof Power Ranking

| Rank | Type | Strength | Best Placement | |------|------|----------|----------------| | 1 | Case study with metrics | "Company X increased revenue 40% in 3 months" | Mid-page, after benefits section | | 2 | Named testimonial with photo | Full name, title, company, headshot | Near CTA, after objection handling | | 3 | Aggregate numbers | "10,000+ teams" or "4.8/5 on G2" | Above the fold, near headline | | 4 | Customer logos | Recognizable brand logos | Above the fold, logo strip | | 5 | Awards/badges | "G2 Leader 2026", "SOC2 Certified" | Footer or near CTA | | 6 | Generic testimonial | "Great product!" -- no specifics | Do not use (no credibility) |

Placement Rules

  • Logo strip: Above the fold, below the CTA
  • Testimonials: After the section that makes the claim they validate
  • Case studies: Mid-page, as their own section
  • Numbers: Inline with headline or subheadline
  • Trust badges: Near the primary CTA and near the form

Objection Handling Architecture

The 5 Universal Objections

Every product page must address these five objections. If the page does not, conversions leak.

| Objection | How to Address | Page Element | |-----------|---------------|--------------| | "Is this worth the money?" | ROI calculator, pricing comparison, "saves X hours" | Benefits section + pricing context | | "Will this work for my situation?" | Industry examples, use case sections, persona targeting | "Who uses this" section | | "Is this hard to set up?" | "Set up in 5 minutes", onboarding preview, integration logos | Feature section or FAQ | | "What if it doesn't work?" | Free trial, money-back guarantee, no CC required | Near CTA | | "Why this over alternatives?" | Comparison table, differentiators, switcher testimonials | Mid-page or FAQ |

FAQ Design for Objection Handling

The FAQ section should be the last defense before conversion. Structure it to address the 5 objections:

  1. "How long does setup take?" (complexity objection)
  2. "Can I cancel anytime?" (commitment objection)
  3. "What's included in the free trial?" (value objection)
  4. "Do you integrate with [popular tool]?" (compatibility objection)
  5. "How is this different from [competitor]?" (alternatives objection)

Page-Type Playbooks

Homepage

| Element | Best Practice | |---------|---------------| | Audience | Cold visitors who may not know you | | Headline | Position the company, not a single feature | | CTA split | Primary: "Start Free Trial" / Secondary: "See Demo" or "Learn More" | | Content | Overview of benefits, social proof, feature highlights, use cases | | Navigation | Full site navigation (unlike landing pages) |

Landing Page (Paid Traffic)

| Element | Best Practice | |---------|---------------| | Navigation | Remove or minimize (no escape routes) | | Headline | Message-match with the ad that drove the click | | CTA | Single action, repeated 2-3 times down the page | | Content | Complete argument on one page: problem > solution > proof > CTA | | Social proof | Directly relevant to the ad audience |

Pricing Page

| Element | Best Practice | |---------|---------------| | Plan presentation | Good-Better-Best with recommended plan highlighted | | Toggle | Annual/Monthly with savings percentage shown | | Feature comparison | Full table below the fold | | FAQ | "Which plan is right for me?" as first question | | CTA | Per-plan CTA with plan-specific copy | | Social proof | Logos and testimonials relevant to each tier |

Feature Page

| Element | Best Practice | |---------|---------------| | Headline | Benefit of the feature, not the feature name | | Content | Use cases > technical capabilities | | Demo | Screenshot, GIF, or interactive demo | | CTA | "Try this feature" or "Start

Truncated for display โ€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryContent
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit โ€” see the Safety scan above for what the skill file itself contains.

1 medium
page-cro โ€” Universal Skill: Install & Safety Check | SkillAgent