Marketing CROFormsConversion

Form CRO

Optimize any form for better completion rates and conversions.

$skillfish add ~skills/form-cro

Real Conversations

See how the Form CRO skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

Our demo request form has a 23% completion rate — meaning 77% of people who start filling it out abandon it. The form has 8 fields: name, company, email, phone, company size, role, use case, and 'how did you hear about us'. What should I cut and how do I restructure it?

Agent

A 23% completion rate on an 8-field demo form is about right — that form is asking for too much, too early. Industry benchmark for demo request forms is 35–45% completion. Here's the fix:

Fields to cut immediately:

  • Phone — the #1 form abandonment trigger for B2B SaaS. Remove unless your sales team genuinely cold-calls from it (they shouldn't)
  • "How did you hear about us" — valuable for attribution but collect this after the demo, not as a barrier to booking one
  • Use case — replace with a dropdown in the post-form qualification step

Minimum viable demo form (4 fields):

  1. First name
  2. Work email
  3. Company name
  4. Team size (dropdown: 1–10 / 11–50 / 51–200 / 200+)

Why work email instead of email: Labeling it "work email" increases form completion and automatically filters personal addresses — which means cleaner leads for sales.

What to add instead of cutting:

  • Inline validation — show green checkmarks as fields complete, not red errors after submit
  • Progress signal — "Takes 60 seconds" near the submit button reduces abandonment
  • Social proof near the form — "Join 500+ engineering teams" with logos

Alternative: 2-step form Step 1: Just email. Step 2: Remaining 3 fields. This approach captures partial completions (email is the valuable field) and typically increases full completion rate by 20–30% over single-step.

Expected outcome: Moving from 8 to 4 fields typically increases completion rate from ~23% to 45–55%.

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best
Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2
Good
Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only
32K+ Skill + conversation
100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Form CRO?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.

$skillfish add ~skills/form-cro
← Browse all 169 skills