form-cro
Form optimization for lead capture, contact, demo request, application, and checkout forms. Covers field-cost analysis, multi-step form design, validation UX, mobile optimization, and A/B testing frameworks.
Install / Use
npx skills add borghei/Claude-Skills --skill form-croInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of form-cro
form-cro scores 91/100 on our quality scale, 1130th of 4,702 Development & Engineering skills we index (top 25%).
Its SKILL.md is 22 KB long, well organised into 51 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so form-cro is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
form-cro compared with similar skills
All 4 of these similar skills score higher than form-cro; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| form-cro (this skill)by borghei | 91 | 817 | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install form-cro?
- Run
npx skills add borghei/Claude-Skills --skill form-cro. The install tabs above show the steps for each supported agent. - Which AI agents does form-cro work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is form-cro safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is form-cro still maintained?
- The repository was last updated about 2 months ago, so form-cro is actively maintained.
Skill content
View source on GitHubname: form-cro description: > Form optimization for lead capture, contact, demo request, application, and checkout forms. Covers field-cost analysis, multi-step form design, validation UX, mobile optimization, and A/B testing frameworks. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: [cro, forms, lead-capture, conversion-optimization, ux]
Form CRO
Production-grade form optimization framework covering field-cost analysis, layout engineering, multi-step form architecture, validation UX patterns, mobile-specific optimization, and structured A/B test design. Applicable to lead capture, contact, demo request, application, survey, and checkout forms. For signup/registration flows, use signup-flow-cro.
Table of Contents
- Initial Assessment
- Field-Cost Analysis Framework
- Multi-Step vs Single-Step Decision
- Field Design Patterns
- Validation UX
- CTA and Submit Button Optimization
- Mobile Form Optimization
- Trust and Context Elements
- Form Type Playbooks
- A/B Test Framework
- Metrics and Measurement
- Output Artifacts
- Related Skills
Clarify First
Before optimizing the form, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Form type — lead capture, contact, demo, application, or checkout (sets the optimal field count and playbook)
- [ ] Current fields + which are used in follow-up — reveals which fields to cut or enrich (the core of field-cost analysis)
- [ ] Current completion rate + where users abandon — baseline and the specific friction point to target
- [ ] Compliance requirements — GDPR/HIPAA fields that cannot be removed (constrains the field reduction)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit.
Initial Assessment
Required Context
| Question | Why It Matters | |----------|---------------| | What type of form? (lead capture, contact, demo, application, checkout) | Different types have different optimal field counts | | How many fields currently? | Establishes baseline friction level | | What is the current completion rate? | Benchmark for improvement | | Where do users abandon? (if field-level analytics exist) | Identifies the specific friction point | | Mobile vs desktop split? | Mobile forms need separate optimization | | What happens with submitted data? | Determines which fields are truly necessary | | Which fields are actually used in follow-up? | Often reveals 30-50% of fields are never used | | Any compliance requirements? (GDPR, HIPAA) | Constrains what can be removed |
Field-Cost Analysis Framework
Every field has a cost measured in abandonment. The question is not "what data would be nice to have" but "what data is worth the conversion loss."
Field Cost Matrix
| Field Type | Estimated Abandonment Cost | Justification Threshold | |-----------|---------------------------|------------------------| | Email | Baseline (near zero for gated content) | Always justified for lead forms | | First name | +2-3% drop | Justified if personalization drives follow-up | | Last name | +2-3% drop | Rarely justified for first touch | | Phone number | +5-10% drop | Only if sales will call within 24 hours | | Company name | +3-5% drop | Justified for B2B qualification | | Company size | +3-5% drop | Justified only if routing decisions depend on it | | Job title | +3-5% drop | Can often be enriched post-submission | | Industry | +2-3% drop | Can often be enriched post-submission | | Message/textarea | +5-8% drop | Justified for contact forms, not for lead capture | | Budget | +8-12% drop | Only justified for high-intent demo/sales forms | | Custom question | +3-5% per question | Must directly affect lead routing or qualification |
The Enrichment Test
Before including any field, ask: Can this be enriched after submission?
| Field | Enrichable? | Method | Keep in Form? | |-------|------------|--------|---------------| | Company name | Yes (from email domain) | Clearbit, Apollo, manual lookup | Remove | | Company size | Yes (from company name) | Enrichment API | Remove | | Industry | Yes (from company name) | Enrichment API | Remove | | Job title | Partially (from LinkedIn) | Manual enrichment | Remove unless critical for routing | | Phone number | No | Must be provided | Keep only if sales calls immediately | | Budget | No | Must be stated | Keep only for high-intent forms |
Recommended Field Sets by Form Type
| Form Type | Minimum Fields | Optimal Fields | Maximum Fields | |-----------|---------------|----------------|----------------| | Newsletter signup | Email | Email | Email + First name | | Content download | Email | Email + First name | Email + Name + Company | | Contact form | Email + Message | Email + Name + Message | Email + Name + Subject + Message | | Demo request | Email + Company | Email + Name + Company + Role | + Phone + Use case + Team size | | Application form | Varies by requirement | -- | All required fields (justified individually) |
Multi-Step vs Single-Step Decision
Decision Criteria
| Factor | Single-Step | Multi-Step | |--------|------------|------------| | Total fields | < 5 fields | > 5 fields | | Field complexity | Simple text inputs | Mix of dropdowns, checkboxes, conditional fields | | User motivation | Low-commitment (newsletter, content) | High-commitment (demo, application) | | Qualification need | No routing needed | Different paths based on answers | | Mobile proportion | < 30% mobile | > 50% mobile |
Multi-Step Best Practices
Step structure:
- Step 1: Easiest fields (email, name) -- lowest friction to start
- Step 2: Qualifying information (company, role, use case)
- Step 3: Specific details (budget, timeline, message)
Progress indication:
- Show progress bar with step count ("Step 2 of 3")
- Show completion percentage
- Label each step with what it covers ("Your Details", "Company Info", "Project Details")
Psychological commitment:
- Once a user completes Step 1, they are 40-60% more likely to complete the form (sunk cost effect)
- Capture the email in Step 1 so you can follow up even if they abandon later
Back navigation:
- Always allow users to go back to previous steps
- Preserve entered data when navigating between steps
- Never reset the form on back navigation
Field Design Patterns
Field Labels
| Pattern | When to Use | Example | |---------|-------------|---------| | Above-field labels | Default for most forms | Label sits above the input | | Inline labels (floating) | Space-constrained layouts | Label moves from inside to above on focus | | Left-aligned labels | Wide desktop forms | Label to the left of field | | Placeholder-only labels | Never | Disappears on input, accessibility failure |
Field Types
| Data Needed | Best Input Type | Avoid |
|------------|-----------------|-------|
| Email | type="email" with validation | Plain text input |
| Phone | type="tel" with format mask | Plain text input |
| Country | Searchable dropdown | Long static dropdown |
| Company size | Button group (1-10, 11-50, 51-200, 200+) | Free text input |
| Interest/topic | Checkbox group (max 6 options) | Multi-select dropdown |
| Message | Textarea (3-4 rows visible) | Single-line text input |
| Date | Native date picker | Three separate dropdowns |
Conditional Fields
Show additional fields based on earlier answers. This reduces visible complexity while capturing necessary data.
Example: "What is your primary goal?" dropdown shows "Budget range" only if they select "Ready to buy" or "Evaluating solutions."
Rules:
- Conditional fields appear with smooth animation (not instant jump)
- Only 1-2 conditional fields per trigger
- Conditional fields are never required (the trigger answer may change)
Validation UX
Real-Time vs Submit-Time Validation
| Validation Type | When to Use | |----------------|-------------| | Real-time (on blur) | Email format, phone format, required fields | | On submit | Complex validation, server-side checks | | Inline suggestions | Company name auto-complete, address lookup |
Error Message Design
| Pattern | Good | Bad | |---------|------|-----| | Position | Below the field, in context | Top of form, disconnected | | Tone | "Please enter a valid email address" | "Error: Invalid input" | | Specificity | "Phone must include area code" | "Invalid phone number" | | Color | Red text + red border on field | Red banner at top of page | | Icon | Error icon next to message | No visual indicator |
Success Indicators
- Green checkmark on valid fields (especially email and phone)
- Positive microcopy: "Looks good!" on valid email
- Do NOT flash green/red on every keystroke -- validate on blur (when user leaves the field)
CTA and Submit Button Optimization
Button Copy Framework
| Form Type | Weak Copy | Strong Copy | Strongest Copy | |-----------|-----------|-------------|----------------| | Content download | Submit | Download Guide | Get My Free Guide | | Demo request | Submit | Request Demo | Schedule My Demo | | Contact form | Send | Send Message | Get in Touch | | Newsletter | Subscribe | Join Newsletter | Get Weekly Tips | | Free trial | Sign Up | Start Free Trial | Start Building Free |
Rules:
- Use first person ("Get My..." not "Get Your...")
- Specify what they get, not what they do
- Include "Free" when applicable
- Keep under 5 words
Button Design
| Element | Best Practice | |---------|---------------| | Color | High contrast against form background, consistent with brand CTA color | | Size | Full-width on mobile, min 44px height for touch targets | | Position | Immediately below last field, no gap | | Loading state | Show spinner + "Sending..." to prevent double-submit | | Disabled state | Disabled until required fields are valid (with clear visual distinction) |
Mobile Form Optimization
Mobile-Specific Rules
| Rule | Implementation |
|------|---------------|
| Touch targets | Minimum 44x44px for all interactive elements |
| Keyboard types | type="email" for email, type="tel" for phone, type="number" for numeric |
| Auto-focus | Focus first field on page load (with keyboard open) |
| Sticky submit | Pin submit button to bottom of viewport on long forms |
| Input spacing | Minimum 8px between fields to prevent mis-taps |
| Dropdown alternatives | Use button groups or radio buttons instead of dropdowns on mobile |
| Auto-fill | Support browser auto-fill for standard fields (name, email, phone, address) |
Mobile vs Desktop Form Differences
| Aspect | Desktop | Mobile | |--------|---------|--------| | Layout | 1 or 2 columns | Always 1 column | | Field count | Up to 8 | Max 5 per step | | Dropdown | Standard dropdown | Bottom sheet or full-screen picker | | Help text | Hover tooltips | Always-visible inline text | | Validation | On blur | On blur + on submit summary |
Trust and Context Elements
Trust Signals Near Forms
| Signal | Placement | Impact | |--------|-----------|--------| | Privacy assurance | Below submit button | "We'll never share your email" | | Security badges | Next to form container | SSL, SOC2, GDPR compliance | | Testimonial | Adjacent to form | Social proof reduces hesitation | | Response time | Below submit button | "We respond within 2 hours" | | Subscriber/user count | Above or within form | "Join 10,000+ subscribers" |
Context Reinforcement
| Element | Purpose | Example | |------
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
