# Optimize Forms for More Completions

Long or confusing forms lose qualified submissions. This skill scores form health, identifies friction, and recommends measurable improvements while preserving useful data collection.

## Install

```bash
npx skillstore add sickn33/form-cro
```

## Metadata

- Status: approved
- Slug: sickn33-form-cro
- Skillstore revision: r2
- Version status: missing
- Tree hash: a04cf2f4c965660a7b0cf458816dd69669ad2710f31341e8df49d349a2e89bf5
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/form-cro
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-form-cro
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-form-cro/manifest

## Capabilities

- Calculates a 0-100 Form Health and Friction Index across six weighted categories.
- Classifies forms into health bands and prioritizes structural fixes when the score is below 55.
- Audits field necessity, order, labels, controls, validation, trust signals, and submission states.
- Recommends form copy, field requirements, error messages, layouts, and multi-step flows.
- Evaluates mobile usability through touch targets, keyboard types, autofill support, and responsive layout.
- Creates measurement plans and focused A/B test hypotheses with expected outcomes.

## Use Cases

- Improve Lead Capture: Audit a lead capture or demo request form, identify completion barriers, and create prioritized experiments.
- Prepare a Form Redesign: Review field order, labels, validation, mobile controls, and error recovery before a form redesign.
- Balance Data and Conversion: Balance qualification data needs against completion friction for quote, contact, or application forms.

## Prompt Templates

### Review a Simple Form

```
Review this [form type] for obvious friction. The goal is [business goal], and the fields are [field list]. Suggest the five highest-impact improvements.
```

### Score Form Health

```
Calculate the Form Health and Friction Index for this [form type]. Use [form details], [submission process], and [known constraints]. Explain each category score.
```

### Create a Prioritized Audit

```
Audit this [form type] using [field list], [completion rate], [drop-off data], and [device split]. Prioritize issues and recommend revised fields, copy, errors, and layout.
```

### Design an Experiment Program

```
Build a form optimization program for [business goal]. Use [analytics], [field usage], [qualification criteria], and [compliance constraints]. Provide the health score, redesign, measurement plan, and sequenced A/B tests.
```

## Limitations

- Does not cover signup or account registration forms.
- Recommendations depend on accurate business context, field usage, and performance data.
- Does not implement analytics, redesign forms, or run experiments.
- Legal, privacy, and compliance requirements need qualified human review.

## Best Practices

- Provide the form goal, post-submission process, required qualification data, and legal constraints.
- Share current completion rate, field-level drop-off, error rates, and device split when available.
- Test one focused hypothesis at a time and measure both completion quality and submission volume.

## Anti Patterns

- Do not remove required fields without confirming operational, legal, and qualification needs.
- Do not optimize signup or account registration flows with this skill.
- Do not combine multiple unrelated changes in one experiment.

## Security Audit

- Audited at: 2026-07-23T22:24:49.914\+00:00
- Summary: All four static findings are false positives from ordinary form usability guidance. The skill contains no executable code, system reconnaissance, keylogging instructions, prompt injection, or data exfiltration intent. No semantic security findings were identified.

## Stats

- Views: 96
- Downloads: 12
- Favorites: 0
- Popularity score: 0