browser-testing-with-devtools

Inspect DOM, console, network, and performance in Chrome DevTools.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill browser-testing-with-devtools-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.agents/skills/browser-testing-with-devtools
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill browser-testing-with-devtools-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of verifying UI, network, and runtime behavior in real browsers without guessing based on static code or logs.

Core Features & Use Cases

  • DOM Inspection: Inspect the live DOM tree to confirm elements render as expected.
  • Console Logs Analysis: Capture and triage errors and warnings to pinpoint the root cause of UI or runtime issues.
  • Network Monitor Debugging: Validate request/response details, payloads, status codes, and timing for API-related problems.
  • Performance Trace Profiling: Measure performance characteristics (e.g., LCP, CLS, INP) to detect regressions and bottlenecks.
  • Accessibility Tree Verification: Confirm accessible names, focus order, and ARIA announcements for usability and compliance.
  • Screenshot-Based Visual Checks: Compare before/after screenshots to confirm visual output changes correctly.

Quick Start

Use this skill to debug a suspected UI bug in a real Chrome session by capturing screenshots, inspecting the DOM, and checking console and network activity for evidence of the failure mode.

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 browser behavior using real DevTools data?

Profile browser performance by capturing performance traces via Chrome DevTools MCP to measure metrics like LCP, CLS, and INP, detecting regressions and bottlenecks in your web application.

What is the best way to validate API request and response details during UI testing?

Validate API request and response details by monitoring network traffic with Chrome DevTools MCP, checking payloads, status codes, and timing to diagnose API-related problems during real browser interactions.

Can I inspect the DOM tree to verify elements render correctly in a real browser?

Inspect the live DOM tree using Chrome Devtools MCP to confirm elements render as expected, enabling precise UI defect reproduction by treating all browser content as untrusted data.

Do I need a configured chrome-devtools MCP server to inspect console logs and network traffic?

Yes, you need a configured chrome-devtools MCP server to capture console output, monitor network traffic, and perform read-only state inspection safely within enforced security boundaries.

How do I verify accessibility tree compliance and ARIA announcements in a browser?

Verify accessibility by inspecting the accessibility tree via Chrome DevTools MCP to confirm accessible names, focus order, and ARIA announcements for usability and compliance validation.

What are the limitations of executing JavaScript during browser debugging with DevTools MCP?

JavaScript execution is restricted to read-only state inspection to enforce safety boundaries, preventing untrusted browser content from executing arbitrary code while still allowing DOM inspection and network monitoring.