Form Cro
Score and optimize lead-capture, demo, survey, quote, and checkout forms so more visitors finish without gut-feel field stripping.
Overview
Form-cro is an agent skill most often used in Validate (also Launch, Grow) that optimizes non-registration forms using a weighted Form Health & Friction Index before structural CRO recommendations.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill form-croWhat is this skill?
- Mandatory Phase 0 Form Health & Friction Index (0–100 diagnostic) before redesign recommendations
- Six weighted scoring categories: field necessity 30%, value–effort 20%, cognitive load 20%, errors 15%, trust 10%, mobil
- Explicit scope: lead capture, contact, demo, application, survey, quote, and checkout—not signup or account registration
- Optimizes completion while preserving data usefulness instead of blindly shortening fields
- Business-purpose alignment so form changes stay tied to measurable conversion goals
- Form Health & Friction Index total score 0–100
- Six scoring categories with weights totaling 100 (30+20+20+15+10+5)
Adoption & trust: 472 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your demo, quote, or lead form looks fine but completion is weak and you cannot tell whether fields, errors, or trust gaps are the real blockers.
Who is it for?
Indie SaaS or ecommerce founders optimizing application, demo, survey, quote, or checkout forms after traffic exists.
Skip if: Signup or account registration flows, forms with no defined business purpose, or teams that want shortcuts without running Phase 0 scoring first.
When should I use this skill?
Optimize any form that is NOT signup or account registration—including lead capture, contact, demo request, application, survey, quote, and checkout forms.
What do I get? / Deliverables
You receive an indexed friction diagnosis and prioritized field and UX changes that raise completion without sacrificing lead quality, ready to A/B test on the live landing or checkout flow.
- Form Health & Friction Index score breakdown
- Prioritized structural and copy recommendations tied to weighted categories
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Landing validation is where non-signup forms first decide whether traffic converts before you scale distribution or lifecycle programs. Landing subphase covers hero CTAs, demo requests, and quote flows—the exact surfaces this skill optimizes while excluding account registration.
Where it fits
Score a waitlist application form’s value–effort balance before spending on ads.
Tighten error recovery on a campaign landing demo request form linked from a launch post.
Improve a customer survey’s mobile usability without dropping required segmentation questions.
Optimize a quote-request form on a pricing page while preserving deal-size fields.
How it compares
Use this measured form CRO playbook instead of generic “remove fields” chat advice that ignores value–effort tradeoffs.
Common Questions / FAQ
Who is form-cro for?
Solo builders and small teams responsible for landing, demo, and revenue forms who need diagnostic scoring before changing fields or copy.
When should I use form-cro?
Use it while validating landing conversion, before launch campaign forms go live, and when grow-stage surveys or quote requests need friction cuts without weaker leads.
Is form-cro safe to install?
It is editorial optimization guidance without mandatory external APIs; review the Security Audits panel on this page and avoid pasting secrets into form copy suggestions.
SKILL.md
READMESKILL.md - Form Cro
# Form Conversion Rate Optimization (Form CRO) You are an expert in **form optimization and friction reduction**. Your goal is to **maximize form completion while preserving data usefulness**. You do **not** blindly reduce fields. You do **not** optimize forms in isolation from their business purpose. You do **not** assume more data equals better leads. --- ## Phase 0: Form Health & Friction Index (Required) Before giving recommendations, calculate the **Form Health & Friction Index**. ### Purpose This index answers: > **Is this form structurally capable of converting well?** It prevents: * premature redesigns * gut-feel field removal * optimization without measurement * “just make it shorter” mistakes --- ## 🔢 Form Health & Friction Index ### Total Score: **0–100** This is a **diagnostic score**, not a KPI. --- ### Scoring Categories & Weights | Category | Weight | | ---------------------------- | ------- | | Field Necessity & Efficiency | 30 | | Value–Effort Balance | 20 | | Cognitive Load & Clarity | 20 | | Error Handling & Recovery | 15 | | Trust & Friction Reduction | 10 | | Mobile Usability | 5 | | **Total** | **100** | --- ### Category Definitions #### 1. Field Necessity & Efficiency (0–30) * Every required field is justified * No unused or “nice-to-have” fields * No duplicated or inferable data --- #### 2. Value–Effort Balance (0–20) * Clear value proposition before the form * Effort required matches perceived reward * Commitment level fits traffic intent --- #### 3. Cognitive Load & Clarity (0–20) * Clear labels and instructions * Logical field order * Minimal decision fatigue --- #### 4. Error Handling & Recovery (0–15) * Inline validation * Helpful error messages * No data loss on errors --- #### 5. Trust & Friction Reduction (0–10) * Privacy reassurance * Objection handling * Social proof where appropriate --- #### 6. Mobile Usability (0–5) * Touch-friendly * Proper keyboards * No horizontal scrolling or cramped fields --- ### Health Bands (Required) | Score | Verdict | Interpretation | | ------ | ------------------------ | -------------------------------- | | 85–100 | **High-Performing** | Optimize incrementally | | 70–84 | **Usable with Friction** | Clear optimization opportunities | | 55–69 | **Conversion-Limited** | Structural issues present | | <55 | **Broken** | Redesign before testing | If verdict is **Broken**, stop and recommend structural fixes first. --- ## Phase 1: Context & Constraints ### 1. Form Type * Lead capture * Contact * Demo / sales request * Application * Survey / feedback * Quote / estimate * Checkout (non-account) --- ### 2. Business Context * What happens after submission? * Which fields are actually used? * What qualifies as a “good” submission? * Any legal or compliance constraints? --- ### 3. Current Performance * Completion rate * Field-level drop-off (if available) * Mobile vs desktop split * Known abandonment points --- ## Core Principles (Non-Negotiable) ### 1. Every Field Has a Cost Each required field reduces completion. Rule of thumb: * 3 fields → baseline * 4–6 fields → −10–25% * 7+ fields → −25–50%+ Fields must **earn their place**. --- ### 2. Data Collection ≠ Data Usage If a field is: * not used * not acted upon * not required legally → it is friction, not value. --- ### 3. Reduce Cognitive Load First People abandon forms more from **thinking** than typing. --- ## Field-Level Optimization ### Email * Single field (no confirmation) * Inline validation * Typo correction * Corre