$ skilldirectory
— zsh — registry.skilldirectory.dev
skill library blog

home / Browser Automation / Browser Testing With Devtools Skill by @sickn33

Browser Testing With Devtools Skill by @sickn33

FREE
github stars★ 49,230updatedOct 2026repo@sickn33
$git clone https://github.com/sickn33/agentic-awesome-skills

The skill is the skills/browser-testing-with-devtools folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

Read the opening of the original SKILL.md
# Browser Testing with DevTools

## Overview

Use Chrome DevTools MCP to give your agent eyes into the browser. This bridges the gap between static code analysis and live browser execution — the agent can see what the user sees, inspect the DOM, read console logs, analyze network requests, and capture performance data. Instead of guessing what's happening at runtime, verify it.

## When to Use

- Building or modifying anything that renders in a browser
- Debugging UI issues (layout, styling, interaction)
- Diagnosing console errors or warnings
- Analyzing network requests and API responses
- Profiling performance (Core Web Vitals, paint timing, layout shifts)
- Verifying that a fix actually works in the browser
- Automated UI testing through the agent

**When NOT to use:** Backend-only changes, CLI tools, or code that doesn't run in a browser.

## Setting Up Chrome DevTools MCP

### Installation
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.