page-cro
Optimize conversion rates for landing and product pages
SKILL.mdplugins/marketing/skills/page-cro/SKILL.md
GitHubPage CRO
Optimize landing pages and product pages for "$ARGUMENTS". Analyze current conversion performance and recommend improvements to increase conversion rate.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/marketing/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
Read .metapowers/marketing/<project>/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "<project>". Run
/marketing:customer-research <project>first, or use--skip-checksto bypass.
Process
Read context:
- Read
.metapowers/marketing/<project>/00-strategy.mdfor audience and positioning - Read
.metapowers/marketing/<project>/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/<project>/02-act.mdunder a## Page CROsection. Create the file with a# Act — <project>heading if it does not exist; if a## Page CROsection already exists, replace only that section. The section contains:- 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/<project>/02-act.md. Present a summary highlighting:
- Top 3 conversion blockers identified
- Highest-impact recommendation
- Suggested first A/B test