# Fewer Fields

> Shorten a web form that is not a sign-up form - lead capture, contact, demo request, quote, application, survey or
> checkout. Paste the form's HTML or a plain list of its fields. The page reads every field, prints the form as a
> receipt of what each field costs in rough seconds, lints it against the form-optimization rules and rebuilds it with
> the fixes it can make alone. A metered run decides, field by field, whether to keep it, make it optional, ask it
> after they submit, merge it or drop it; writes the labels, error messages, order (and steps for a long form), the
> button and the line under it, and A/B tests. The page checks the plan against its own rules and gives the shorter
> form back as plain HTML. Nothing is sent anywhere from the page. Built on the SkillSafe skill @coreyhaines31/form-cro.

https://fewer-fields.skillsafe.ai/

## What is free
- Reading HTML without running it: inputs, dropdowns with their options, text boxes, radio groups and tick-box groups (folded into one question each), the label tied to each (label element, wrapping label, aria-label, fieldset legend, short text just before it - otherwise the placeholder or the code name), required marks (the attribute, aria-required or an asterisk), hidden fields (counted, not planned), a CAPTCHA and the submit button.
- Reading a plain list: one field per line; a line may carry `required` or `optional`, a type (email, phone, dropdown, radio, checkbox, textarea, date, file...) and options split by `/` or commas; `button: ...` sets the button. With no marks at all, every field is read as required.
- Per field: a kind (email, name, phone, company, job title, company size, budget, address parts, country, message, consent...), a rough number of seconds to answer (halved when optional), and the findings: placeholder-only or missing labels, a repeated email, an email or phone input without the right type, missing autocomplete, a split name, a required phone or message, dropdowns of 2-4 or more than 15 options, a dropdown that opens on a real answer, a pre-ticked box, a password; and for the form: sensitive fields first, everything required, more than six fields, a CAPTCHA, a weak button.
- The band from the source skill's rule of thumb: 3 fields or fewer the baseline, 4 to 6 about 10 to 25% fewer finish, 7 or more about 25 to 50% or more. A guide, not a measurement.
- "Team uses it" marks per field, the page's own fixes rebuilt as a live form, a CSV of every field, and four samples that replay saved trims at no cost.

## The metered task
One task, `trim`, on gpt-terra, metered per run. Input string fields: `task`, `kind` (lead, contact, demo, quote, application, survey, checkout, other), `goal`, `fields` (one line per field, `q1.` ... up to 30), `facts` (counts, the rule of thumb and every finding) and `button`. The reply is one JSON object: `verdict` (`lean`, `trim` or `steps`), `fields` (each `field` id, `action` - keep, optional, later, merge or drop - `into`, `label`, `error`, `why`), `order`, `steps`, `button`, `trust`, `tests` and `note`.

The page checks that the verdict follows from the plan (steps when more than six fields stay, trim when any is cut, lean otherwise), that the order and steps hold exactly the staying fields, that no field the team uses is dropped, that an email or phone stays required, that only parts of one answer merge, that the button is not a bare Submit or Send, and that every number the reply writes comes from the form.

## Links
- API tutorial: https://fewer-fields.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@coreyhaines31/form-cro