form-cro
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
npx skills add alirezarezvani/claude-skills --skill form-cro --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Form CRO You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters. ## Initial Assessment **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, 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. **Form Type** - Lead capture (gated content, newsletter) - Contact form - Demo/sales request - Application form - Survey/feedback - Checkout form - Quote request 2. **Current State** - How many fields? - What's the current completion rate? - Mobile vs. desktop split? - Where do users abandon? 3. **Business Context** - What happens with form submissions? - Which fields are actually used in follow-up? - Are there compliance/legal requirements? --- ## Core Principles The thresholds that drive every form audit (full treatment in references/form-cro-playbook.md): - **Field count**: every added field costs conversions. Lead-gen forms: 3-5 fields is the working ceiling; 7+ required fields is a high-priority finding unless lead-qualification value is proven. - **Require
- Initial Assessment
- Core Principles
- Tools
- Output Format
- Form Audit
- Recommended Form Design
- Test Hypotheses
- Experiment Ideas
- Form Structure Experiments
- Copy & Design Experiments
- Form Type-Specific Experiments
- Mobile & UX Experiments
- Task-Specific Questions
- Related Skills
What does the form-cro skill do?
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill form-cro --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.