| name | form_fill |
| description | Fill structured web forms with PageState-based targeting, validation checks, and guarded submission. |
| official | true |
| version | 0.1.0 |
Form Fill Skill
Use this skill when the task requires entering data into a browser form, selecting options, and optionally submitting once the page state looks correct.
Goal
Complete forms reliably on dynamic sites by using stable backend_node_id targets, re-checking browser_get_page, and stopping before risky submissions when the content is ambiguous.
Preferred Tool Sequence
- Use
browser_get_page to identify editable fields and buttons.
- Use
browser_type with backend_node_id when present.
- Use
browser_click for checkboxes, radios, selects, and submit buttons.
- Use
browser_press_key for Enter or Tab only when it is clearly part of the intended flow.
- Use
browser_wait plus another browser_get_page after large DOM updates.
Guardrails
- Never submit if required field values are uncertain.
- If a field label is ambiguous, ask the user instead of guessing.
- Re-read
browser_get_page before submitting if the form changed after typing.
- If the page warns about login, captcha, or MFA, hand back control to the user.
- Mention exactly which fields were changed in the final response.
Minimal Demo Flow
browser_get_page to inspect inputs.
browser_type for each required field.
browser_click optional toggles or selectors.
browser_get_page again to confirm the final state.
browser_click submit only if the user explicitly asked to send or submit.