browser-testing-with-devtools

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The browser environment is difficult to audit from outside, so this skill uses Chrome DevTools MCP to give your agent eyes into the browser, enabling live inspection of the DOM, console logs, network activity, and performance data to verify UI behavior.

Core Features & Use Cases

  • DOM inspection and live state reading to verify rendering and structure
  • Console log capture for diagnosing errors and warnings
  • Network monitor for API call verification and payload analysis
  • Performance tracing to profile load times and bottlenecks
  • Accessibility tree checks to validate screen reader experience
  • Read-only JavaScript execution to inspect page state without mutating it
  • Use cases: debugging UI issues, validating fixes in real runtime, profiling performance, auditing network activity

Quick Start

Enable Chrome DevTools MCP and start a browser inspection session to verify DOM, network, and console output.

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 live DOM state in a browser to debug UI rendering issues?

Network monitoring verifies API calls and analyzes request payloads by capturing live browser network activity. It tracks outgoing requests and responses to debug connectivity issues and validate data exchange during UI rendering.

Can I profile performance bottlenecks using a browser DevTools trace?

Performance tracing profiles load times and identifies bottlenecks by recording runtime metrics in a real browser. It captures execution timelines to help developers locate slow scripts and rendering delays during page loads.

How do I capture console logs and errors from a real browser session?

Console log capture diagnoses errors and warnings by extracting runtime output from a live browser session. It records JavaScript exceptions and console messages to verify UI behavior and pinpoint script failures during rendering.

Does read-only JavaScript execution work safely for inspecting untrusted page data?

Read-only JavaScript execution inspects page state without mutating it, operating safely within an untrusted data context. It allows querying live variables and application state to verify UI behavior without risking unwanted side effects.

How do I check the accessibility tree to validate screen reader experience?

Accessibility tree checks validate the screen reader experience by inspecting the live browser's exposed DOM structure. It audits ARIA roles and semantic hierarchy to ensure UI components are properly announced to assistive technologies.