← ClaudeAtlas

browselisted

Browse, operate and verify web pages with the SnapSurf MCP tools (browser_open, browser_find, browser_act, browser_verify, browser_assert). Use whenever a task involves reading, navigating, testing or verifying a website or a local web app, or checking whether an action on a page actually changed anything.
zumerlab/snapsurf · ★ 0 · AI & Automation · score 70
Install: claude install-skill zumerlab/snapsurf
# Browse and verify with SnapSurf SnapSurf gives you a semantic view of a page and a typed diff after each action, so you read what changed instead of re-reading the page or taking screenshots. The tools come from the `snapsurf` MCP server this plugin installs; their descriptions carry the full contract, and every reply puts the facts in `structuredContent`. ## The loop 1. `browser_open` the URL. You get a ~2 KB digest: landmark regions with ids, headings, and the top ranked actionables with their hrefs. Ids look like `n_1r2x`. 2. If the element you need is not in the digest, `browser_find` with its text. It searches the WHOLE page and returns ranked clickable ids with hrefs. Never scroll blindly, never guess coordinates. 3. `browser_act` — `click` by id, `type` into the focused element (click it first), or `enter`. Native single-select controls also accept `select` with the target id and exactly one of `value` or `label` (an exact option match). The reply echoes the role and name of the element actually resolved: read it. 4. After EVERY action, `browser_verify`. It returns `changed` (a faithful negative: if the click did nothing it says so), the list of changes with kind, role and name, and what became covered or visible. Read `structuredContent`, not the prose. 5. To assert the transition you just read, call `browser_assert` with the `diffId` that verify returned (`changed`, `mustInclude`, `mustNotInclude`, `only`, `maxChanges`, `becameVisib