Browser Testing

by addyosmani

Browser Testing is a Quality skill for Claude Code, published by addyosmani in agent-skills.

86.7K stars9.3K forkson addyosmani/agent-skillsAdded 2026/08/13Repository updated 2026/08/11

View source on GitHub Download repo ZIP

agent-skillsantigravityclaude-codecodexcursorskills

Install in seconds

Install Browser Testing

Copy Browser Testing into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/addyosmani/agent-skills/tree/main/skills/browser-testing-with-devtools ~/.claude/skills/browser-testing-with-devtools

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/addyosmani/agent-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/browser-testing-with-devtools/SKILL.md in addyosmani/agent-skills
Installs to: ~/.claude/skills/browser-testing-with-devtools
Collection: One of 24 skills cataloged from this repository
Category: Quality — 1354 skills

What Browser Testing does

Browser Testing runs tests and inspections in a real browser via Chrome DevTools MCP. Use it when building or debugging browser UI to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output.

Browser Testing is cataloged under Quality on DirSkills. Browser Testing comes from a repository tagged agent-skills, antigravity, claude-code, codex and cursor.

Documentation

README

Excerpt

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Browser Testing

What else does addyosmani publish alongside Browser Testing?
Browser Testing is one of 24 skills that DirSkills catalogs from addyosmani/agent-skills, the repository it ships in. Its siblings there include API and Interface Design, Agent Skill Discovery and CI/CD and Automation. Each one is a separate skill with its own page in this directory, installs the same way Browser Testing does, and is maintained by addyosmani in that same repository. The rest of the collection is listed on the addyosmani/agent-skills page.
How does Browser Testing compare to other Quality skills?
Browser Testing ranks #28 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Browser Testing against them. Open each page to compare what they document and how they install.