browser-form-automation

Browser Form Automation

Use When

• The user asks you to configure or verify an authenticated web console, admin page, or form.
• You are editing origins, redirect URIs, secrets, settings, or multi-field config in Chrome, Browser, or another browser automation surface.
• A click/type attempt misses focus, typing lands nowhere, cmd+a selects the page, a console or side panel steals focus, or coordinates have changed after scrolling.

Near misses:

• Read-only inspection or screenshots: use the Browser/Chrome skill directly.
• A single visible button/link with no text entry: a coordinate or vision click is fine, then check state.
• A provider API or secret-retrieval task: use local-secret-retrieval first; use this skill only when you must operate the web UI.

Procedure

1. Start with the relevant Browser/Chrome skill and its runtime docs. Prefer the browser's semantic API: Playwright locators, accessible labels, form_input, or JavaScript DOM writes with dispatched input/change events.
2. Map the form before changing it: list visible inputs/buttons with labels, placeholders, current values, disabled state, and the current URL/account/project. Confirm it is the expected account/project before writing.
3. Use coordinates only to expose or open a control. Do not use stale x/y clicks as the main data-entry method for text fields.
4. After any missed-focus signal, stop coordinate typing immediately. Switch to locator/DOM entry before retrying. A second blind click/type sequence without new DOM evidence is the failure pattern.
5. When using DOM writes, mimic user input enough for frameworks: set the value through the native setter when needed, dispatch input and change, then read the field value back.
6. Verify the result from the page's own state before saving/submitting: current input values, selected options, validation messages, success toast, or saved detail page.
7. If saving transmits secrets, credentials, or external state and the user's request did not already authorize that exact destination/action, follow browser safety confirmation. Otherwise finish the authorized flow.