.github/skills/marketing/page-cro/SKILL.md
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
npx skillsauth add thesethrose/peptidecalc page-croInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, identify:
Analyze the page across these dimensions, in order of impact:
Check for:
Common issues:
Evaluate:
Strong headline patterns:
Primary CTA assessment:
CTA hierarchy:
Check:
Types to look for:
Placement: Near CTAs and after benefit claims
Common objections to address:
Address through: FAQ sections, guarantees, comparison content, process transparency
Look for:
Structure your recommendations as:
Easy changes with likely immediate impact.
Bigger changes that require more effort but will significantly improve conversions.
Hypotheses worth A/B testing rather than assuming.
For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
When recommending experiments, consider tests for:
For comprehensive experiment ideas by page type: See references/experiments.md
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
tools
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
testing
Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
testing
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.