Best use case
page-cro is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using page-cro should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/page-cro/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How page-cro Compares
| Feature / Agent | page-cro | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Page CRO
> **WHAT**: Analyze and optimize marketing pages for higher conversion rates
> **WHEN**: User wants to improve conversions on homepage, landing pages, pricing pages, feature pages, or blog posts; mentions "CRO," "page isn't converting," "improve conversions"
> **KEYWORDS**: CRO, conversion rate optimization, improve conversions, page optimization, landing page optimization, why isn't this converting
## Reference Files
- `references/experiments.md` - A/B test ideas by page type (100+ experiments)
## Installation
### OpenClaw / Moltbot / Clawbot
```bash
npx clawhub@latest install page-cro
```
---
## Workflow
### 1. Initial Assessment
Check for `.claude/product-marketing-context.md` first.
Identify:
- **Page Type**: Homepage, landing page, pricing, feature, blog, about
- **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download
- **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
Ask if not clear:
- What's your current conversion rate and goal?
- Do you have user research, heatmaps, or session recordings?
- What have you already tried?
### 2. Analyze by Priority
Evaluate in order of impact:
#### Value Proposition Clarity (Highest Impact)
- Can a visitor understand what this is within 5 seconds?
- Is the primary benefit clear, specific, and differentiated?
- Is it written in customer language (not company jargon)?
#### Headline Effectiveness
- Does it communicate the core value proposition?
- Is it specific enough to be meaningful?
- Does it match the traffic source's messaging?
#### CTA Placement, Copy, and Hierarchy
- Is there one clear primary action?
- Is it visible without scrolling?
- Does button copy communicate value, not just action?
#### Visual Hierarchy and Scannability
- Can someone scanning get the main message?
- Are the most important elements visually prominent?
- Do images support or distract from the message?
#### Trust Signals and Social Proof
- Customer logos (especially recognizable ones)
- Testimonials (specific, attributed, with photos)
- Case study snippets with real numbers
- Review scores and counts
#### Objection Handling
- Price/value concerns addressed?
- "Will this work for my situation?" answered?
- Implementation difficulty explained?
- Risk reversal present?
#### Friction Points
- Too many form fields?
- Unclear next steps?
- Confusing navigation?
- Mobile experience issues?
### 3. Structure Recommendations
```
## Quick Wins (Implement Now)
[Easy changes with likely immediate impact]
## High-Impact Changes (Prioritize)
[Bigger changes requiring more effort but significant impact]
## Test Ideas
[Hypotheses worth A/B testing rather than assuming]
## Copy Alternatives
[For headlines and CTAs, provide 2-3 alternatives with rationale]
```
---
## Page-Specific Frameworks
### Homepage CRO
- Clear positioning for cold visitors
- Quick path to most common conversion
- Handle both "ready to buy" and "still researching"
### Landing Page CRO
- Message match with traffic source
- Single CTA (remove navigation if possible)
- Complete argument on one page
### Pricing Page CRO
- Clear plan comparison
- Recommended plan indication
- Address "which plan is right for me?" anxiety
### Feature Page CRO
- Connect feature to benefit
- Use cases and examples
- Clear path to try/buy
### Blog Post CRO
- Contextual CTAs matching content topic
- Inline CTAs at natural stopping points
---
## Common Issues Checklist
### Value Proposition
- [ ] Feature-focused instead of benefit-focused
- [ ] Too vague or too clever (sacrificing clarity)
- [ ] Trying to say everything instead of the most important thing
### Headlines
- [ ] Generic (could apply to any competitor)
- [ ] Abstract instead of concrete
- [ ] Mismatch with traffic source
### CTAs
- [ ] Weak button copy (Submit, Sign Up, Learn More)
- [ ] Too many competing CTAs
- [ ] Not visible above fold
- [ ] Missing from key decision points
### Trust
- [ ] No social proof
- [ ] Vague testimonials ("Great product!")
- [ ] Missing trust indicators near conversion points
### Friction
- [ ] Too many form fields
- [ ] Required fields that shouldn't be required
- [ ] Unclear what happens next
- [ ] Poor mobile experience
---
## CTA Strength Guide
**Weak (avoid):**
- Submit
- Sign Up
- Learn More
- Click Here
- Get Started
**Strong (use):**
- Start Free Trial
- Get My Report
- See [Product] in Action
- Create Your First [Thing]
- Book My Demo
**Formula:** [Action Verb] + [What They Get] + [Qualifier if needed]
---
## Experiment Categories
See `references/experiments.md` for 100+ specific test ideas.
**Hero Section Tests:**
- Headline variations
- Visual format (screenshot vs. video vs. illustration)
- CTA button text and color
- Interactive demos
**Trust Signal Tests:**
- Logo placement and selection
- Testimonial format (text vs. video)
- Case study snippets
**Pricing Tests:**
- Number of tiers
- Annual vs. monthly default
- Plan recommendation badges
- Feature comparison format
**Form Tests:**
- Field count
- Multi-step vs. single
- Field enrichment
- Labels and placeholders
---
## NEVER
- Recommend changes without understanding traffic source
- Assume what works for one page works for all
- Skip asking about current conversion rate
- Ignore mobile experience
- Recommend removing navigation from homepage (only landing pages)
- Suggest fake urgency or scarcity
- Make recommendations without offering test alternatives
---
## Related Skills
- `copywriting` - Complete copy rewrites
- `marketing-psychology` - Psychological principles for conversion
- `marketing-ideas` - Tactical marketing approachesRelated Skills
schema-markup
Add, fix, or optimize schema markup and structured data. Use when the user mentions schema markup, structured data, JSON-LD, rich snippets, schema.org, FAQ schema, product schema, review schema, or breadcrumb schema.
prompt-engineering
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, designing production prompt templates, or building AI-powered features.
professional-communication
Write effective professional messages for software teams. Use when drafting emails, Slack/Teams messages, meeting agendas, status updates, or translating technical concepts for non-technical audiences. Triggers on email, slack, teams, message, meeting agenda, status update, stakeholder communication, escalation, jargon translation.
persona-docs
Create persona documentation for a product or codebase. Use when asked to create persona docs, document target users, define user journeys, document onboarding flows, or when starting a new product and needing to define its audience. Persona docs should be the first documentation created for any product.
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
game-changing-features
Find 10x product opportunities and high-leverage improvements. Use when the user wants strategic product thinking, mentions 10x, wants to find high-impact features, or asks what would make a product dramatically more valuable.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
brainstorming
Explore ideas before implementation through collaborative dialogue. Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Turns ideas into fully formed designs and specs through structured conversation.
Article Illustrator
When the user wants to add illustrations to an article or blog post. Triggers on: "illustrate article", "add images to article", "generate illustrations", "article images", or requests to visually enhance written content. Analyzes article structure, identifies positions for visual aids, and generates illustrations using a Type x Style two-dimension approach.
subagent-driven-development
Execute implementation plans by dispatching a fresh subagent per task with two-stage review (spec compliance then code quality). Use when you have an implementation plan with mostly independent tasks and want high-quality, fast iteration within a single session.
skill-judge
Evaluate Agent Skill quality against official specifications. Use when reviewing SKILL.md files, auditing skill packages, improving skill design, or checking if a skill follows best practices. Provides 8-dimension scoring (120 points) with actionable improvements. Triggers on review skill, evaluate skill, audit skill, improve skill, skill quality, SKILL.md review.
skill-creator
WHAT: Guide for creating effective AI agent skills - modular packages that extend Claude's capabilities with specialized knowledge, workflows, and tools. WHEN: User wants to create, write, author, or update a skill. User asks about skill structure, SKILL.md format, or how to package domain knowledge for AI agents. KEYWORDS: "create a skill", "make a skill", "new skill", "skill template", "SKILL.md", "agent skill", "write a skill", "skill structure", "package a skill"