Individual skill
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.
skills/web-browser/SKILL.md
Source commit 0865c849befd2021490679f96a8dee58c84ac857
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,211
- Repository last updated
- Sep 27, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,805 bytesSKILL.mdcore · 5,805 bytesSKILL.mdcore · 5,805 bytesscripts/browser-processes.jsruns · 1,226 bytesscripts/browser-processes.test.jsruns · 1,066 bytesscripts/cdp.jsruns · 7,647 bytesscripts/devices.jsruns · 3,498 bytesscripts/dismiss-cookies.jsruns · 14,459 bytesscripts/emulate.jsruns · 3,586 bytesscripts/emulation-state.jsruns · 1,950 bytesscripts/eval.jsruns · 2,278 bytesscripts/logs-tail.jsruns · 1,904 bytesscripts/nav.jsruns · 1,926 bytesscripts/net-summary.jsruns · 2,605 bytesscripts/package-lock.jsonasset · 756 bytesscripts/package.jsonruns · 68 bytesscripts/pick.jsruns · 5,693 bytesscripts/screenshot.jsruns · 4,511 bytesscripts/start.jsruns · 7,895 bytesscripts/stop.jsruns · 1,935 bytesscripts/watch.jsruns · 7,413 bytes
Read excerpt
# Web Browser Skill
Minimal CDP tools for collaborative site exploration.
## Start Chrome (Prefer Headless)
```bash
./scripts/start.js --headless # Recommended: isolated reusable profile
./scripts/start.js --headless --profile # Headless with a copy of your profile
./scripts/start.js # Visible browser window when needed
./scripts/start.js --headless --reset-profile # Clear cached profile before launch
```
Starts Chrome with remote debugging (default port `:9222`). **Agents should use `--headless` by default** because it is less disruptive and supports navigation, evaluation, screenshots, emulation, and logging. User extensions are disabled for headless launches; a copied profile still provides its cookies and other browser state, but extension-based features are unavailable. Headed launches continue to load extensions normally. Use headed mode only when a person needs to see or interact with the browser, such as for `pick.js`, manual authentication, or debugging a headless-specific difference.