Form Cro
Raise signup, demo, and contact form completion on landing pages by cutting fields and fixing labels before you ship traffic.
Overview
form-cro is an agent skill most often used in Validate (also Launch and Grow) that applies form conversion principles and field-by-field patterns to reduce friction on lead-capture flows.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill form-croWhat is this skill?
- Field-cost heuristics: 3-field baseline, 4–6 fields (~10–25% drop), 7+ fields (~25–50%+ drop)
- Principles: value must exceed effort, one question per field, conversational labels, logical order
- Per-field guidance for email, name, phone, company, role, free text, and dropdown selects
- Phone optional when possible; company enrichment after submit (Clearbit-style) instead of extra fields
- Inline email validation, typo hints, and mobile keyboard considerations
- 3-field baseline; 4–6 fields tied to ~10–25% completion reduction; 7+ fields to ~25–50%+ reduction
Adoption & trust: 522 installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your landing form asks for too much too soon, so completions tank even when traffic and offer quality are fine.
Who is it for?
Solo builders tuning waitlist, trial, contact, or demo forms on a validation landing page before scaling distribution.
Skip if: Products with no user-submitted forms, or teams that already locked a long enterprise intake form for compliance with no room to trim fields.
When should I use this skill?
You are designing or revising a lead, signup, demo, or contact form and want field-level CRO guidance.
What do I get? / Deliverables
You get a prioritized field audit—what to remove, defer, enrich later, or relabel—so the same page converts more signups without a full redesign.
- Field-by-field keep-cut-defer recommendations
- Ordered form layout and labeling suggestions
- Optional-field and enrichment strategy notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Landing and waitlist forms are the canonical CRO surface during validate, when you are proving demand before full build. Subphase landing matches lead-capture and early-access forms tied to validation experiments, not post-launch ops forms alone.
Where it fits
Trim a seven-field waitlist down to email plus optional company before running validation ads.
Align a campaign landing form with the value prop above the fold so paid clicks convert.
Shorten upgrade or newsletter forms that block repeat engagement.
How it compares
Use as a structured CRO checklist for forms instead of guessing field order in ad-hoc chat.
Common Questions / FAQ
Who is form-cro for?
Indie and solo builders shipping SaaS, content, or ecommerce pages who own signup and lead forms and want higher completion without hiring a CRO agency.
When should I use form-cro?
During Validate on landing and pricing capture pages, at Launch when forms sit on campaign landing URLs, and in Grow when you refine lifecycle signup or upgrade forms.
Is form-cro safe to install?
It is documentation-style guidance with no runtime hooks described here; review the Security Audits panel on this skill’s Prism page before installing from any third-party repo.
SKILL.md
READMESKILL.md - Form Cro
# form-cro reference ## 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 focus ``` ### Visual 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 clear