Browser automation, debugging, performance profiling, and DevTools-driven diagnostics via Playwright
layer
utility
category
tooling
triggers
["open browser","inspect page","debug in browser","performance profile","lighthouse audit","network requests","console errors","test in browser"]
inputs
[{"url":"Target URL to inspect or automate"},{"action":"inspect | profile | automate | debug | audit"},{"selectors":"CSS selectors for specific elements (optional)"}]
[{"browser_state":"Opens and interacts with browser instances"},{"network":"Makes HTTP requests to target URLs"}]
Chrome DevTools
Purpose
This skill provides browser-based debugging, inspection, performance profiling, and automation capabilities via Playwright MCP. It enables direct interaction with web pages — navigating, clicking, reading content, capturing screenshots, monitoring network requests, and evaluating JavaScript — all without requiring a manual browser session.
Snapshot (browser_snapshot): Returns the accessibility tree as structured text. Best for understanding page structure, finding interactive elements, and getting element references for actions. Use this for most inspection tasks.
Screenshot (browser_take_screenshot): Returns a visual image. Best for visual regression checking, capturing current state for review, and when the visual layout matters more than the DOM structure.
Rule: Use snapshot first to understand the page, screenshot to capture visual evidence.
Workflows
Workflow 1: Page Inspection
STEP 1: Navigate to the target URL
→ browser_navigate(url)
STEP 2: Capture the accessibility snapshot
→ browser_snapshot()
→ Analyze the page structure, identify key elements
STEP 3: Take a screenshot for visual reference
→ browser_take_screenshot(type: "png")
STEP 4: Check console for errors
→ browser_console_messages(level: "error")
STEP 5: Check network requests
→ browser_network_requests(includeStatic: false)
OUTPUT:
PAGE STRUCTURE: [From snapshot]
VISUAL STATE: [Screenshot reference]
ERRORS: [Console errors found]
FAILED REQUESTS: [4xx/5xx responses]
RECOMMENDATIONS: [Based on findings]
Screenshot-first: Taking screenshots before snapshots. Snapshots are more information-dense and provide element references for interaction. Always snapshot first.
Missing wait states: Clicking a button and immediately reading the page. Always use browser_wait_for after actions that trigger async operations.
Hardcoded selectors: Using brittle CSS selectors that break with minor DOM changes. Prefer element references from snapshots.
Ignoring console: Not checking console messages after interactions. Many client-side errors only appear in the console.
Not closing browsers: Leaving browser instances open after completing tasks. Always use browser_close when finished.
Integration Notes
Hand off visual findings to ui-ux-pro for design system recommendations.
Hand off screenshots to ai-multimodal for detailed visual analysis.
Hand off error patterns to error-handling for systematic resolution strategies.
When performance issues are found, link to media-processing for asset optimization recommendations.