Agent skill · marketing growth · alirezarezvani
form-cro
Use when a lead, contact, demo or checkout form is underperforming or being designed, before changing fields. Scores field friction with form_field_analyzer.py. Signup forms: signup-flow-cro.
Why this skill is useful
Provides domain-specific knowledge on form optimization strategies and includes a script for analyzing form fields that the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 5k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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 Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. 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 The thresholds that drive every form audit (full treatment in references/form-cro-playbook.md): Field count: every added field costs conversions. Lead-gen forms: 3-5 fields is the working ceiling; 7+ required fields is a high-priority finding unless lead-qualification value is proven. Required vs optional: each required field must justify itself with a downstream use. "Nice for sales" is not a justification — make it optional or cut it. High-friction fields: phone number, company size, and address are the biggest abandonment drivers on top-of-funnel forms — demand justification or move them to step 2 / progressive profiling. Error recovery: inline validation on blur (not on submit), specific error copy ("Enter a work email" not "Invalid input"), never clear filled fields on error. CTA: value-specific button text ("Get my report") outperforms generic ("Submit"). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/form-cro--91ce1e