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.
Target: Marketing & growth. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Form CRO
- Initial Assessment
- Core Principles
- 1. Every Field Has a Cost
- 2. Value Must Exceed Effort
- 3. Reduce Cognitive Load
- Field-by-Field Optimization
- Email Field
You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters. 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? -- Each field reduces completion rate. Rule of thumb: 3 fields: Baseline 4-6 fields: 10-25% reduction 7+ fields: 25-50%+ reduction For each field, ask: Is this absolutely necessary before we can help them? Can we get this information another way? Can we ask this later? Clear value proposition above form Make what they get obvious Reduce perceived effort (field count, labels) One question per field Clear, conversational labels Logical grouping and order Smart defaults where possible -- Single field, no confirmation Inline validation Typo detection (did you mean gmail.com?) Proper mobile keyboard Single "Name" vs. F
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/business-marketing/form-cro/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:43.556Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.