Landing Page Copy
rampstackco/claude-skills
Write landing page copy with attention to the hero, value proposition, social proof, objection handling, and conversion-focused CTAs.
Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and…
Install Page Cro
$ npx skills add borghei/Claude-Skills --skill page-cro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills page-cro --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-growth/page-cro .claude/skills/page-cro && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "page-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-cro into .claude/skills/page-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-cro", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-croType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill page-cro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills page-cro --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/business-growth/page-cro .agents/skills/page-cro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "page-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-cro into .agents/skills/page-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-cro", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill page-cro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills page-cro --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/business-growth/page-cro .cursor/skills/page-cro && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "page-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-cro into .cursor/skills/page-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-cro", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path business-growth/page-cro--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill page-cro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills page-cro --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/business-growth/page-cro .gemini/skills/page-cro && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "page-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-cro into .gemini/skills/page-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-cro", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills page-croInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill page-cro -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/business-growth/page-cro .github/skills/page-cro && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "page-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-cro into .github/skills/page-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-cro", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill page-cro -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills page-cro --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/business-growth/page-cro .opencode/skills/page-cro && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "page-cro" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/page-cro into .opencode/skills/page-cro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-cro", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
page-cro- GitHub stars
- 886
- Token cost
- ~5.9k tokens
- SKILL.md length
- 2,674 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and…
- Works in 3 steps: page_cro_scorer.py → headline_scorer.py → conversion_benchmark_calculator.py
- Tasks that involve Conversion rate optimization
- SKILL.md covers Table of Contents, Clarify First, Initial Assessment and The 7-Dimension CRO Framework, plus 5 more sections
- Runs Python scripts from its folder; calls python
What it does
Page Cro is an agent skill from borghei/Claude-Skills. 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.
Its SKILL.md is about 5.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/conversion_benchmark_calculator.py`, `scripts/headline_scorer.py` and `scripts/page_cro_scorer.py`).
It sits in Marketing & SEO, covering Conversion rate optimization, Marketing psychology and Sales enablement. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Tasks that involve Conversion rate optimization
- Tasks that involve Marketing psychology
- Tasks that involve Sales enablement
Example prompts
- “/page-cro”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Page Cro loads about 5.9k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 2,674 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,674 words, ~5,896 tokens.
Download SKILL.mdSave it as
.claude/skills/page-cro/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- 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
- metadata.author
- borghei
- metadata.category
- business-growth
- metadata.updated
- 2026-03-31
- metadata.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
- Initial Assessment
- The 7-Dimension CRO Framework
- Above-the-Fold Engineering
- Social Proof Hierarchy
- Objection Handling Architecture
- Page-Type Playbooks
- Copy Alternatives Methodology
- Traffic Source Matching
- A/B Test Framework
- Metrics and Benchmarks
- Output Artifacts
- Related Skills
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:
- "How long does setup take?" (complexity objection)
- "Can I cancel anytime?" (commitment objection)
- "What's included in the free trial?" (value objection)
- "Do you integrate with [popular tool]?" (compatibility objection)
- "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 Free Trial" |
| Internal links | Link to related features and pricing |
Blog Post
| Element | Best Practice |
|---|---|
| CTA type | Contextual inline CTA matching the content topic |
| Placement | After introduction, at natural breaks, at end |
| CTA style | Inline banner or text link, not aggressive popup |
| Content CTA | Offer a related resource (template, checklist, tool) |
Copy Alternatives Methodology
When recommending copy changes, always provide 2-3 alternatives with reasoning.
Alternative Generation Framework
For each key element (headline, subheadline, CTA), generate variants across these axes:
| Axis | Variant A | Variant B | Variant C |
|---|---|---|---|
| Benefit focus | Outcome-focused | Problem-focused | Feature-focused |
| Specificity | Numbers and data | Customer quote | Use case scenario |
| Tone | Direct and assertive | Conversational | Aspirational |
Example
Current headline: "Marketing Automation Software"
| Variant | Copy | Rationale |
|---|---|---|
| A (outcome) | "Generate 3X More Qualified Leads Without Adding Headcount" | Specific outcome + pain point |
| B (problem) | "Stop Losing Leads Because Your Team Can't Follow Up Fast Enough" | Addresses the pain directly |
| C (social proof) | "How 2,000+ Marketing Teams Hit Their Pipeline Targets" | Authority + specificity |
Recommendation: Test A first (most specific), B if A does not outperform current (different psychological angle).
Traffic Source Matching
Different traffic sources require different page optimization strategies.
| Source | Visitor State | Page Must Do |
|---|---|---|
| Paid search (brand) | Knows you, high intent | Fast path to action, minimal education |
| Paid search (non-brand) | Problem-aware, solution-seeking | Prove you solve their specific problem |
| Paid social | Interrupted, low intent | Hook attention, educate, build interest |
| Organic search | Research-mode | Comprehensive content, gradual conversion |
| Already engaged | Deliver on the email promise, reduce friction | |
| Referral | Pre-sold by referrer | Validate referrer's recommendation, fast CTA |
Message Match Audit
For paid traffic: Compare the ad copy with the landing page headline. They must share:
- The same language/terminology
- The same promise
- The same offer
- Visual consistency (if display ad)
Mismatch = wasted ad spend. Users who click an ad about "free SEO audit" and land on a generic homepage will bounce.
Show full SKILL.md (1,045 more words)Show less
A/B Test Framework
Test Priority Matrix
| Priority | What to Test | Expected Impact |
|---|---|---|
| 1 | Headline copy | 10-30% conversion lift |
| 2 | CTA copy and color | 5-20% conversion lift |
| 3 | Social proof placement | 5-15% conversion lift |
| 4 | Above-the-fold layout | 5-20% conversion lift |
| 5 | Form field reduction | 5-10% completion lift |
| 6 | Hero image vs video | 2-10% lift (variable) |
Test Design Rules
- One variable per test (unless running a multivariate test with sufficient traffic)
- Minimum 200 conversions per variant before declaring a winner
- Run for full business cycles (minimum 2 weeks)
- Track downstream metrics (not just page conversion, but lead quality / revenue)
Fix vs Test Decision
| Situation | Action |
|---|---|
| Obvious UX problem (broken form, missing CTA) | Fix immediately, no test needed |
| Missing social proof | Add it, no test needed |
| Headline copy alternative | A/B test |
| Layout change | A/B test |
| Removing page elements | A/B test |
| Adding a new section | A/B test |
Metrics and Benchmarks
Conversion Rate Benchmarks
| Page Type | Below Average | Average | Good | Excellent |
|---|---|---|---|---|
| SaaS homepage | < 2% | 2-4% | 4-7% | > 7% |
| Landing page (paid) | < 5% | 5-10% | 10-20% | > 20% |
| Pricing page | < 3% | 3-5% | 5-10% | > 10% |
| Blog post (to email) | < 1% | 1-3% | 3-5% | > 5% |
| Feature page | < 2% | 2-5% | 5-8% | > 8% |
Key Metrics
| Metric | What It Tells You |
|---|---|
| Bounce rate | Is the page meeting visitor expectations? |
| Scroll depth | How much of the page are visitors seeing? |
| Time on page | Are visitors reading or immediately leaving? |
| CTA click rate | Is the CTA compelling and visible? |
| Form start rate | Are visitors beginning the conversion process? |
| Form completion rate | Are they finishing it? |
Output Artifacts
| Artifact | Format | Description |
|---|---|---|
| CRO Audit Report | 7-dimension analysis | Per-dimension assessment with severity ratings |
| Quick Wins List | Bullet list (max 5) | Implementable today with expected impact |
| High-Impact Recommendations | Structured list | Each with rationale, effort estimate, and success metric |
| Copy Alternatives | Side-by-side table | 2-3 variants per key element with reasoning |
| A/B Test Plan | Prioritized table | Hypothesis, variant, success metric, priority |
| Traffic Source Matching Audit | Source x page element table | Message match assessment per traffic source |
Related Skills
- form-cro -- Use when the form on the page is the specific bottleneck (field optimization, validation, mobile form UX).
- signup-flow-cro -- Use when users convert on the page but drop off during the signup/registration process.
- popup-cro -- Use when considering a popup as an additional conversion layer on the page.
- onboarding-cro -- Use when post-conversion activation is the real problem and the page itself converts adequately.
- pricing-strategy -- Use when the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks.
Tool Reference
1. page_cro_scorer.py
Purpose: Score a marketing page across the 7 CRO dimensions and generate an audit report with severity ratings.
python scripts/page_cro_scorer.py page_audit.json
python scripts/page_cro_scorer.py page_audit.json --json| Flag | Required | Description |
|---|---|---|
page_audit.json | Yes | JSON file with page elements and dimension checks |
--json | No | Output results as JSON |
2. headline_scorer.py
Purpose: Score headline effectiveness against the 5-criteria rubric and generate copy alternatives.
python scripts/headline_scorer.py --headline "Marketing Automation Software" --audience "B2B marketers" --traffic-source paid-search
python scripts/headline_scorer.py --headline "Marketing Automation Software" --json| Flag | Required | Description |
|---|---|---|
--headline | Yes | The headline text to score |
--audience | No | Target audience description (default: "general") |
--traffic-source | No | Primary traffic source: organic, paid-search, paid-social, email, referral (default: organic) |
--json | No | Output results as JSON |
3. conversion_benchmark_calculator.py
Purpose: Calculate conversion rate benchmarks for a given page type, traffic source, and industry, and assess current performance.
python scripts/conversion_benchmark_calculator.py --page-type landing-page --traffic paid --current-rate 8.5
python scripts/conversion_benchmark_calculator.py --page-type homepage --traffic organic --current-rate 3.0 --json| Flag | Required | Description |
|---|---|---|
--page-type | Yes | Page type: homepage, landing-page, pricing, feature, blog |
--traffic | Yes | Traffic source: organic, paid, email, social, referral |
--current-rate | Yes | Current conversion rate as percentage |
--industry | No | Industry for benchmarks: saas, ecommerce, fintech, healthcare, education (default: saas) |
--json | No | Output results as JSON |
Troubleshooting
| Problem | Likely Cause | Solution |
|---|---|---|
| High bounce rate (>70%) on landing page | Message mismatch with traffic source or poor above-the-fold | Audit message match: compare ad copy with landing page headline; ensure value proposition is visible in first 5 seconds |
| Page converts on desktop but not mobile | Mobile UX not optimized | Check touch targets (44px+), form field count on mobile, CTA visibility without scrolling; score with page_cro_scorer.py |
| CTA click rate below 2% | CTA is generic, below the fold, or visually weak | Replace "Submit" with value-specific copy; ensure CTA is visible above fold and repeated after key sections |
| High scroll depth but low conversion | Visitors read but are not convinced to act | Add social proof near CTA positions; address objections in FAQ; add risk reversal (free trial, no CC) |
| A/B test shows no significant winner after 4 weeks | Change too small to detect or insufficient traffic | Use ab_test_calculator.py from form-cro to validate sample size; test bigger changes (headline rewrite vs word swap) |
| Paid traffic converts worse than organic | Landing page not tailored to paid traffic intent | Create dedicated landing pages for paid campaigns with message match; remove navigation on paid landing pages |
| Social proof section is ignored | Generic testimonials or poor placement | Use specific, attributed testimonials with metrics; place after the section that makes the claim they validate |
Success Criteria
- Page CRO score of 70+ across the 7-dimension framework (scored by page_cro_scorer.py)
- Headline scores 7+ on the 10-point rubric (scored by headline_scorer.py)
- Conversion rate at or above industry benchmark for page type (verified by conversion_benchmark_calculator.py)
- Above-the-fold contains: headline, CTA, and at least one social proof element
- Message match verified for all paid traffic campaigns (ad copy matches landing page headline)
- Mobile conversion rate within 20% of desktop rate
- Every page addresses at least 3 of the 5 universal objections
Scope & Limitations
- In scope: Page-level conversion optimization, headline effectiveness, CTA hierarchy, social proof placement, objection handling, traffic source matching, A/B test prioritization
- Out of scope: Form optimization (use form-cro), signup flow optimization (use signup-flow-cro), popup optimization (use popup-cro), pricing structure changes (use pricing-strategy)
- Page speed: This skill covers CRO elements, not technical performance; pages loading >3 seconds need technical optimization first
- Traffic minimum: A/B testing recommendations require 200+ conversions per variant; low-traffic pages should implement best practices without testing
- Qualitative input: Heatmaps and session recordings provide critical behavioral data that analytics alone cannot reveal; consider investing in these tools
Integration Points
- form-cro -- When the form on the page is the bottleneck (field optimization, validation UX, mobile form experience)
- signup-flow-cro -- When users convert on the page but drop off during the signup/registration process
- popup-cro -- When considering a popup as an additional conversion layer on top of the page
- onboarding-cro -- When post-conversion activation is the real problem and the page itself converts adequately
- pricing-strategy -- When the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks
- competitive-teardown -- When comparison pages need competitive data to build credible content
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in business-growth/page-cro of borghei/Claude-Skills.
- SKILL.md
- scripts/conversion_benchmark_calculator.py
- scripts/headline_scorer.py
- scripts/page_cro_scorer.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Page Cro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Page Cro this skillborghei/Claude-Skills | 886 | — | ~5.9k | Automated safety check: Pass | MIT | |
| Landing Page Copyrampstackco/claude-skills | 941 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Cro Methodologywondelai/skills | 2.4k | — | ~4.3k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Competitor Teardownirinabuht12-oss/marketing-skills | 4k | — | ~1.6k | Automated safety check: Pass | None | |
| Afa Convertafadtc/afa-dtc-skills | 168 | — | ~2.3k | Automated safety check: Pass | Custom licence |
Similar skills
Cro Methodology
wondelai/skills
Audit websites and landing pages for conversion issues and design evidence-based A/B tests.
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Competitor Teardown
irinabuht12-oss/marketing-skills
Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.
Afa Convert
afadtc/afa-dtc-skills
DTC 转化率优化——结账优化、弃单挽回、落地页、A/B测试、信任与无障碍。触发词: 转化率, CRO, 加购, 结账, 弃单, 落地页, A/B测试, 转化漏斗, conversion rate, abandoned cart, checkout optimization, landing page, a/b test, add to cart。复杂问题先经 afa。
Landing Optimizer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "optimize our landing page for influencer traffic", "fix our promo-code landing page", or "improve conversion from a creator campaign"; produces a…
More from borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Categories
Questions about Page Cro
What does Page Cro do?
Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and…. Page Cro is an agent skill from borghei/Claude-Skills. 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.
When should I use Page Cro?
Page Cro fits situations like: tasks that involve Conversion rate optimization; tasks that involve Marketing psychology; tasks that involve Sales enablement.
How do I install Page Cro in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill page-cro -a claude-code`. Or copy the skill folder (business-growth/page-cro in borghei/Claude-Skills) into .claude/skills/page-cro in your project. Claude Code loads it when a task matches its description.
How do I install Page Cro in Codex?
Run `npx skills add borghei/Claude-Skills --skill page-cro -a codex`. Or copy the skill folder (business-growth/page-cro in borghei/Claude-Skills) into .agents/skills/page-cro in your project. Codex loads it when a task matches its description.
Can I use Page Cro in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill page-cro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/page-cro, .gemini/skills/page-cro, .github/skills/page-cro and .opencode/skills/page-cro in your project.
What does Page Cro need to run?
Going by SKILL.md and its folder, Page Cro needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Page Cro access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Page Cro safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Page Cro use?
Page Cro is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Page Cro use?
About 5.9k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Page Cro?
Skills that share tags, products or a category with Page Cro: Landing Page Copy (rampstackco/claude-skills, 941 stars), Cro Methodology (wondelai/skills, 2.4k stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars) and Competitor Teardown (irinabuht12-oss/marketing-skills, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Page Cro?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.