domains / families / marketing / form-cro

form-cro

combined

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro. When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

When to use

• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The LeoYeAI copies (openclaw-marketing-skills and openclaw-master-skills) are nearly identical, providing a detailed, step-by-step guide for form optimization (field-by-field, layout, error handling). The sickn33 copy (agentic-awesome-skills) introduces a distinct, mandatory diagnostic framework (the 'Form Health & Friction Index') with specific scoring weights and health bands that the LeoYeAI copies lack. Conversely, the LeoYeAI copies contain specific implementation details (e.g., 44px tap targets, specific button placement rules, progressive commitment patterns) that are absent or less detailed in the sickn33 copy. Because the sickn33 copy adds a unique diagnostic phase and the LeoYeAI copies add unique implementation constraints, crowning one would hide a real alternative approach (diagnostic-first vs. implementation-first).