Page cro
Optimize conversion rates for landing and product pagesFrom its SKILL.md
npx -y skills add bromso/metapowers --skill page-croAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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.
SKILL.md
2.5 KB, 585 tokens by cl100k_base, as published. Nobody here has run it
Page CRO
Optimize landing pages and product pages for "$ARGUMENTS". Analyze current conversion performance and recommend improvements to increase conversion rate.
Prerequisites
Read .metapowers/marketing/$ARGUMENTS/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "$ARGUMENTS". Run
/marketing:customer-research $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/marketing/$ARGUMENTS/skip-log.md.
Process
-
Read context:
- Read
.metapowers/marketing/$ARGUMENTS/00-strategy.mdfor audience and positioning - Read
.metapowers/marketing/$ARGUMENTS/02-act.mdif it exists
- Read
-
Page audit (if URL provided):
- Use WebFetch to analyze the page
- Evaluate: headline clarity, value proposition visibility, CTA prominence, social proof, objection handling
- Check page speed and mobile experience
- Identify friction points in the conversion path
-
Analyze page structure:
- Above-the-fold content: does it answer "what, who, why"?
- Information hierarchy: is the most important content most prominent?
- Visual flow: does the eye naturally reach the CTA?
- Content length: appropriate for the decision complexity?
-
CRO recommendations:
- Headline and subheadline improvements
- CTA placement, copy, and design recommendations
- Social proof placement and type
- Objection handling and FAQ placement
- Trust signals (security badges, guarantees, testimonials)
- Page speed and technical improvements
-
A/B test suggestions:
- Identify the highest-impact elements to test
- For each: hypothesis, variant description, expected impact
- Prioritize by potential uplift and ease of implementation
-
Write the artifact — append to
.metapowers/marketing/$ARGUMENTS/02-act.mdunder a## Page CROsection:- Current State Assessment — strengths and weaknesses
- Recommendations — prioritized by impact
- A/B Test Suggestions — with hypotheses
- Wireframe Notes — suggested layout changes
- Expected Impact — estimated conversion lift per change
Output
Page CRO analysis appended to .metapowers/marketing/$ARGUMENTS/02-act.md. Present a summary highlighting:
- Top 3 conversion blockers identified
- Highest-impact recommendation
- Suggested first A/B test
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.