stonega/cusco/chrome-devtools
Claude Code and agent skill by stonega/cusco
- community
Checking that the SKILL.md file is still in the repository.
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).
Install
npx vskill@latest install stonega/cusco/chrome-devtoolsSKILL.md
The same SKILL.md was published earlier as stonega/cusco/chrome-devtools.
Using this skill in Cusco
Use Cusco’s connected mcp__chrome_devtools__* tools for browser tasks; the CLI skill applies to shell automation requests. Read the Cusco connection guide for connection status, tool routing, saved configuration, and optional features. Before target navigation, create a new named Chrome tab group for the task using that guide; add subsequent task tabs to the same group. Use the live tool schema when an upstream example differs.
Core Concepts
Browser lifecycle: The first browser tool attaches to the user's running, signed-in Chrome profile using --auto-connect. Chrome must have remote debugging enabled and the user must accept its Allow prompt. Keep task tabs in that same profile; do not use isolatedContext unless a clean-session test is requested. Inspect configuration options with npx -y chrome-devtools-mcp@1.9.0 --help. The Cusco preset already enables these additional categories:
- For extension tooling, use the
--categoryExtensionsflag. - For memory tooling, use the
--memoryDebuggingflag.
Page targeting: Page-scoped tools require a pageId parameter to target a specific page. Use list_pages to see available pages and their IDs (e.g. pageId: 1), or use the ID returned when creating a page with new_page. Note: For evaluate_script, pageId is required when targeting pages. However, when --categoryExtensions is enabled, pageId is optional so you can pass serviceWorkerId instead to evaluate inside an extension background service worker. Element interaction: Use take_snapshot to get page structure with element uids. Each element has a unique uid for interaction. If an element isn't found, take a fresh snapshot - the element may have been removed or the page changed.
Workflow Patterns
Before interacting with a page
- Group: follow task tab groups to open a helper tab
and create the task's group, or add the tab to this task's existing group.
- Navigate that same MCP
pageIdto the target URL withnavigate_page. - Wait:
wait_forto ensure content is loaded if you know what you look for. - Snapshot:
take_snapshotwithpageIdto understand page structure - Interact: Use element
uids from snapshot forclick,fill, etc., passing the correspondingpageId.
Efficient data retrieval
- Use
filePathparameter for large outputs (screenshots, snapshots, traces) - Use pagination (
pageIdx,pageSize) and filtering (types) to minimize data - Set
includeSnapshot: falseon input actions unless you need updated page state
Tool selection
- Automation/interaction:
take_snapshot(text-based, faster, better for automation) - Visual inspection:
take_screenshot(when user needs to see visual state) - Additional details:
evaluate_scriptfor data not in accessibility tree
Parallel execution
You can send multiple tool calls in parallel, but maintain correct order: navigate → wait → snapshot → interact.
Testing an extension
Extension tools (install_extension, list_extensions, etc.) require --category-extensions, which is included in the preset. If they are missing, inspect the saved server's flags and tool allowlist using the connection guide. Preserve its other arguments when enabling a category, then restart Cusco. Use Chrome 149+ for extension testing through auto-connect; the extension directory must be within a configured filesystem root.
- Install: Use
install_extensionwith the path to the unpacked extension. - Identify: Get the extension ID from the response or by calling
list_extensions. - Trigger Action: Use
trigger_extension_actionto open the popup or side panel if applicable. - Verify Service Worker: Use
evaluate_scriptwithserviceWorkerId(omittingpageIdandargs) to check extension state or trigger background actions. When evaluating in a page, passpageId(omittingserviceWorkerId). - Verify Page Behavior: Navigate to a page where the extension operates and use
take_snapshotto check if content scripts injected elements or modified the page correctly.
Troubleshooting
If chrome-devtools-mcp is insufficient, guide users to use Chrome DevTools UI:
- https://developer.chrome.com/docs/devtools
- https://developer.chrome.com/docs/devtools/ai-assistance
If there are errors launching chrome-devtools-mcp or Chrome, refer to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/chrome-devtools/skills/chrome-devtools/SKILL.md
Popularity
- Repository stars
- 4
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/stonega/cusco/chrome-devtools)