browser-testing-with-devtools

Inspect live DOM, console, network, and performance data via Chrome DevTools MCP.

9|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/klh/speedy-claude --skill browser-testing-with-devtools-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/klh/speedy-claude/tree/main/skills/browser-testing-with-devtools
Command: npx skills add https://github.com/klh/speedy-claude --skill browser-testing-with-devtools-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents and developers cannot reliably diagnose runtime browser issues from static code alone; this Skill provides live browser inspection so you can observe DOM, console, network, and performance behavior as it actually runs to find root causes quickly.

Core Features & Use Cases

  • Live DOM Inspection: Read the rendered DOM tree to verify component output and structure.
  • Console & Network Capture: Collect console logs and network requests/responses to diagnose errors and API issues.
  • Performance & Visual Verification: Capture performance traces and screenshots for profiling and visual regression checks.
  • Use Case: When a UI bug only appears in the browser, use this Skill to reproduce the issue, capture a trace and screenshots, inspect the DOM and network activity, implement a code fix, and verify the result in the same session.

Quick Start

Open the target page with the Chrome DevTools MCP connection and capture a screenshot, DOM snapshot, console logs, network requests, and a short performance trace for the failing flow.

Frequently Asked Questions about browser-testing-with-devtools

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

FAQPage Schema
How do I debug a UI bug that only appears in the browser?

Live browser inspection lets you observe the rendered DOM, console logs, and network activity as the application actually runs to find root causes quickly. You can reproduce the issue, capture a performance trace, inspect the DOM, and verify the fix in the same session.

Can I capture network requests and console logs for front-end debugging?

Capturing network requests and console logs allows you to collect live network responses and console output to diagnose front-end errors and API issues. This live data helps pinpoint the exact source of runtime failures and API mismatches.

What is the best way to inspect the rendered DOM tree of a web application?

Live DOM inspection reads the rendered DOM tree to verify component output and structure. This ensures you see the actual runtime state of the UI rather than relying on static code assumptions.

How do I capture a performance trace and screenshot for visual regression checks?

Capture a performance trace and screenshot by running the failing flow in a real browser with DevTools connected. This provides visual verification and profiling data to identify rendering bottlenecks and visual regressions.

Does Chrome DevTools MCP support accessibility inspection for web applications?

Chrome DevTools MCP supports diagnosing accessibility issues in real browsers. You can apply live inspection to evaluate accessibility behavior directly during runtime, ensuring compliance alongside performance and network checks.

Why does static code analysis fail to diagnose runtime browser issues?

Static code analysis cannot observe live DOM, console, network, and performance behavior. Without live browser inspection, the actual runtime state and execution context of the UI remain hidden, making root causes hard to find.