方法与优势
当前 cro Skill 合并了原 page-cro 与 form-cro,并提供按页面类型分类的实验参考。
检查营销页与表单的转化阻力,并提出可测试改动。
检查营销页与表单的转化阻力,并提出可测试改动。当前 cro Skill 合并了原 page-cro 与 form-cro,并提供按页面类型分类的实验参考。
当前 cro Skill 合并了原 page-cro 与 form-cro,并提供按页面类型分类的实验参考。
审查落地页价值说明与 CTA;减少线索或联系表单的填写阻力;准备附依据的页面实验优先级。
页面 URL 或截图、转化目标、流量来源、基线数据和客户顾虑。
使用能发现已安装 Skill 并读取辅助文件的兼容 Agent。外部服务或创作运行环境需另行配置。
建议是假设,不是已测得的提升;Skill 不会自行部署改动或运行 A/B 平台。
在具备 Node.js/npm 的环境运行,并选择实际使用的 Agent。此方式取得当前上游包,可能比本页核对的提交更新。
npx skills add coreyhaines31/marketingskills --skill cro以下为已核对版本未经改写的 SKILL.md。安装完整包才能保留引用的脚本、素材和指引。下方启动提示词为 EcomAgentTools 编写的示例。
2026 年 10 月 25 日核对源码及随包文件:GitHub e85f3cbc2e4a。 当前包标识为 cro。本次为静态审查,不代表已完成安装运行或业务效果测试。
MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
---
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](references/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](references/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:
1. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
2. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
3. **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](references/experiments.md)
---
## Task-Specific Questions
1. What's your current conversion rate and goal?
2. Where is traffic coming from?
3. What does your signup/purchase flow look like after this page?
4. Do you have user research, heatmaps, or session recordings?
5. 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](https://github.com/coreyhaines31/marketingskills/blob/main/skills/revops/references/inbound-routing.md): 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](references/form.md).
以下是主要功能的用例提示词,可以直接复制使用。
审查落地页价值说明与 CTA 适用于:审查落地页价值说明与 CTA。请准备:页面 URL 或截图、转化目标、流量来源、基线数据和客户顾虑。
请使用已安装的 cro Skill。任务:审查落地页价值说明与 CTA。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。建议是假设,不是已测得的提升;Skill 不会自行部署改动或运行 A/B 平台。[INPUT][CONSTRAINTS]减少线索或联系表单的填写阻力 适用于:减少线索或联系表单的填写阻力。请准备:页面 URL 或截图、转化目标、流量来源、基线数据和客户顾虑。
请使用已安装的 cro Skill。任务:减少线索或联系表单的填写阻力。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。建议是假设,不是已测得的提升;Skill 不会自行部署改动或运行 A/B 平台。[INPUT][CONSTRAINTS]准备附依据的页面实验优先级 适用于:准备附依据的页面实验优先级。请准备:页面 URL 或截图、转化目标、流量来源、基线数据和客户顾虑。
请使用已安装的 cro Skill。任务:准备附依据的页面实验优先级。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。建议是假设,不是已测得的提升;Skill 不会自行部署改动或运行 A/B 平台。[INPUT][CONSTRAINTS]建议是假设,不是已测得的提升;Skill 不会自行部署改动或运行 A/B 平台。
2026 年 10 月 25 日核对源码及随包文件:GitHub e85f3cbc2e4a。 当前包标识为 cro。本次为静态审查,不代表已完成安装运行或业务效果测试。
使用获授权输入,不把密钥贴入提示词。采用前检查面向客户的声明、计算、代码改动及任何拟议的外部操作。
检查营销页与表单的转化阻力,并提出可测试改动。当前 cro Skill 合并了原 page-cro 与 form-cro,并提供按页面类型分类的实验参考。
按实际 Agent 选择方式,安装完整包,不要只复制页面中的 SKILL.md。 页面 URL 或截图、转化目标、流量来源、基线数据和客户顾虑。 开启新 Agent 会话,明确要求使用 cro。先用小型样本尝试下方一个场景,并检查输出。
审查落地页价值说明与 CTA;减少线索或联系表单的填写阻力;准备附依据的页面实验优先级
建议是假设,不是已测得的提升;Skill 不会自行部署改动或运行 A/B 平台。
2026 年 10 月 25 日核对源码及随包文件:GitHub e85f3cbc2e4a。 当前包标识为 cro。本次为静态审查,不代表已完成安装运行或业务效果测试。
2026 年 10 月 25 日核对源码及随包文件:GitHub e85f3cbc2e4a。 当前包标识为 cro。本次为静态审查,不代表已完成安装运行或业务效果测试。
2026 年 10 月 25 日核对源码及随包文件:GitHub e85f3cbc2e4a。 当前包标识为 cro。本次为静态审查,不代表已完成安装运行或业务效果测试。
内容核验日期:
暂无评论。