AI Agent Hub
Back to skills
Browser Automation Script Generator icon

Browser Automation Script Generator

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_f28fdad8/oc-browser-auto.

About this skill

Problem

Browser automation often fails less because the task is impossible and more because login flows, navigation, form filling, and scraping keep requiring manual selector tweaks, waits, and error handling.
Browser Automation Script Generator turns a described task into a runnable Playwright Python script: provide a target URL, steps, fields, or pagination rules, and it outputs local .py code. It does not launch a browser or execute page actions by itself; it generates code that you run locally for tests, pipelines, or ad-hoc automation.

How It Works

  • Login scripts: provide url, login steps, and session-save preference to generate browser startup, page opening, step-by-step actions, save_session, retries, and screenshot verification.
  • Navigation scripts: provide jumps and click targets to generate wait strategies, CSS/XPath locators, action intervals, retries, and logging.
  • Form scripts: provide fields and submit selector to generate field-by-field input, dropdown/radio/checkbox handling, file upload support, submission, and result checks.
  • Scraping scripts: provide target fields, pagination rules, and output format to generate extraction, pagination, de-duplication, and JSON/CSV export.

The workflow is: define the inputs such as URL, steps, selectors, fields, or output format; the generator assembles Playwright code with logs, waits, retries, and screenshot points for easier debugging.

Limits

Generated scripts still require a local Playwright installation, and real results depend on site structure, selector stability, and login or captcha behavior. It fits repetitive page actions, form automation, and structured data extraction; for frequent redesigns, complex human verification, or heavy anti-bot controls, manual selector and error-handling work is still needed.

Use Cases

  • QA engineers reproduce account login in CI and generate a Playwright script with retries and screenshots.
  • Ops engineers navigate multi-page admin menus and generate a script with waits, locators, and logging.
  • Operations staff batch-fill customer details into a public form with dropdowns, radios, and file upload.
  • Analysts scrape product prices and inventory, then generate pagination, de-duplication, and CSV export.

Best For

  • Web test engineers who want login, navigation, and screenshot checks as runnable Playwright code.
  • Operations staff filling backend forms who need automatic field entry, dropdown handling, and submit checks.
  • Data analysts extracting site lists who want pagination and JSON or CSV export generated for them.
  • Automation developers needing page-action code with waits, retries, and logging.