Form Field Optimizer

What it does

Reviews each field on a form for whether it's actually necessary at this step, flags asks that could be deferred to a later interaction or dropped entirely, and reorders the remaining fields easiest-first to build momentum before harder questions. Also checks that labels and placeholder text clearly state what's expected, a common source of confusion-driven abandonment.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/form-field-optimizer/ (or ~/.claude/skills/form-field-optimizer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/form-field-optimizer/

OpenAI Codex

.codex/skills/form-field-optimizer/

Cursor

.cursor/skills/form-field-optimizer/ (or ~/.cursor/skills/form-field-optimizer/ globally)

Compatibility

Works with common form plugins (Contact Form 7, WPForms, Gravity Forms) the agent can read field configuration from.

The complete SKILL.md for this skill:

---
name: form-field-optimizer
description: Use when a user wants a form reviewed for length or friction, mentions form abandonment, or asks whether a signup or contact form is asking for too much.
---

# Form Field Optimizer

## When to use
A contact, signup, or checkout form seems to have more friction than needed, and the user wants the fields reviewed for necessity, order, and clarity.

## Procedure
1. List every field on the form along with its type (text, dropdown, checkbox) and whether it's marked required.
2. For each field, assess whether it's genuinely needed to complete the immediate action, or could be deferred to a follow-up email or a later step.
3. Flag fields that ask for information the site could reasonably infer or already has (e.g. asking for a country when payment already provides it).
4. Reorder the remaining fields easiest-first (name, email) before harder or more personal ones, to build momentum before the friction increases.
5. Check each label and placeholder for clarity, flag any that are ambiguous about format (date order, phone format) or purpose.
6. Present the trimmed and reordered field list with a one-line reason for each removal before applying changes to the live form.

## Guardrails
- Don't remove a field that feeds a required downstream process (billing, compliance, integration) without confirming it's safe to drop.
- Leave the final field list for the user to approve, since business requirements for "required" data aren't always visible from the form alone.