autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
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
$ npx -y skills add MaximoCorrea1/ultra-powers --skill cro --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/croContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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.0
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
**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)
---
Analyze the page across these dimensions, in order of impact:
**Check for:**
**Common issues:**
**Evaluate:**
**Strong headline patterns:**
**Primary CTA assessment:**
**CTA hierarchy:**
**Check:**
**Types to look for:**
**Placement:** Near CTAs and after benefit claims
**Common objections to address:**
**Address through:** FAQ sections, guarantees, comparison content, process transparency
**Look for:**
---
Structure your recommendations as:
Easy changes with likely immediate impact.
Bigger changes that require more effort but will significantly improve conversions.
Hypotheses worth A/B testing rather than assuming.
For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.
---
---
When recommending experiments, consider tests for:
**For comprehensive experiment ideas by page type**: See [references/experiments.md](references/experiments.md)
---
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?
---
---
For detailed form CRO guidance — including field optimization, multi-step forms,
The everything-Flow for building, shipping, and growing software — 40 hand-picked skills from 7 open-source suites, behind one FLOW.md router that fires the right skill on intent (and disambiguates the overlaps), with mandatory routing that survives context
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.…
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and…
Document a recently solved problem to compound your team's knowledge
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue…
Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI…