$npx -y skills add indranilbanerjee/digital-marketing-pro --skill croOptimize conversion rates. Use when: auditing landing pages, testing forms, or improving checkout flow.
| 1 | # CRO (Conversion Rate Optimization) |
| 2 | |
| 3 | ## When to Use This Skill |
| 4 | |
| 5 | Activate this skill when the user's request involves any of the following: |
| 6 | |
| 7 | - Auditing a landing page for conversion performance |
| 8 | - Designing or improving a landing page layout, copy, or user flow |
| 9 | - Setting up, analyzing, or interpreting A/B tests or multivariate tests |
| 10 | - Optimizing web forms (lead gen, signup, contact, application) |
| 11 | - Designing or auditing pricing pages and pricing presentation |
| 12 | - Reducing cart abandonment or improving checkout completion rates |
| 13 | - Improving any website conversion metric (lead form submissions, signups, purchases, trial starts) |
| 14 | - Calculating sample sizes, test duration, or statistical significance for experiments |
| 15 | - Prioritizing which conversion improvements to tackle first |
| 16 | - Diagnosing why a page or funnel has a low conversion rate |
| 17 | - Asking about trust signals, social proof, urgency elements, or CTA optimization |
| 18 | |
| 19 | ## Brand Context (Auto-Applied) |
| 20 | |
| 21 | Before producing any marketing output from this module: |
| 22 | |
| 23 | 1. **Check session context** — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there. |
| 24 | 2. **If you need the full profile**, read: `~/.claude-marketing/brands/{slug}/profile.json` |
| 25 | 3. **Apply brand voice** — Formality, energy, humor, authority levels must shape all content tone and word choices |
| 26 | 4. **Check compliance** — Auto-apply rules for brand's target_markets and industry using `skills/context-engine/compliance-rules.md` |
| 27 | 5. **Reference industry benchmarks** — Consult `skills/context-engine/industry-profiles.md` for the brand's industry |
| 28 | 6. **Use platform specs** — Reference `skills/context-engine/platform-specs.md` for character limits and format requirements |
| 29 | 7. **Check campaign history** — Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns` before planning new work |
| 30 | 8. **If no brand exists**, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices." |
| 31 | 9. **Check brand guidelines** — If `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` exists, load and enforce: `restrictions.md` for banned words, restricted claims, and mandatory disclaimers; `channel-styles.md` for channel-specific tone overrides (may differ from base voice); `messaging.md` for approved key messages, taglines, and positioning language; `voice-and-tone.md` for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings. |
| 32 | |
| 33 | Do not ask the user for information that already exists in their brand profile. |
| 34 | |
| 35 | ## Required Context |
| 36 | |
| 37 | Before executing, gather the following from the user (ask if not provided): |
| 38 | |
| 39 | - **Page URL or description**: The specific page or flow being optimized |
| 40 | - **Current conversion rate**: Baseline metric to improve against (if known) |
| 41 | - **Monthly traffic volume**: Needed for test duration and statistical significance calculations |
| 42 | - **Conversion goal**: What counts as a conversion (form submit, purchase, signup, download) |
| 43 | - **Business model**: B2B, B2C, D2C, SaaS, ecommerce, lead gen |
| 44 | - **Traffic sources**: Where visitors come from (paid, organic, email, direct) since source affects intent level |
| 45 | - **Device split**: Percentage of mobile vs desktop traffic |
| 46 | - **Existing test history**: What has been tested before and results |
| 47 | - **Tech stack**: CMS, testing tools (Optimizely, VWO, Google Optimize successor, custom), analytics platform |
| 48 | - **Constraints**: Legal disclaimers required, brand guidelines, compliance restrictions |
| 49 | |
| 50 | ## Capabilities |
| 51 | |
| 52 | ### Landing Page Audits |
| 53 | - **5-second test**: Does the page communicate its value proposition within 5 seconds of loading? |
| 54 | - **Above-the-fold analysis**: Headline clarity, subheadline support, hero image relevance, primary CTA visibility |
| 55 | - **Trust signal inventory**: Logos, testimonials, reviews, certifications, security badges, guarantees |
| 56 | - **CTA assessment**: Clarity, contrast, placement, copy specificity, number of competing CTAs |
| 57 | - **Form evaluation**: Field count, field labels, required vs optional, error handling, multi-step vs single-step |
| 58 | - **Page speed impact**: Load time correlation to bounce rate, Core Web Vitals as conversion factors |
| 59 | - **Mobile experience**: Touch targets, scroll depth, thumb-zone CTA placement, mobile-specific friction points |
| 60 | - **Content hierarchy**: Information architecture, visual hierarchy, F-pattern or Z-pattern scanning support |
| 61 | - **Objection handling**: Whether the page addresses common objections before the conversion point |
| 62 | |
| 63 | ### A/B Testing Framework |
| 64 | - **ICE prioritization**: Score potential tests by Impact (1-10), Confidence (1-10), and Ease (1-10) to determine test order |
| 65 | - **Hypothesis format**: Structured as "If we [c |