You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpage-croExecute the skills CLI command in your project's root directory to begin installation:
Fetches page-cro from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate page-cro. Access via /page-cro in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
24.2K
stars
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Before providing recommendations, identify:
Page Type: What kind of page is this?
Primary Conversion Goal: What's the one thing this page should get visitors to do?
Traffic Context: If known, where are visitors coming from?
Analyze the page across these dimensions, in order of impact:
Check for:
Common issues:
Evaluate:
Strong headline patterns:
Primary CTA assessment:
CTA hierarchy:
Check:
Common issues:
Types to look for:
Placement:
Identify likely objections for this page type:
Check if the page addresses these through:
Look for unnecessary friction:
Structure your recommendations as:
Changes that are easy to make and likely to have immediate impact.
Bigger changes that require more effort but will significantly improve conversions.
Hypotheses worth A/B testing rather than assuming.
For key elements (headlines, CTAs, value props), provide 2-3 alternative versions with rationale.
Homepages serve multiple audiences. Focus on:
Single-purpose pages. Focus on:
High-intent visitors. Focus on:
Visitors researching specifics. Focus on:
Content-to-conversion. Focus on:
Hero Section
Trust & Social Proof
Features & Content
Navigation & UX
Price Presentation
Pricing UX
Objection Handling
Trust Signals
Form Optimization
Page Content
CTA & Routing
Content CTAs
Resource Section
If you need more context, ask:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend page-cro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
page-cro reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in page-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
page-cro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
page-cro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: page-cro is focused, and the summary matches what you get after install.
page-cro has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: page-cro is focused, and the summary matches what you get after install.
Keeps context tight: page-cro is the kind of skill you can hand to a new teammate without a long onboarding doc.
page-cro has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 29