What problem does it solve? AI agents cannot see or interact with live web pages that depend on login state, cookies, client-side rendering, or visible user tabs. This Skill connects agents to a real Chromium browser through the local omnibot daemon and CLI so they can read rendered pages, click controls, fill forms, navigate, and collect verifiable evidence. ## Core Features & Use Cases - Native browser operations: Read page content, snapshot interactive elements, click, fill, select, scroll, navigate, and wait using semantic locators and tab-scoped refs instead of fragile JavaScript shortcuts. - Structured fallback tiers: Escalate from semantic find to snapshot refs, selectors, DOM, mouse, JavaScript, and raw CDP only with documented evidence, keeping automation auditable. - Debug evidence collection: Capture screenshots, console logs, network requests, traces, and recordings to prove browser state or explain failures. - Use Case: An agent needs to log into a web app, fill a checkout form, and confirm the order preview. It creates a tab, runs observe-act-verify cycles per control, and stops before the final payment button unless the user explicitly confirms. ## Quick Start Ask the agent to open a website in a new browser tab with omnibot, read the page content, and verify the final URL before reporting the result.