browser-testing-with-devtools

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge the gap between static code analysis and live browser execution so agents can verify runtime behavior, reproduce UI bugs, and confirm fixes by observing the actual page state instead of guessing from code alone.

Core Features & Use Cases

  • Live DOM Inspection: Read the rendered DOM tree to verify component structure and detect mismatches between expected and actual markup.
  • Console & Network Analysis: Capture console errors, warnings, and network requests to diagnose runtime exceptions, API failures, and CORS or payload issues.
  • Performance Profiling: Record traces to measure LCP, CLS, INP, and identify long tasks or render bottlenecks.
  • Visual Verification: Take before/after screenshots for visual regression testing and responsive layout checks.
  • Security-conscious JS Execution: Run constrained, read-only JavaScript in the page context for targeted state inspection while avoiding credential access or external requests.
  • Use Case: Reproduce a task completion animation bug by reproducing the steps in the browser, inspecting the DOM and styles, checking console logs, examining network PATCH requests, applying a code fix, and verifying the visual result with screenshots.

Quick Start

Open the target page with Chrome DevTools MCP and ask the agent to reproduce the issue, capture a screenshot, inspect the DOM and computed styles, report console errors, analyze relevant network requests, and summarize findings.

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 inspect the live DOM to debug a UI rendering issue?

To debug a UI rendering issue, live DOM inspection reads the rendered DOM tree to verify component structure and detect mismatches between expected and actual markup, bridging static code analysis and live browser execution.

How do I capture console errors and network requests during browser testing?

During browser testing, console and network analysis captures console errors, warnings, and network requests to diagnose runtime exceptions, API failures, and CORS or payload issues directly from the live browser page.

What is the best way to measure web performance metrics like LCP and CLS?

To measure web performance metrics like LCP and CLS, performance profiling records browser traces to identify long tasks or render bottlenecks, verifying actual runtime behavior instead of guessing from code alone.

Can I run custom JavaScript in the browser context for state inspection?

Yes, you can run constrained, read-only JavaScript in the page context for targeted state inspection. This security-conscious execution strictly prevents credential access and external network requests.

How do I perform visual regression testing for responsive layouts?

Visual regression testing for responsive layouts uses before and after screenshots to verify visual results, confirming UI fixes by observing the actual page state after applying code changes.