addy-browser-testing-with-devtools

Tests and debugs web pages in real browsers using Chrome DevTools MCP.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill addy-browser-testing-with-devtools-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: addy-browser-testing-with-devtools
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/addy-browser-testing-with-devtools
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill addy-browser-testing-with-devtools-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? Static code analysis cannot reveal what actually happens at runtime in a browser. This Skill gives the agent live visibility into the browser so UI bugs, console errors, network failures, and performance issues are verified with real runtime data instead of guesswork. ## Core Features & Use Cases - Live Browser Inspection: Capture screenshots, read the DOM, inspect computed styles, and read the accessibility tree through Chrome DevTools MCP. - Console, Network, and Performance Analysis: Diagnose console errors, verify API request/response payloads, and record performance traces covering LCP, CLS, and INP. - Structured Debugging Workflows: Follow reproduce-inspect-diagnose-fix-verify flows for UI bugs, network issues, and performance regressions, with screenshot-based before/after verification. - Use Case: A task completion animation glitches in your app. The agent navigates to localhost, reproduces the bug, checks the console and network monitor for the PATCH request, identifies the root cause, applies the fix, and verifies with a clean console and a comparison screenshot. ## Quick Start Use the browser testing skill to open my app on localhost:3000, reproduce the layout bug on the tasks page, and check the console and network requests for errors.

Frequently Asked Questions about addy-browser-testing-with-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug UI bugs with Chrome DevTools MCP?▼

Follow the reproduce-inspect-diagnose-fix-verify workflow: navigate to the page, trigger the bug, take a screenshot, then check console errors, inspect the DOM element, and read computed styles. After fixing the source code, reload and verify with a comparison screenshot and a clean console.

How to set up chrome-devtools-mcp server?▼

Add a chrome-devtools entry to your .mcp.json with command npx and args -y chrome-devtools-mcp@latest --isolated. The --isolated flag uses a temporary browser profile wiped on close, which is the recommended setup for most testing.

Can Chrome DevTools MCP analyze network requests and performance?▼

Yes. The network monitor captures request URLs, headers, payloads, response status codes, and timing, while the performance trace tool records Core Web Vitals including LCP, CLS, and INP plus long tasks over 50ms.

Is it safe to connect the agent to my logged-in Chrome profile?▼

Attaching via --autoConnect gives the agent access to all open windows of your profile, including logged-in sessions. Default to the dedicated or --isolated profile, and if logged-in state is required, use a separate test profile signed into only the account under test.

When should I not use browser testing with DevTools?▼

Do not use it for backend-only changes, CLI tools, or code that does not run in a browser. It is designed for anything that renders in a browser, where runtime verification adds value over static analysis.