Browser Testing with DevTools
Give your agent eyes into the browser via Chrome DevTools MCP — DOM, console, network, performance, real runtime data
- What
- Give your agent eyes into the browser via Chrome DevTools MCP — DOM, console, network, performance, real runtime data
- Cost
- Free
- Needs
- the chrome-devtools MCP server configured (add to .mcp.json or Claude Code settings: npx -y chrome-devtools-mcp@latest --isolated)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a browser-verification skill from Addy Osmani's engineering workflow collection: use Chrome DevTools MCP to give your agent eyes into the browser, bridging the gap between static code analysis and live execution. The agent can inspect the DOM, read console logs, analyze network requests, profile performance (Core Web Vitals, paint timing, layout shifts), and verify that a fix actually works with real runtime data — instead of guessing. It pairs with TDD for browser-based changes and explicitly forbids page-data exfiltration. Distinct from the already-published addyosmani skills — none of them cover live browser verification. By @addyosmani, listed here with credit to its creator. Honest caveats: requires the chrome-devtools MCP server configured (npx chrome-devtools-mcp); the isolated profile is wiped on close, so no persistent logins across sessions — plan accordingly. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: the chrome-devtools MCP server configured (add to .mcp.json or Claude Code settings: npx -y chrome-devtools-mcp@latest --isolated) Install "Browser Testing with DevTools" for me. Give your agent eyes into the browser via Chrome DevTools MCP — DOM, console, network, performance, real runtime data Repository: https://github.com/addyosmani/agent-skills/blob/main/skills/browser-testing-with-devtools/SKILL.md 1. Fetch the SKILL.md file for the addyosmani-browser-testing-with-devtools skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-browser-testing-with-devtools". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.