Browser Form Workflows
Apps & Automationbrowser-form-workflowsBrowser Form Workflows is an Agent Skill for apps & automation published in the agent0ai/agent-zero repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use for complex Agent Zero Browser form workflows involving selects, checkboxes, radios, file uploads, contenteditable fields, multi-step validation, or visually verified submission.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/agent0ai/agent-zero/blob/HEAD/plugins/_browser/skills/browser-form-workflows/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/browser-form-workflows, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Browser Forms
Use this skill as the form-specific extension of browser-automation. Load it after, or alongside, browser-automation when the page state may depend on selects, checkboxes, radios, file uploads, contenteditable fields, validation, or visual confirmation.
Start with browser:content to capture current refs, then use browser:detail on ambiguous fields before acting. Prefer ref-based form actions before coordinates.
Use select_option, set_checked, upload_file, type, type_submit, and submit for form interaction. Use coordinates only when no stable ref exists or the UI is intentionally canvas-like.
Use browser:screenshot plus vision_load when layout, visual validation, captcha-like UI, canvas content, or hidden state matters. Browser screenshots are not automatically loaded into model-visible history; no-path screenshots return chat-scoped artifact paths for vision_load.
Verify after submission with browser:content, browser:state, or another explicit browser:screenshot plus vision_load.
Do not guess file paths for upload. Verify that every path exists before calling upload_file.