Analyzes marketing pages, landing pages, and forms to identify friction points and provide actionable recommendations for improving conversion rates. It evaluates value propositions, CTA effectiveness, trust signals, and user experience to boost user engagement and desired actions.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill when a user wants to improve the performance of a specific marketing page, landing page, or form. It is appropriate when users report low conversion rates, high form abandonment, or ask for feedback on why a page is not performing well. It also applies when a user shares a URL and requests general optimization advice for increasing signups, sales, or leads.
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Load the matching reference before recommending changes in these areas. Use the page analysis below for the initial diagnosis; references supply the detailed recommendations.
| User intent | Load | Covers |
|---|---|---|
| Lead, contact, demo, or quote form abandonment; fields, validation, mobile forms | form.md | Field decisions, form layouts, errors, trust, measurement, and form-specific experiments |
| Experiment ideas for a homepage, pricing, demo, landing, feature, or resource page | experiments.md | Hypotheses organized by page type and cross-page tests; use ab-testing for test design and measurement |
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), 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: - Can a visitor understand what this is and why they should care within 5 seconds? - Is the primary benefit clear, specific, and differentiated? - Is it written in the customer's language (not company jargon)?
Common issues: - Feature-focused instead of benefit-focused - Too vague or too clever (sacrificing clarity) - Trying to say everything instead of the most important thing
Evaluate: - Does it communicate the core value proposition? - Is it specific enough to be meaningful? - Does it match the traffic source's messaging?
Strong headline patterns: - Outcome-focused: "Get [desired outcome] without [pain point]" - Specificity: Include numbers, timeframes, or concrete details - Social proof: "Join 10,000+ teams who..."
Primary CTA assessment: - Is there one clear primary action? - Is it visible without scrolling? - Does the button copy communicate value, not just action? - Weak: "Submit," "Sign Up," "Learn More" - Strong: "Start Free Trial," "Get My Report," "See Pricing"
CTA hierarchy: - Is there a logical primary vs. secondary CTA structure? - Are CTAs repeated at key decision points?
Check: - Can someone scanning get the main message? - Are the most important elements visually prominent? - Is there enough white space? - Do images support or distract from the message?
Types to look for: - Customer logos (especially recognizable ones) - Testimonials (specific, attributed, with photos) - Case study snippets with real numbers - Review scores and counts - Security badges (where relevant)
Placement: Near CTAs and after benefit claims
Common objections to address: - Price/value concerns - "Will this work for my situation?" - Implementation difficulty - "What if it doesn't work?"
Address through: FAQ sections, guarantees, comparison content, process transparency
Look for: - Too many form fields - Unclear next steps - Confusing navigation - Required information that shouldn't be required - Mobile experience issues - Long load times
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: - Hero section (headline, visual, CTA) - Trust signals and social proof placement - Pricing presentation - Form optimization - Navigation and UX
For comprehensive experiment ideas by page type: See references/experiments.md
When enrichment controls the next step after a lead form, use the revops inbound-routing playbook: preserve valid submissions, bound the lookup wait, and provide a useful fallback when qualification is unknown.
For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see references/form.md.
LICENSESKILL.mdevals/evals.jsonreferences/experiments.mdreferences/form.mdVendored from coreyhaines31/marketingskills, commit e85f3cbc2e4a, path skills/cro, licence MIT. The upstream licence file ships inside the skill.