← ClaudeAtlas

browserlisted

Fast scripted work with websites: browser-harness (CDP) plus a page snapshot as a numbered table, so one call can open, fill, click, walk result pages and extract data, and the site's own data (internal API, embedded JSON) comes before DOM parsing. Use when something has to be done on a site or pulled from it: "go to this site", "find it on a job board / marketplace", "collect from this page / from several pages", "scrape it", "get it through the site's API", "fill in the form", "click around the site", "does the search / form work", "screenshot the site"; and when WebFetch returned an empty shell, a refusal, or the page is rendered by JS. Plain reading of a public page, docs or a documented API is WebFetch/curl, not this. Showing the user a page in the app pane or their own dev server: the built-in browser. Acting in their main Chrome with their logins: Claude in Chrome.
letsloose501/sqs-agent-memory · ★ 1 · Web & Frontend · score 77
Install: claude install-skill letsloose501/sqs-agent-memory
# browser The agent writes a short Python script; the script does everything that needs no fresh look at the page in **one** call and prints a snapshot. Speed comes from the number of calls, not from fast clicks: each call costs about a second of overhead, a snapshot costs 0.01-0.13 s. Engine: [browser-harness](https://github.com/browser-use/browser-harness) (MIT), the Python package `browser_harness`, installed separately as a uv tool (references/setup.md). The snapshot is ported from [jev-ultrafast](https://github.com/browser-use/jev-ultrafast) (`snapshot.js`, MIT): one CDP call instead of the accessibility tree and screenshots; for them it cut browser protocol calls from 1,092 to 101. Pagination follows the ideas of [maxun](https://github.com/getmaxun/maxun) (AGPL-3.0: ideas only, the code is ours). Racing a click against a native dialog follows playwright-core's `_raceAgainstModalStates` ([playwright-cli](https://github.com/microsoft/playwright-cli), Apache-2.0). Install, telemetry, profile: [references/setup.md](references/setup.md). ## Script first, the browser is reconnaissance The rule: use a script wherever one can work; the browser walks a site to find how its data and actions go (internal API, headers, anti-bot), so that a script or skill can be written from that. Before opening a site, look for an existing script: `sites.md` for the site, memory, the project's own tools. Kuper shows why: the browser hit a ServicePipe CAPTCHA and then a "turn off your VPN" page