browser-automationlisted

# Browser Automation Use this skill when you need the `browser` tool for anything beyond a single page check. ## Operating Loop 1. Check browser state before acting: - `openclaw browser doctor` or `action="status"` when the browser/plugin setup itself may be broken. - `action="status"` for availability. - `action="profiles"` if login state or profile choice matters. - `action="tabs"` before opening a new tab if retries/timeouts may have left windows behind. 2. Prefer stable tab handles: - Open important tabs with `label`, for example `label="meet"`. - After `action="tabs"` or `action="open"`, store `suggestedTargetId` and pass it as `targetId` in later calls. - `suggestedTargetId` is the label when one exists, otherwise the stable `tabId` handle like `t1`. - Avoid relying on raw DevTools `targetId` except for immediate diagnostics; it can change under Chromium target replacement. 3. Read before you click: - Use `action="snapshot"` on the intended `targetId`. - Use the same `targetId` for follow-up actions so refs stay on the same tab. - For durable Playwright refs, request `refs="aria"` when supported. If you receive `axN` refs from `snapshotFormat="aria"`, use them only after that same snapshot call; stale or unbound `axN` refs fail fast and need a fresh snapshot. - Use `urls=true` when link text is ambiguous or a direct navigation target would avoid brittle clicks. - Use `labels=true` on snapshot or screenshot when visual position m