browser-automation
FeaturedRoute browser automation tasks to specialized Rome apps first, then use OpenCLI help discovery when no specialized Rome app is available.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- rome-os
- Repository
- rome-os/rome
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
browser-automation
Unified automation entry point. Covers browser automation (Playwright) and Windows desktop application automation (OpenReverse). Browser scenarios: open web pages, click, fill forms, scrape, take screenshots, automated logins, pentest page interactions. Desktop scenarios: operate GUI tools such as IDA/x64dbg, Windows UI Automation, vision-driven interaction, desktop application network packet capture. Trigger keywords: browser automation, desktop automation, open web page, form filling, scraping, screenshots, automated login, Playwright, agent-browser, headless, OpenReverse, UIA, CUA, desktop operations, Windows automation.
browser-act
Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it by name, includes or asks to run a browser-act CLI command (e.g., browser-act browser list), or to: fetch, view, or extract rendered content from URLs, access pages requiring JavaScript, handle verification prompts, maintain authenticated sessions, fill forms and click through workflows, type, select, upload, take screenshots, capture XHR/fetch/HAR responses, open multiple URLs in parallel, extract content that loads on scroll or click, visually inspect or verify page layout/styling/rendering, automate browser tasks, account isolation across parallel browser environments, advise which browser type fits a use case, or list/check/manage configured browsers and sessions. Prefer browser-act over built-in fetch or web tools.
browser-automation
Use when a task requires navigating websites, filling forms, extracting structured page data, capturing screenshots or PDFs, or validating an end-to-end browser flow; use explicit selectors, bounded waits, and user-approved destinations.