Description
browser-testing-with-devtools is an agent skill from Addy Osmani's agent-skills collection that uses Chrome DevTools MCP to give an agent a view into a real browser. The idea is to verify behavior at runtime rather than guess from static code. With the tool, the agent can see what the user sees, inspect the DOM, read console logs, analyze network requests and API responses, and capture performance data such as Core Web Vitals, paint timing and layout shifts. The skill lists when to use it: when building or changing anything that renders in a browser, when debugging layout, styling or interaction problems, when diagnosing console errors and warnings, when checking network calls, when profiling performance, when confirming a fix works in the browser, and when running automated UI tests through the agent. It says not to use it for backend-only changes, CLI tools or code that never runs in a browser. The skill includes a section on setting up Chrome DevTools MCP. It is listed on skills.sh, with its security audit results shown there. It suits developers and agents who work on web front ends and want evidence from the running page.…
Highlights
- Inspect the DOM and read console logs
- Analyze network requests and responses
- Capture Core Web Vitals and paint timing
- Automated UI checks through the agent
Ratings & Reviews
No ratings yet
Be the first to rate browser-testing-with-devtools.
People also visit
jira-integration
Retrieving Jira tickets, analyzing requirements, updating ticket status
browser-testing-with-devtools FAQ
What does the browser-testing-with-devtools skill do?
It uses Chrome DevTools MCP to let an agent inspect and test a page in a real browser, including the DOM, console, network and performance data.
How do I install it?
Run: npx skills add https://github.com/addyosmani/agent-skills --skill browser-testing-with-devtools
When should I not use it?
For backend-only changes, CLI tools, or code that does not run in a browser.
What does it measure?
The DOM, console logs, network requests, and performance data such as Core Web Vitals, paint timing and layout shifts.
What security checks has it passed?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Warn. A Warn or Fail is worth reading before you install.
What are the best browser-testing-with-devtools alternatives?
Popular alternatives to browser-testing-with-devtools include mcporter, codehealth-mcp and deep-research. See all browser-testing-with-devtools alternatives