MR
Mayur Rathi
@mayurrathi
⭐ 40.7k GitHub stars

Page Cro

Page Cro is an code AI skill with a core value of >. It helps developers solve real-world problems in the code domain, boosting efficiency, automating repetitive tasks, and optimizing workflows.

>

Last verified on: 2026-07-07

Quick Facts

Category code
Works With Claude
Source sickn33/antigravity-awesome-skills
Stars ⭐ 40.7k
Last Verified 2026-07-07
Risk Level Low
mkdir -p ./skills/page-cro && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/page-cro/SKILL.md -o ./skills/page-cro/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# 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 point

🎯 Best For

  • Claude users
  • Software engineers
  • Development teams
  • Tech leads

💡 Use Cases

  • Code quality improvement
  • Best practice enforcement

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Page Cro to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Is Page Cro compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for Page Cro?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install Page Cro?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/page-cro/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills