Run any Skill in Manus with one click

chrome-devtools

Stars6

Forks0

UpdatedJune 14, 2026 at 08:00

Inspect, instrument, and control a local Google Chrome through the Chrome DevTools MCP server. Use when Claude needs live Chrome tabs, navigation, DOM/console/network inspection, or Chrome DevTools Protocol commands against a running browser, rather than the headless browser automation covered by the playwright skill.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sluongng

sluongng/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	chrome-devtools
description	Inspect, instrument, and control a local Google Chrome through the Chrome DevTools MCP server. Use when Claude needs live Chrome tabs, navigation, DOM/console/network inspection, or Chrome DevTools Protocol commands against a running browser, rather than the headless browser automation covered by the playwright skill.

Chrome DevTools

Use the Chrome DevTools MCP server as the interface to a running Chrome on this machine. Its tools surface as mcp__chrome-devtools__* (load schemas with ToolSearch when they are not already in context). They drive Chrome over the Chrome DevTools Protocol and return structured results.

For scripted, headless, or cross-browser end-to-end automation, prefer the playwright skill instead. Reach for Chrome DevTools MCP when you specifically need to attach to and inspect the user's live Chrome session.

Prerequisites

The Chrome DevTools MCP server must be configured for the session. If the mcp__chrome-devtools__* tools are absent:

Confirm the server is registered (project or user .mcp.json / settings.json, or claude mcp list).
The common server is chrome-devtools-mcp (npx chrome-devtools-mcp@latest), which launches or attaches to Chrome and exposes DevTools Protocol tooling.
If it cannot be enabled, fall back to the playwright skill and say so.

Workflow

Discover the available mcp__chrome-devtools__* tools with ToolSearch and read their schemas before calling them.
Prefer read-only probes first: list pages/tabs, read the current URL/title, snapshot the DOM, read console messages, or capture a screenshot.
Use navigation and interaction tools (navigate, click, fill, evaluate) only when the task requires changing browser state.
Use raw CDP / evaluate calls for anything the higher-level tools don't cover, e.g.:
```
// via an evaluate-style tool
document.title
```
Clean up after browser work: close throwaway tabs you opened, leaving only tabs the user needs for handoff.

Safety

Do not read cookies, passwords, local storage, or arbitrary Chrome profile files.
Do not run interaction or raw CDP commands against logged-in sites unless the user explicitly asks for that browser action.
Treat the user's live session as theirs: navigate or mutate state only when requested, and report exactly what you did.

More from this repository

same repository

desktop-incident-triage

sluongng/dotfiles

Triage this Framework Desktop's Hyprland, CachyOS, SDDM login, Ghostty/Chrome focus, workspace routing, Bluetooth, AirPods, PipeWire, media controls, and local desktop service incidents with live-state checks before changing config.

2026-07-216

desktop-incident-triage

Create GitHub pull requests from the current checkout, including combined commit-and-PR requests. Use when Claude needs to inspect the change, use `draft-commit-message` as the source of truth for the commit message and PR title/body, then push and create a draft or ready PR without a separate wording approval when the user already requested PR creation.

2026-07-206

codex-chrome-linux

sluongng/dotfiles

Inspect, instrument, and control Linux Google Chrome through the local Codex Chrome Extension native messaging bridge. Use when Codex needs Chrome tabs, history, navigation, Chrome DevTools Protocol commands, native host manifest/socket troubleshooting, or a Linux browser-control path instead of Chrome DevTools MCP.

2026-07-206

github-create-pr

sluongng/dotfiles

Create GitHub pull requests from the current checkout, including combined commit-and-PR requests. Use when Codex needs to inspect the change, use `draft-commit-message` as the source of truth for the commit message and PR title/body, then push and create a draft or ready PR without a separate wording approval when the user already requested PR creation.

2026-07-206

linux-computer-use

sluongng/dotfiles

Use the local linux-computer-use CLI or MCP server to inspect and safely interact with running Wayland/Hyprland desktop apps through Sky-compatible computer-use tools, grim screenshots, AT-SPI, wtype, ydotool, approvals, and dry-run raw input.

2026-07-206

name	chrome-devtools
description	Inspect, instrument, and control a local Google Chrome through the Chrome DevTools MCP server. Use when Claude needs live Chrome tabs, navigation, DOM/console/network inspection, or Chrome DevTools Protocol commands against a running browser, rather than the headless browser automation covered by the playwright skill.

Chrome DevTools

Prerequisites

The Chrome DevTools MCP server must be configured for the session. If the mcp__chrome-devtools__* tools are absent:

Confirm the server is registered (project or user .mcp.json / settings.json, or claude mcp list).
The common server is chrome-devtools-mcp (npx chrome-devtools-mcp@latest), which launches or attaches to Chrome and exposes DevTools Protocol tooling.
If it cannot be enabled, fall back to the playwright skill and say so.

Workflow

Discover the available mcp__chrome-devtools__* tools with ToolSearch and read their schemas before calling them.
Prefer read-only probes first: list pages/tabs, read the current URL/title, snapshot the DOM, read console messages, or capture a screenshot.
Use navigation and interaction tools (navigate, click, fill, evaluate) only when the task requires changing browser state.
Use raw CDP / evaluate calls for anything the higher-level tools don't cover, e.g.:
```
// via an evaluate-style tool
document.title
```
Clean up after browser work: close throwaway tabs you opened, leaving only tabs the user needs for handoff.

Safety

Do not read cookies, passwords, local storage, or arbitrary Chrome profile files.
Do not run interaction or raw CDP commands against logged-in sites unless the user explicitly asks for that browser action.
Treat the user's live session as theirs: navigate or mutate state only when requested, and report exactly what you did.