Skill Tracer
Skills › Marketing Skills › cro

cro

skill · 198 lines · MIT · skills/cro/SKILL.md

The facts

Its 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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone wants to improve how well a marketing page or form converts — a homepage, landing page, pricing page, feature page, or a lead/contact/demo form — including when they simply share a URL and ask for feedback. It also fires on plain-language complaints like 'this page isn't converting' or 'form abandonment'.

Things a person might say (the model's guesses)

  • “Our landing page isn't converting — can you look at it and tell me what to fix?”
  • “Here's our pricing page URL, any feedback on how to improve conversions?”
  • “Our demo request form has a lot of abandonment. How do we get more people to finish it?”

A model's summary of when it is used.

A model's reading

Files it mentions

references/form.md, references/experiments.md

Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.

Found by matching wordsline 18 line 19 line 171 line 198

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

Other settings

metadata: version: 2.0.3

More settings at the top of the file, shown as written.

From its settingsline 4
Other files in this skill (3) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: cro
3description: "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."
4metadata:
5 version: 2.0.3
6---
7
8# Conversion Rate Optimization (CRO)
9
10You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.

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.

Raw lines 1 to 11
Names a skill signup :3
Names a skill onboarding :3
Names a skill popups :3
12## Reference Routing
14Load the matching reference before recommending changes in these areas. Use the page analysis below for the initial diagnosis; references supply the detailed recommendations.
16| User intent | Load | Covers |
17|---|---|---|
18| 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 |
19| 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 |

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 intentLoadCovers
Lead, contact, demo, or quote form abandonment; fields, validation, mobile formsform.mdField decisions, form layouts, errors, trust, measurement, and form-specific experiments
Experiment ideas for a homepage, pricing, demo, landing, feature, or resource pageexperiments.mdHypotheses organized by page type and cross-page tests; use ab-testing for test design and measurement
Raw lines 12 to 20
Reads a file references/form.md :18
Reads a file references/experiments.md :19
Names a skill ab-testing :19
21## Initial Assessment
24If `.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.
26Before providing recommendations, identify:
281. **Page Type**: Homepage, landing page, pricing, feature, blog, about, other
292. **Primary Conversion Goal**: Sign up, request demo, purchase, subscribe, download, contact sales
303. **Traffic Context**: Where are visitors coming from? (organic, paid, email, social)
32---

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)

Raw lines 21 to 33
Names a skill product-marketing :23
34## CRO Analysis Framework
36Analyze the page across these dimensions, in order of impact:

CRO Analysis Framework

Analyze the page across these dimensions, in order of impact:

Raw lines 34 to 37
38### 1. Value Proposition Clarity (Highest Impact)
40**Check for:**
41- Can a visitor understand what this is and why they should care within 5 seconds?
42- Is the primary benefit clear, specific, and differentiated?
43- Is it written in the customer's language (not company jargon)?
45**Common issues:**
46- Feature-focused instead of benefit-focused
47- Too vague or too clever (sacrificing clarity)
48- Trying to say everything instead of the most important thing

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
Raw lines 38 to 49
50### 2. Headline Effectiveness
52**Evaluate:**
53- Does it communicate the core value proposition?
54- Is it specific enough to be meaningful?
55- Does it match the traffic source's messaging?
57**Strong headline patterns:**
58- Outcome-focused: "Get [desired outcome] without [pain point]"
59- Specificity: Include numbers, timeframes, or concrete details
60- Social proof: "Join 10,000+ teams who..."

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..."
Raw lines 50 to 61
62### 3. CTA Placement, Copy, and Hierarchy
64**Primary CTA assessment:**
65- Is there one clear primary action?
66- Is it visible without scrolling?
67- Does the button copy communicate value, not just action?
68 - Weak: "Submit," "Sign Up," "Learn More"
69 - Strong: "Start Free Trial," "Get My Report," "See Pricing"
71**CTA hierarchy:**
72- Is there a logical primary vs. secondary CTA structure?
73- Are CTAs repeated at key decision points?

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?
Raw lines 62 to 74
75### 4. Visual Hierarchy and Scannability
77**Check:**
78- Can someone scanning get the main message?
79- Are the most important elements visually prominent?
80- Is there enough white space?
81- Do images support or distract from the message?

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?
Raw lines 75 to 82
83### 5. Trust Signals and Social Proof
85**Types to look for:**
86- Customer logos (especially recognizable ones)
87- Testimonials (specific, attributed, with photos)
88- Case study snippets with real numbers
89- Review scores and counts
90- Security badges (where relevant)
92**Placement:** Near CTAs and after benefit claims

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

Raw lines 83 to 93
94### 6. Objection Handling
96**Common objections to address:**
97- Price/value concerns
98- "Will this work for my situation?"
99- Implementation difficulty
100- "What if it doesn't work?"
102**Address through:** FAQ sections, guarantees, comparison content, process transparency

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

Raw lines 94 to 103
104### 7. Friction Points
106**Look for:**
107- Too many form fields
108- Unclear next steps
109- Confusing navigation
110- Required information that shouldn't be required
111- Mobile experience issues
112- Long load times
114---

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

Raw lines 104 to 115
116## Output Format
118Structure your recommendations as:

Output Format

Structure your recommendations as:

Raw lines 116 to 119
120### Quick Wins (Implement Now)
121Easy changes with likely immediate impact.

Quick Wins (Implement Now)

Easy changes with likely immediate impact.

Raw lines 120 to 122
123### High-Impact Changes (Prioritize)
124Bigger changes that require more effort but will significantly improve conversions.

High-Impact Changes (Prioritize)

Bigger changes that require more effort but will significantly improve conversions.

Raw lines 123 to 125
126### Test Ideas
127Hypotheses worth A/B testing rather than assuming.

Test Ideas

Hypotheses worth A/B testing rather than assuming.

Raw lines 126 to 128
129### Copy Alternatives
130For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
132---

Copy Alternatives

For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.


Raw lines 129 to 133
134## Page-Specific Frameworks

Page-Specific Frameworks

Raw lines 134 to 135
136### Homepage CRO
137- Clear positioning for cold visitors
138- Quick path to most common conversion
139- Handle both "ready to buy" and "still researching"

Homepage CRO

  • Clear positioning for cold visitors
  • Quick path to most common conversion
  • Handle both "ready to buy" and "still researching"
Raw lines 136 to 140
141### Landing Page CRO
142- Message match with traffic source
143- Single CTA (remove navigation if possible)
144- Complete argument on one page

Landing Page CRO

  • Message match with traffic source
  • Single CTA (remove navigation if possible)
  • Complete argument on one page
Raw lines 141 to 145
146### Pricing Page CRO
147- Clear plan comparison
148- Recommended plan indication
149- Address "which plan is right for me?" anxiety

Pricing Page CRO

  • Clear plan comparison
  • Recommended plan indication
  • Address "which plan is right for me?" anxiety
Raw lines 146 to 150
151### Feature Page CRO
152- Connect feature to benefit
153- Use cases and examples
154- Clear path to try/buy

Feature Page CRO

  • Connect feature to benefit
  • Use cases and examples
  • Clear path to try/buy
Raw lines 151 to 155
156### Blog Post CRO
157- Contextual CTAs matching content topic
158- Inline CTAs at natural stopping points
160---

Blog Post CRO

  • Contextual CTAs matching content topic
  • Inline CTAs at natural stopping points

Raw lines 156 to 161
162## Experiment Ideas
164When recommending experiments, consider tests for:
165- Hero section (headline, visual, CTA)
166- Trust signals and social proof placement
167- Pricing presentation
168- Form optimization
169- Navigation and UX
171**For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md)
173---

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


Raw lines 162 to 174
Reads a file references/experiments.md :171
175## Task-Specific Questions
1771. What's your current conversion rate and goal?
1782. Where is traffic coming from?
1793. What does your signup/purchase flow look like after this page?
1804. Do you have user research, heatmaps, or session recordings?
1815. What have you already tried?
183---

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?

Raw lines 175 to 184
185## Related Skills
187- **signup**: If the issue is in the signup process itself
188- **popups**: If considering popups as part of the strategy
189- **copywriting**: If the page needs a complete copy rewrite
190- **ab-testing**: To properly test recommended changes
192---

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

Raw lines 185 to 193
Names a skill copywriting :189
194## Form Optimization
196When 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.
198For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see [references/form.md](references/form.md).

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.

Raw lines 194 to 198
Names a skill revops :196
Reads a file references/form.md :198

From coreyhaines31/marketingskills at 88c79f6, 2026-10-30. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.