browser-driverlisted

# OneWorks In-App Browser Control Use this skill for websites shown in the OneWorks internal browser. It does not control external Chrome or native desktop applications. Prefer `execute_in_app_browser_workflow` when one page has two or more deterministic steps. When independent work is ready for multiple pages, submit it once with `execute_in_app_browser_workflows`; pages run concurrently while each page remains serial. Use low-level tools only to inspect, recover from a changed page, or perform a single action. 1. Use `in_app_browser_open` when the requested page is not already open. It reuses the same URL by default; pass `open_mode: "new-tab"` only when the task needs a separate page instance. Pages open on the right by default; pass `placement: "bottom"` only when a wide horizontal panel better suits the task. Call `in_app_browser_list_pages` only when you need to discover existing pages. Use `in_app_browser_show_page` to reveal an existing page when the user needs to see it; ordinary background operations should continue addressing the page directly by `page_id` without changing the visible tab. 2. Call `in_app_browser_snapshot` before referring to page elements. Keep its `page_id` paired with every returned `ref`; do not invent CSS selectors or coordinates. Every page operation requires an explicit `page_id`, so never rely on an implicit active tab. 3. A ref can become stale after navigation or DOM updates. If a tool returns `TARGET_NOT_FOUND`, take a new snapshot an