Agent skill · paulrberg
chromium-browser
Use Chrome DevTools through PRB's shared attach-only Chromium browser for browsing, debugging, automation, visual inspection, console or network analysis, performance or memory profiling, screencasts, and Wayback Machine research.
What it needs
About 4k tokens when loaded.
What this skill does
Chromium Browser Operate the configured Chrome DevTools MCP against the existing shared browser without disrupting unrelated tabs or authenticated state. Environment Contract Treat ~/.local/libexec/mcp/chrome-devtools and the tools exposed in the current session as authoritative. The wrapper owns server versioning, flags, logging, and browser attachment; do not run the MCP package directly. The MCP attaches to an existing remote-debugging browser. Never launch a fallback browser or create another profile when attachment fails. Treat the browser as shared, authenticated, and concurrently used by the user and other agents. Inspect only pages relevant to the task and do not surface unrelated tab titles or content. Trust the live tool inventory; an absent tool is unavailable in this session. Do not advise editing client MCP configuration as a troubleshooting shortcut. Reference Routing For Wayback Machine capture discovery or replay research, read references/wayback-machine.md before making any Wayback request. Otherwise do not load it. Discover captures through serialized APIs outside Chromium, then open only the selected replay when rendered inspection adds evidence. Page Ownership 1. Call listpages before interacting and preserve the initial pages as pre-existing state. 2. Prefer newpage with background: true when a fresh page satisfies the task. Record the exact pageId returned by every page this task creates; never infer ownership from a later page-list difference. 3. Pass an explicit pageId to every page-scoped tool. Do not rely on selected-page state; use selectpage only when deliberately bringing a page to the foreground. 4. Navigate or mutate a pre-existing page only when the task explicitly depends on that page's current state. Never close a pre-existing page. 5. At completion, close only the recorded pages created by this task unless the user asked to leave one open. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paulrberg/chromium-browser