chrome-devtools
Skill1 starsChanged 7 months agoMITView on GitHub
Use when setting up or using the Chrome DevTools MCP — covers privacy-first install (--no-usage-statistics), per-project scoping to avoid polluting global context, when to use this MCP instead of Playwright, and ethical hacking patterns (Burp proxy, session recon, endpoint mapping).
43 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- byrodi/chrome-devtoolstheir own version, first seen Nov 8, 2026
- artivilla/agent-skillstheir own version, first seen Nov 8, 2026
- JustinWangJP/cc-agent-teams-action-monitortheir own version, first seen Nov 8, 2026
- LuisSambrano/antigravity-configtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use aesthetic, web-frameworks and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
mrgoonieSkillaesthetic
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
Also in 5 projects that use this
mrgoonieSkillweb-frameworks
Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.
Also in 8 projects that use this
truongtv22SkillProblem-Solving Techniques
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Also in 4 projects that use this
truongtv22Skillmobile-development
Build modern mobile applications with React Native, Flutter, Swift/SwiftUI, and Kotlin/Jetpack Compose. Covers mobile-first design principles, performance optimization (battery, memory, network), offline-first architecture, platform-specific guidelines (iOS HIG, Material Design), testing strategies, security best practices, accessibility, app store deployment, and mobile development mindset. Use when building mobile apps, implementing mobile UX patterns, optimizing for mobile constraints, or making native vs cross-platform decisions.
Also in 5 projects that use this
- +8 more from mrgoonie
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- ChromeDevTools/chrome-devtools-mcp★ 55ksame name
- github/awesome-copilot★ 41ksame name
- mrgoonie/claudekit-skills★ 2.2ksame name
- typv/nest-turbo-starter★ 224same name
- duongthinh03/portfolio★ 85same name
- laguagu/claude-code-nextjs-skills★ 72same name
- iuhoay/skills★ 54same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- ulises-jeremias/agent-toolkit★ 19same name
- johnlindquist/claude-workshop-skills★ 16same name
33 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autoresearchSkill
- experiment-runnerSkill
- playwright-browserSkill
- pr-reviewSkill
- save-knowledgeSkill
- skill-creatorSkill
- sp-plan-discoverySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 42 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Use --slim (3 tools: navigate_page, evaluate_script, take_screenshot) for basic tasks:
- Very specific: line 103
Run lighthouse_audit — surfaces missing CSP, HSTS, X-Frame-Options as findings.
“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
chrome-devtools
Complement to the official ChromeDevTools/chrome-devtools-mcp plugin. Install the plugin first — it covers core automation, performance, and debugging. This skill covers what the plugin doesn't: privacy, context management, and ethical hacking.
Setup
See README for copy-paste install blocks. Run scripts/setup-local.sh to add the MCP to the current project.
Managing Context (On/Off)
The MCP loads 29 tools into context. Add per project, remove when done:
# Add to current project
claude mcp add chrome-devtools --scope local -- npx -y chrome-devtools-mcp@latest --no-usage-statistics
# Remove
claude mcp remove chrome-devtools
# Verify
claude mcp listUse --slim (3 tools: navigate_page, evaluate_script, take_screenshot) for basic tasks:
"args": ["-y", "chrome-devtools-mcp@latest", "--slim", "--no-usage-statistics"]Chrome DevTools MCP vs Playwright
| Task | Use |
| Multi-browser (Firefox, WebKit) | Playwright |
| CI/CD test suite | Playwright |
Formal test assertions (expect, toBeVisible) | Playwright |
| Connect to existing Chrome session with auth | Chrome DevTools MCP |
| Performance tracing + Lighthouse | Chrome DevTools MCP |
| Memory snapshot | Chrome DevTools MCP |
| Ethical hacking / recon | Chrome DevTools MCP |
DevTools Protocol (evaluate_script) | Chrome DevTools MCP |
Ethical Hacking Patterns
Only use against systems you are authorized to test.
Route traffic through Burp Suite
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y", "chrome-devtools-mcp@latest",
"--proxyServer=http://127.0.0.1:8080",
"--acceptInsecureCerts",
"--no-usage-statistics"
]
}
}
}Connect to an existing Chrome session (preserves auth state)
Useful when the target blocks WebDriver-launched browsers (e.g., some SSO flows).
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/pentest-profile"args": ["-y", "chrome-devtools-mcp@latest", "--browser-url=http://127.0.0.1:9222", "--no-usage-statistics"]Recon: extract client-side storage
Via evaluate_script:
JSON.stringify({
cookies: document.cookie,
localStorage: Object.assign({}, localStorage),
sessionStorage: Object.assign({}, sessionStorage)
})Recon: map API endpoints
Navigate to the target and trigger app actions, then call list_network_requests to enumerate XHR/fetch calls, headers, and payloads.
Recon: inspect security headers
Run lighthouse_audit — surfaces missing CSP, HSTS, X-Frame-Options as findings.
Connect via WebSocket (sandboxed environments)
curl http://127.0.0.1:9222/json/version | jq '.webSocketDebuggerUrl'"args": [
"-y", "chrome-devtools-mcp@latest",
"--wsEndpoint=ws://127.0.0.1:9222/devtools/browser/<id>",
"--no-usage-statistics"
]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

