All directories
SkillMarketingGrowth

CRO (Landing Page Conversion)

Marketing Skills sub-skill for conversion-rate optimization on homepages, landing pages, and forms—explicitly called out in BrowserAct’s marketing collection summary.

Open on GitHubBrowse more skills
01

Overview

CRO (Landing Page Conversion) is a Claude skill catalogued in LimeDock Directories for teams working across marketing, growth, product. It is tagged for saas, ecommerce, agency, other contexts. Marketing Skills sub-skill for conversion-rate optimization on homepages, landing pages, and forms—explicitly called out in BrowserAct’s marketing collection summary. Use this page as the operational brief: install path, how to invoke it, copy-paste prompts, prerequisites, and concrete use cases so your team can adopt it without re-reading every roundup article.

SaaSE-commerceAgencyOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/coreyhaines31/marketingskills/tree/main/skills/cro
03

Installation guide

npx skills add coreyhaines31/marketingskills --skill cro

After install, restart the Claude Code session (or re-open Claude.ai Skills) so the skill is discoverable. Confirm it appears in your skills list before relying on auto-trigger.

04

How to use it

Share the page URL/copy/goal; ask to optimize conversions with the cro skill.

**Suggested workflow** 1. Install and enable the skill. 2. Open the target project (or Claude.ai chat) with enough product context. 3. Invoke with a clear goal, constraints, and success criteria. 4. Review the first output against your standards; refine with follow-ups. 5. Save winning prompts / outputs into your team playbook.

If Claude does not auto-select it, mention the skill by name: “Use the CRO (Landing Page Conversion) skill…”

05

Example prompts

  • “Use the CRO (Landing Page Conversion) skill for this task: Homepage conversion teardown”
  • “Walk me through how CRO (Landing Page Conversion) would approach this step by step, then execute.”
  • “Review my current draft/plan and improve it using CRO (Landing Page Conversion). Call out assumptions.”
  • “Produce a checklist I can reuse whenever we run CRO (Landing Page Conversion) on similar work.”
06

Use cases and examples

  • Homepage conversion teardown
  • Signup form friction audit
  • Landing page hypothesis list
  • CTA/hierarchy recommendations
  • First-week trial of CRO (Landing Page Conversion) on a real marketing workflow
  • Document a reusable prompt template for CRO (Landing Page Conversion) for your team
07

Prerequisites

  • Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
  • Network access if the skill fetches guidelines or calls external tools
  • Project or brand context (CLAUDE.md / product notes) for better outputs
  • Permission to install third-party skills — audit SKILL.md and scripts first
08

Tips

  • Keep descriptions/triggers tight so CRO (Landing Page Conversion) fires only when relevant (avoids context tax).
  • Prefer one sharp job over a mega-skill that tries to do everything.
  • Pair with verification (tests, review, screenshots) before shipping outputs.
  • Re-audit installed skills monthly — unused skills still cost context every turn.
09

Sources