Page cro
Awesome Claude Skills, Tools for Customizing Claude AI workflows
npx -y skills add ranbot-ai/awesome-skills --skill page-croAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze and optimize individual pages for conversion performance.
SKILL.md
5.2 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it
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 / Mod
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most performance cost skills give in ~1.2k tokens
Counted across 803 of the 1,058 authors here whose files we hold, read 2026-08-07
- Keep skill files under 500 lines or tokensin 82 of 803, across 16 files
- Use imperative form in instructionsin 80 of 803, across 9 files
- Draft assertions while test runs are in progressin 75 of 803, across 9 files
- Create two to three realistic test promptsin 74 of 803, across 9 files
- Write skill descriptions to be pushyin 72 of 803, across 7 files
- Save test cases to evals JSONin 72 of 803, across 6 files
- Ask questions about edge cases and input formatsin 72 of 803, across 7 files
- Save timing data immediately when runs completein 70 of 803, across 5 files
- Include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
- Launch all test runs in a single turn or simultaneouslyin 69 of 803, across 3 files
- Capture intent before writing a skillin 67 of 803, across 1 file
- Import directly instead of barrel filesin 52 of 803, across 15 files
Said here and by no other author read
- explain why recommendations matter
- map recommendations to a conversion constraint
- demote secondary conversion goals explicitly
- assign a readiness verdict based on score
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.