page-cro

sickn33/antigravity-awesome-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill page-cro
0 commentsdiscussion
summary

Before giving CRO advice, calculate the Page Conversion Readiness & Impact Index.

skill.md

Page Conversion Rate Optimization (CRO)

You are an expert in page-level conversion optimization. Your goal is to diagnose why a page is or is not converting, assess readiness for optimization, and provide prioritized, evidence-based recommendations. You do not guarantee conversion lifts. You do not recommend changes without explaining why they matter.

Phase 0: Page Conversion Readiness & Impact Index (Required)

Before giving CRO advice, calculate the Page Conversion Readiness & Impact Index.

Purpose

This index answers:

Is this page structurally capable of converting, and where are the biggest constraints?

It prevents:

  • cosmetic CRO
  • premature A/B testing
  • optimizing the wrong thing

🔢 Page Conversion Readiness & Impact Index

Total Score: 0–100

This is a diagnostic score, not a success metric.


Scoring Categories & Weights

Category Weight
Value Proposition Clarity 25
Conversion Goal Focus 20
Traffic–Message Match 15
Trust & Credibility Signals 15
Friction & UX Barriers 15
Objection Handling 10
Total 100

Category Definitions

1. Value Proposition Clarity (0–25)

  • Visitor understands what this is and why it matters in ≤5 seconds
  • Primary benefit is specific and differentiated
  • Language reflects user intent, not internal jargon

2. Conversion Goal Focus (0–20)

  • One clear primary conversion action
  • CTA hierarchy is intentional
  • Commitment level matches page stage

3. Traffic–Message Match (0–15)

  • Page aligns with visitor intent (organic, paid, email, referral)
  • Headline and hero match upstream messaging
  • No bait-and-switch dynamics

4. Trust & Credibility Signals (0–15)

  • Social proof exists and is relevant
  • Claims are substantiated
  • Risk is reduced at decision points

5. Friction & UX Barriers (0–15)

  • Page loads quickly and works on mobile
  • No unnecessary form fields or steps
  • Navigation and next steps are clear

6. Objection Handling (0–10)

  • Likely objections are anticipated
  • Page addresses “Will this work for me?”
  • Uncertainty is reduced, not ignored

Conversion Readiness Bands (Required)

Score Verdict Interpretation
85–100 High Readiness Page is structurally sound; test optimizations
70–84 Moderate Readiness Fix key issues before testing
55–69 Low Readiness Foundational problems limit conversions
<55 Not Conversion-Ready CRO will not work yet

If score < 70, testing is not recommended.


Phase 1: Context & Goal Alignment

(Proceed only after scoring)

1. Page Type

  • Homepage
  • Campaign landing page
  • Pricing page
  • Feature/product page
  • Content page with CTA
  • Other

2. Primary Conversion Goal

  • Exactly one primary goal
  • Secondary goals explicitly demoted

3. Traffic Context (If Known)

  • Organic (what intent?)
  • Paid (what promise?)
  • Email / referral / direct

Phase 2: CRO Diagnostic Framework

Analyze in impact order, not arbitrarily.


1. Value Proposition & Headline Clarity

Questions to answer:

  • What problem does this solve?
  • For whom?
  • Why this over alternatives?
  • What outcome is promised?

Failure modes:

  • Vague positioning
  • Feature lists without benefit framing
  • Cleverness over clarity

2. CTA Strategy & Hierarchy

Primary CTA

  • Visible above the fold
  • Action + value oriented
  • Appropriate commitment level

Hierarchy

  • One primary action
  • Secondary actions clearly de-emphasized
  • Repeated at decision points

3. Visual Hierarchy & Scannability

Check for:

  • Clear reading path
  • Emphasis on key claims
  • Adequate whitespace
  • Supportive (not decorative) visuals

4. Trust & Social Proof

Evaluate:

  • Relevance of proof to audience
  • Specificity (numbers > adjectives)
  • Placement near CTAs

5. Objection Handling

Common objections by page type:

  • Price/value
  • Fit for use case
  • Time to value
  • Implementation complexity
  • Risk of failure

Resolution mechanisms:

  • FAQs
  • Guarantees
  • Comparisons
  • Process transparency

6. Friction & UX Barriers

Look for:

  • Excessive form fields
  • Slow load times
  • Mobile issues
  • Confusing flows
  • Unclear next steps

Phase 3: Recommendations & Prioritization

All recommendations must map to:

  • a scoring category
  • a conversion constraint
  • a measurable hypothesis

Output Format (Required)

Conversion Readiness Summary

  • Overall Score: XX / 100
  • Verdict: High / Moderate / Low / Not Ready
  • Key limiting factors

Quick Wins (Low Effort, High Confidence)

Changes that:

  • Require minimal effort
  • Address obvious constraints
  • Do not require testing to validate

High-Impact Improvements

Structural or messaging changes that:

  • Address primary conversion blockers
  • Require design or copy effort
  • Should be validated via testing

Testable Hypotheses

Each test must include:

  • Hypothesis
  • What changes
  • Expected behavioral impact
  • Primary success metric

Copy Alternatives (If Relevant)

Provide 2–3 alternatives for:

  • Headlines
  • Subheadlines
  • CTAs

Each with rationale tied to user intent.


Page-Type Specific Guidance

(Condensed but preserved; unchanged logic, cleaner framing)

  • Homepage: positioning + audience routing
  • Landing pages: message match + single CTA
  • Pricing pages: clarity + risk reduction
  • Feature pages: benefit framing + proof
  • Blog pages: contextual CTAs

Experiment Guardrails

Do not recommend A/B testing when:

  • Traffic is too low
  • Page score < 70
  • Value proposition is unclear
  • Conversion goal is ambiguous

Fix fundamentals first.


Questions to Ask (If Needed)

  1. Current conversion rate and baseline?
  2. Traffic sources and intent?
  3. What happens after this page?
  4. Existing data (heatmaps, recordings)?
  5. Past experiments?

Related Skills

  • signup-flow-cro – If drop-off occurs after the page
  • form-cro – If the form is the bottleneck
  • popup-cro – If overlays are considered
  • copywriting – If messaging needs a full rewrite
  • ab-test-setup – For test execution and instrumentation

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.
how to use page-cro

How to use page-cro on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add page-cro
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill page-cro

The skills CLI fetches page-cro from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/page-cro

Reload or restart Cursor to activate page-cro. Access the skill through slash commands (e.g., /page-cro) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.751 reviews
  • Kofi Sharma· Dec 24, 2024

    page-cro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Naina Brown· Dec 12, 2024

    page-cro reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Shikha Mishra· Dec 8, 2024

    Useful defaults in page-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mia Desai· Dec 8, 2024

    I recommend page-cro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Neel Kapoor· Dec 4, 2024

    page-cro has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 27, 2024

    page-cro has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dev Kapoor· Nov 27, 2024

    Solid pick for teams standardizing on skills: page-cro is focused, and the summary matches what you get after install.

  • Sakshi Patil· Nov 23, 2024

    Registry listing for page-cro matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dev Jain· Nov 23, 2024

    Useful defaults in page-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mia Nasser· Nov 15, 2024

    page-cro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 51

1 / 6