
Conversion Rate Optimization (CRO)
Skillmarketingskills 合集里的转化率优化技能:给它首页、落地页、定价页或表单的链接或内容,按价值主张、标题、按钮、信任背书、阻力点等维度诊断,输出马上能改的快速优化、高影响改动、A/B 测试思路和备选文案。
name: cro
description: "When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups."
metadata:
version: 2.0.3
Conversion Rate Optimization (CRO)
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
Reference Routing
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 |
Initial Assessment
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:
- Page Type: Homepage, landing page, pricing, feature, blog, about, other
- Primary Conversion Goal: Sign up, request demo, purchase, subscribe, download, contact sales
- Traffic Context: Where are visitors coming from? (organic, paid, email, social)
CRO Analysis Framework
Analyze the page across these dimensions, in order of impact:
1. Value Proposition Clarity (Highest 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
2. Headline Effectiveness
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..."
3. CTA Placement, Copy, and Hierarchy
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?
4. Visual Hierarchy and Scannability
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?
5. Trust Signals and Social Proof
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
6. Objection Handling
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
7. Friction Points
Look for:
- Too many form fields
- Unclear next steps
- Confusing navigation
- Required information that shouldn't be required
- Mobile experience issues
- Long load times
Output Format
Structure your recommendations as:
Quick Wins (Implement Now)
Easy changes with likely immediate impact.
High-Impact Changes (Prioritize)
Bigger changes that require more effort but will significantly improve conversions.
Test Ideas
Hypotheses worth A/B testing rather than assuming.
Copy Alternatives
For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
Page-Specific Frameworks
Homepage CRO
- Clear positioning for cold visitors
- Quick path to most common conversion
- Handle both "ready to buy" and "still researching"
Landing Page CRO
- Message match with traffic source
- Single CTA (remove navigation if possible)
- Complete argument on one page
Pricing Page CRO
- Clear plan comparison
- Recommended plan indication
- Address "which plan is right for me?" anxiety
Feature Page CRO
- Connect feature to benefit
- Use cases and examples
- Clear path to try/buy
Blog Post CRO
- Contextual CTAs matching content topic
- Inline CTAs at natural stopping points
Experiment Ideas
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
Task-Specific Questions
- What's your current conversion rate and goal?
- Where is traffic coming from?
- What does your signup/purchase flow look like after this page?
- Do you have user research, heatmaps, or session recordings?
- What have you already tried?
Related Skills
- signup: If the issue is in the signup process itself
- popups: If considering popups as part of the strategy
- copywriting: If the page needs a complete copy rewrite
- ab-testing: To properly test recommended changes
Form Optimization
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.
相關資源

Pricing Page
Skill为 SaaS 设计或重写高转化定价页:先收集方案、价格、限制、升级触发点与常见顾虑,再按价值标题、月付年付切换、三档方案、对比表、FAQ 与安全合规区块组织,并给出标题、方案说明与按钮文案模板。
MengTo/Skills6.8k
Wondel.ai Skills
Skill把《影响力》《StoryBrand》《精益创业》等商业、营销与设计畅销书的方法论做成技能,覆盖产品定位、营销文案、转化率优化、销售谈判和 UX 评审,另有引导创业、建站的分步技能(共 65 个,其中一部分面向编程);纯提示词,无需 API Key,也可按主题作为插件安装。
wondelai/skills2.4k
Landing Page
Skill为 SaaS、应用或服务设计或重写高转化落地页:先问清唯一的转化动作、受众、顾虑与证明素材,按首屏、论证、异议处理的结构编排,并提供版式类型、标题与 CTA 文案模板及 SEO 建议。
MengTo/Skills6.8k
Landing Page Design
Skill构建或修改落地页时分两部分工作:先收集目标、受众与证明材料,确定页面结构、版式、转化文案与 SEO;再遵循一套严格的视觉规则,规定字体、Tailwind 字号阶梯、间距、圆角、背景、图标与动效。规则偏主观,例如禁用 Inter 字体与背景渐变。
elayadesign/ai-design-skills2.7k
Balise UX Writing
Skill在当前 Figma 文件中审查、改写、生成或统一界面文案,覆盖按钮、表单、错误提示、空状态、引导、确认与授权等场景;只改选中范围,保留组件、变量绑定与自动布局,不编造功能、价格或法律表述,审查结果按优先级列表输出。
mrstev3n/balise-skills12
Huashu Design
Skill一句话让 agent 用 HTML 产出高保真可点击原型、可编辑幻灯片、时间轴动画(可导出 MP4/GIF)与信息图,先给三个设计方向再落地,附五维度设计评审。花叔出品,MIT 协议。
alchaincyf/huashu-design25.2k