
Form Cro
- 26 installs
- 578 repo stars
- Updated July 15, 2026
- aitytech/agentkits-marketing
This is a copy of form-cro by coreyhaines31 - installs and ranking accrue to the original listing.
Form CRO is a Claude skill that optimizes non-signup forms to maximize completion rate while capturing needed data.
About
This skill optimizes non-signup forms such as lead-capture, contact, demo-request, application, and checkout forms to raise completion rates. It gives field-by-field guidance, layout and multi-step patterns, error handling, and submit-button copy. A developer uses it when a form has too much friction or low completion.
- Field-by-field optimization guidance with completion-rate cost estimates per field count
- Multi-step form and progressive-commitment patterns
- Error handling, submit-button copy, and trust/friction reduction
Form Cro by the numbers
- 26 all-time installs (skills.sh)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
form-cro capabilities & compatibility
- Capabilities
- page cro · onboarding cro · marketing psychology
- Use cases
- marketing · web design · ui design
- Pricing
- Free
What form-cro says it does
Your goal is to maximize form completion rates while capturing the data that matters.
Single column: Higher completion, mobile-friendly
npx skills add https://github.com/aitytech/agentkits-marketing --skill form-croAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 26 |
|---|---|
| repo stars | ★ 578 |
| Last updated | July 15, 2026 |
| Repository | aitytech/agentkits-marketing ↗ |
What it does
Increase completion rates on lead, contact, demo, and checkout forms by reducing friction.
Who is it for?
Reducing friction on lead-capture, contact, demo-request, and checkout forms to lift completion rates.
Skip if: Signup and registration forms, deferred to signup-flow-cro, and popups, deferred to popup-cro.
When should I use this skill?
Optimizing any non-signup form: lead capture, contact, demo request, application, survey, or checkout.
What you get
A shorter, single-column, well-validated form with higher completion and less field drop-off.
- form field audit
- layout and field-order recommendations
- error-message and validation rewrites
By the numbers
- 4-6 fields cut completion 10-25%
- 7+ fields cut completion 25-50%+
- 44px+ mobile tap targets
Files
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
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
1. Every Field Has a Cost
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?
2. Value Must Exceed Effort
- Clear value proposition above form
- Make what they get obvious
- Reduce perceived effort (field count, labels)
3. Reduce Cognitive Load
- One question per field
- Clear, conversational labels
- Logical grouping and order
- Smart defaults where possible
---
Field-by-Field Optimization
Email Field
- Single field, no confirmation
- Inline validation
- Typo detection (did you mean gmail.com?)
- Proper mobile keyboard
Name Fields
- Single "Name" vs. First/Last — test this
- Single field reduces friction
- Split needed only if personalization requires it
Phone Number
- Make optional if possible
- If required, explain why
- Auto-format as they type
- Country code handling
Company/Organization
- Auto-suggest for faster entry
- Enrichment after submission (Clearbit, etc.)
- Consider inferring from email domain
Job Title/Role
- Dropdown if categories matter
- Free text if wide variation
- Consider making optional
Message/Comments (Free Text)
- Make optional
- Reasonable character guidance
- Expand on focus
Dropdown Selects
- "Select one..." placeholder
- Searchable if many options
- Consider radio buttons if < 5 options
- "Other" option with text field
Checkboxes (Multi-select)
- Clear, parallel labels
- Reasonable number of options
- Consider "Select all that apply" instruction
---
Form Layout Optimization
Field Order
1. Start with easiest fields (name, email) 2. Build commitment before asking more 3. Sensitive fields last (phone, company size) 4. Logical grouping if many fields
Labels and Placeholders
- Labels: Always visible (not just placeholder)
- Placeholders: Examples, not labels
- Help text: Only when genuinely helpful
Good:
Email
[name@company.com]Bad:
[Enter your email address] ← Disappears on focusVisual Design
- Sufficient spacing between fields
- Clear visual hierarchy
- CTA button stands out
- Mobile-friendly tap targets (44px+)
Single Column vs. Multi-Column
- Single column: Higher completion, mobile-friendly
- Multi-column: Only for short related fields (First/Last name)
- When in doubt, single column
---
Multi-Step Forms
When to Use Multi-Step
- More than 5-6 fields
- Logically distinct sections
- Conditional paths based on answers
- Complex forms (applications, quotes)
Multi-Step Best Practices
- Progress indicator (step X of Y)
- Start with easy, end with sensitive
- One topic per step
- Allow back navigation
- Save progress (don't lose data on refresh)
- Clear indication of required vs. optional
Progressive Commitment Pattern
1. Low-friction start (just email) 2. More detail (name, company) 3. Qualifying questions 4. Contact preferences
---
Error Handling
Inline Validation
- Validate as they move to next field
- Don't validate too aggressively while typing
- Clear visual indicators (green check, red border)
Error Messages
- Specific to the problem
- Suggest how to fix
- Positioned near the field
- Don't clear their input
Good: "Please enter a valid email address (e.g., name@company.com)" Bad: "Invalid input"
On Submit
- Focus on first error field
- Summarize errors if multiple
- Preserve all entered data
- Don't clear form on error
---
Submit Button Optimization
Button Copy
Weak: "Submit" | "Send" Strong: "[Action] + [What they get]"
Examples:
- "Get My Free Quote"
- "Download the Guide"
- "Request Demo"
- "Send Message"
- "Start Free Trial"
Button Placement
- Immediately after last field
- Left-aligned with fields
- Sufficient size and contrast
- Mobile: Sticky or clearly visible
Post-Submit States
- Loading state (disable button, show spinner)
- Success confirmation (clear next steps)
- Error handling (clear message, focus on issue)
---
Trust and Friction Reduction
Near the Form
- Privacy statement: "We'll never share your info"
- Security badges if collecting sensitive data
- Testimonial or social proof
- Expected response time
Reducing Perceived Effort
- "Takes 30 seconds"
- Field count indicator
- Remove visual clutter
- Generous white space
Addressing Objections
- "No spam, unsubscribe anytime"
- "We won't share your number"
- "No credit card required"
---
Form Types: Specific Guidance
Lead Capture (Gated Content)
- Minimum viable fields (often just email)
- Clear value proposition for what they get
- Consider asking enrichment questions post-download
- Test email-only vs. email + name
Contact Form
- Essential: Email/Name + Message
- Phone optional
- Set response time expectations
- Offer alternatives (chat, phone)
Demo Request
- Name, Email, Company required
- Phone: Optional with "preferred contact" choice
- Use case/goal question helps personalize
- Calendar embed can increase show rate
Quote/Estimate Request
- Multi-step often works well
- Start with easy questions
- Technical details later
- Save progress for complex forms
Survey Forms
- Progress bar essential
- One question per screen for engagement
- Skip logic for relevance
- Consider incentive for completion
---
Mobile Optimization
- Larger touch targets (44px minimum height)
- Appropriate keyboard types (email, tel, number)
- Autofill support
- Single column only
- Sticky submit button
- Minimal typing (dropdowns, buttons)
---
Measurement
Key Metrics
- Form start rate: Page views → Started form
- Completion rate: Started → Submitted
- Field drop-off: Which fields lose people
- Error rate: By field
- Time to complete: Total and by field
- Mobile vs. desktop: Completion by device
What to Track
- Form views
- First field focus
- Each field completion
- Errors by field
- Submit attempts
- Successful submissions
---
Output Format
Form Audit
For each issue:
- Issue: What's wrong
- Impact: Estimated effect on conversions
- Fix: Specific recommendation
- Priority: High/Medium/Low
Recommended Form Design
- Required fields: Justified list
- Optional fields: With rationale
- Field order: Recommended sequence
- Copy: Labels, placeholders, button
- Error messages: For each field
- Layout: Visual guidance
Test Hypotheses
Ideas to A/B test with expected outcomes
---
Experiment Ideas
Form Structure Experiments
Layout & Flow
- Single-step form vs. multi-step with progress bar
- 1-column vs. 2-column field layout
- Form embedded on page vs. separate page
- Vertical vs. horizontal field alignment
- Form above fold vs. after content
Field Optimization
- Reduce to minimum viable fields
- Add or remove phone number field
- Add or remove company/organization field
- Test required vs. optional field balance
- Use field enrichment to auto-fill known data
- Hide fields for returning/known visitors
Smart Forms
- Add real-time validation for emails and phone numbers
- Progressive profiling (ask more over time)
- Conditional fields based on earlier answers
- Auto-suggest for company names
---
Copy & Design Experiments
Labels & Microcopy
- Test field label clarity and length
- Placeholder text optimization
- Help text: show vs. hide vs. on-hover
- Error message tone (friendly vs. direct)
CTAs & Buttons
- Button text variations ("Submit" vs. "Get My Quote" vs. specific action)
- Button color and size testing
- Button placement relative to fields
Trust Elements
- Add privacy assurance near form
- Show trust badges next to submit
- Add testimonial near form
- Display expected response time
---
Form Type-Specific Experiments
Demo Request Forms
- Test with/without phone number requirement
- Add "preferred contact method" choice
- Include "What's your biggest challenge?" question
- Test calendar embed vs. form submission
Lead Capture Forms
- Email-only vs. email + name
- Test value proposition messaging above form
- Gated vs. ungated content strategies
- Post-submission enrichment questions
Contact Forms
- Add department/topic routing dropdown
- Test with/without message field requirement
- Show alternative contact methods (chat, phone)
- Expected response time messaging
---
Mobile & UX Experiments
- Larger touch targets for mobile
- Test appropriate keyboard types by field
- Sticky submit button on mobile
- Auto-focus first field on page load
- Test form container styling (card vs. minimal)
---
Questions to Ask
If you need more context: 1. What's your current form completion rate? 2. Do you have field-level analytics? 3. What happens with the data after submission? 4. Which fields are actually used in follow-up? 5. Are there compliance/legal requirements? 6. What's the mobile vs. desktop split?
---
Related Skills
- signup-flow-cro: For account creation forms
- popup-cro: For forms inside popups/modals
- page-cro: For the page containing the form
- ab-test-setup: For testing form changes
Form Optimization Guide
Based on research from Formstack, HubSpot, Unbounce.
---
Form Conversion Benchmarks
By Form Type
| Form Type | Average CR | Good CR | Excellent CR |
|---|---|---|---|
| Contact Form | 3-5% | 5-8% | >10% |
| Lead Magnet | 15-25% | 25-35% | >40% |
| Newsletter | 1-3% | 3-5% | >8% |
| Demo Request | 5-10% | 10-15% | >20% |
| Free Trial | 8-15% | 15-25% | >30% |
| Checkout | 60-70% | 70-80% | >85% |
| Application | 20-30% | 30-40% | >50% |
Field Count Impact
| Fields | Conversion Rate |
|---|---|
| 1 field | 100% (baseline) |
| 2 fields | -3% |
| 3 fields | -5% |
| 4 fields | -10% |
| 5 fields | -15% |
| 6 fields | -20% |
| 7+ fields | -25%+ |
Rule of Thumb: Each additional field = 5-7% drop in conversions
---
Form Field Best Practices
Essential Fields Only
Ask yourself for each field: 1. Do we NEED this to complete the transaction? 2. Can we get this information later? 3. Does the value we provide justify asking for this?
Field Hierarchy (by friction)
| Field Type | Friction Level | When to Use |
|---|---|---|
| Low | Always (primary) | |
| Name | Low | Personalization needed |
| Company | Medium | B2B qualification |
| Phone | High | Sales follow-up required |
| Job Title | Medium | B2B segmentation |
| Address | Very High | Shipping/location required |
| Custom questions | Varies | Qualification critical |
Field Design Specifications
| Element | Specification |
|---|---|
| Input height | 44-48px (touch-friendly) |
| Label position | Above field (fastest to complete) |
| Label text | Clear, specific, no jargon |
| Placeholder text | Example format, not instructions |
| Error messages | Inline, specific, helpful |
| Required indicator | Asterisk (*) standard |
---
Multi-Step Form Optimization
When to Use Multi-Step
- YES: More than 4 fields required
- YES: Complex data collection
- YES: Qualification flow needed
- NO: Simple lead capture
- NO: Low-commitment actions
Multi-Step Performance
| Format | Completion Rate vs Single Step |
|---|---|
| 2-step | +15-20% |
| 3-step | +20-30% |
| 4+ steps | Diminishing returns |
Best Practices
1. Easy first step - Start with name/email 2. Progress indicator - Show steps remaining 3. Breadcrumb navigation - Allow going back 4. Auto-save - Don't lose partial data 5. Conditional logic - Skip irrelevant questions
Step Sequence (B2B Demo Form)
Step 1: Contact Info (email, name)
Step 2: Company Info (company, size, role)
Step 3: Needs (use case, timeline)---
Form Copy Optimization
Headline Formulas
| Formula | Example |
|---|---|
| Get [Benefit] | "Get Your Free Audit" |
| Start [Action] | "Start Your Free Trial" |
| [Action] + Timeline | "Book a Demo in 60 Seconds" |
| Question + Solution | "Need Help? Talk to an Expert" |
CTA Button Text
| Generic (Avoid) | Specific (Use) | Lift |
|---|---|---|
| Submit | Get My Free Report | +38% |
| Sign Up | Start My Trial | +90% |
| Download | Download the Guide | +15% |
| Contact | Schedule My Call | +28% |
Microcopy Elements
| Location | Purpose | Example |
|---|---|---|
| Below email field | Privacy reassurance | "We'll never share your email" |
| Below phone field | Usage explanation | "For appointment confirmation only" |
| Below CTA | Risk reversal | "Cancel anytime. No credit card." |
| Form header | Expectation setting | "Takes 30 seconds" |
---
Form Placement & Visibility
Above-Fold Impact
- Forms visible without scrolling: +20% conversion
- Sticky forms on scroll: +15% conversion
Placement Options
| Position | Best For | Considerations |
|---|---|---|
| Above fold | High-intent pages | Must be compelling |
| Sidebar | Content pages | May be ignored |
| Inline content | Blog CTAs | Contextual relevance |
| Footer | All pages | Low conversion, high volume |
| Exit intent | Recovery | Aggressive but effective |
| Slide-in | Time-based trigger | Less intrusive than popup |
Form Width Guidelines
| Context | Recommended Width |
|---|---|
| Sidebar | 300-350px |
| Inline | 500-600px |
| Full-width | Max 700px |
| Modal | 400-500px |
---
Form Validation
Real-Time Validation
- Validate on field blur (not on submit)
- Show success indicators (green checkmarks)
- Display errors immediately and clearly
Error Message Best Practices
| Bad | Good |
|---|---|
| "Invalid input" | "Please enter a valid email (e.g., name@company.com)" |
| "Required field" | "We need your email to send the report" |
| "Error" | "Phone numbers should be 10 digits" |
Input Formatting
- Auto-format phone numbers: (555) 123-4567
- Auto-capitalize names: john → John
- Email lowercase: JOHN@EXAMPLE.COM → john@example.com
- Accept multiple formats (dates, phones)
---
Trust Elements
Near-Form Trust Signals
| Element | Placement | Impact |
|---|---|---|
| Privacy statement | Below form | +5-10% |
| Security badges | Near submit | +5-8% |
| Testimonial quote | Beside form | +10-15% |
| Customer logos | Below form | +8-12% |
| Response time | Above form | +5-10% |
Privacy Copy Examples
- "Your information is secure and will never be shared."
- "We respect your privacy. Unsubscribe anytime."
- "🔒 256-bit SSL encryption"
- "Trusted by 10,000+ companies"
---
Mobile Form Optimization
Mobile-Specific Guidelines
| Element | Desktop | Mobile |
|---|---|---|
| Field height | 44px | 48px minimum |
| Touch targets | 44x44px | 48x48px |
| Font size | 14-16px | 16-18px |
| Field spacing | 12px | 16px+ |
| Submit button | Full or partial width | Full width |
Mobile Input Types
<input type="email"> <!-- Shows @ keyboard -->
<input type="tel"> <!-- Shows number pad -->
<input type="url"> <!-- Shows URL keyboard -->
<input inputmode="numeric"> <!-- Numbers only -->Mobile Autocomplete
<input autocomplete="email">
<input autocomplete="given-name">
<input autocomplete="tel">
<input autocomplete="organization">---
Form Analytics
Key Metrics to Track
| Metric | Formula | Target |
|---|---|---|
| View-to-Start | Started / Viewed | >50% |
| Start-to-Submit | Submitted / Started | >70% |
| Overall Conversion | Submitted / Viewed | >15% |
| Field Drop-off | Per-field abandonment | <10% |
| Error Rate | Errors / Submissions | <5% |
| Time to Complete | Avg seconds | <60s |
Drop-off Analysis
Track abandonment at each field to identify friction points:
- High drop-off at phone field → Make optional or explain why
- High drop-off at company field → Simplify or remove
- High drop-off at custom question → Rephrase or move later
---
A/B Test Ideas
High-Impact Tests
1. Field count - 3 fields vs 5 fields 2. Multi-step vs single-step - For 4+ fields 3. CTA text - "Submit" vs benefit-focused 4. Form position - Above fold vs inline 5. Progress indicator - With vs without 6. Social proof - Near form vs none 7. Form layout - Single column vs two column 8. Required fields - All required vs some optional
Testing Priority
| Change | Expected Lift | Effort |
|---|---|---|
| Reduce fields | +15-30% | Low |
| CTA copy | +10-40% | Low |
| Multi-step | +15-25% | Medium |
| Social proof | +10-20% | Low |
| Mobile optimization | +10-25% | Medium |
---
Lead Form Examples
Minimal Lead Magnet Form
[Email Address*]
[Download Now →]
"Join 5,000+ marketers. Unsubscribe anytime."B2B Demo Request (2-Step)
Step 1:
[Work Email*]
[Full Name*]
[Continue →]
Step 2:
[Company Name]
[Company Size ▼]
[What are you looking to solve? ▼]
[Book My Demo →]Contact Form
[Name*]
[Email*]
[How can we help? (textarea)]
[Send Message →]
"We typically respond within 4 hours"Related skills
FAQ
How many fields should a form have?
The skill treats 3 fields as baseline; 4-6 fields cut completion 10-25% and 7+ fields cut it 25-50%+.
Single or multi-column layout?
It recommends single column for higher completion and mobile-friendliness, reserving multi-column for short related fields.