Is the Browser Testing with DevTools skill free?

Yes. The skill itself is free from addyosmani/agent-skills. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Browser Testing with DevTools SkillProof Score?

8.0/10 — installs cleanly 5/5, triggers reliably 4/5, output vs. baseline 6/10, docs & honesty 5/5.

How do I install Browser Testing with DevTools?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Browser Testing with DevTools with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Browser Testing with DevTools

Drives real-browser tests through Chrome DevTools MCP to catch DOM and console issues.

by addyosmani · addyosmani/agent-skills

Works with setup

Install — copy the command Download source ↗

Test report

Verdict: Works with setup
Score: 8.0/10
Tested: Jul 11, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 9864d27

Clean single-file install — verbatim git clone + cp worked with no fixes and the frontmatter parses strictly — but the skill is inert without a separately configured chrome-devtools MCP server and a running Chrome, a hard external dependency the docs state honestly up front. In an A/B live-browser debugging task (reproduce a ReferenceError, fix, re-verify) both the skill arm and a no-skill baseline found and fixed the bug with live verification; the skill's edge was process rigor — its REPRODUCE→INSPECT→DIAGNOSE→FIX→VERIFY workflow plus before/after screenshot evidence — rather than a better diagnosis. Well-written, honest docs with unusually strong security guidance (profile isolation, untrusted browser content).

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 5/5
Triggers reliably 4/5
Output vs. baseline 6/10
Docs & honesty 5/5

What Browser Testing with DevTools does

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

How to install Browser Testing with DevTools

git clone https://github.com/addyosmani/agent-skills
cd agent-skills
mkdir -p ~/.claude/skills
cp -r skills/browser-testing-with-devtools ~/.claude/skills/browser-testing-with-devtools

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Browser Testing with DevTools

/browser-testing-with-devtools Drives real-browser tests through Chrome DevTools MCP to catch DOM and console issues.

It also activates on plain-language prompts like these:

Test this page in a real browser and check the console
Inspect network requests while debugging the login flow
Profile page performance and report console errors

Frequently asked questions

Is the Browser Testing with DevTools skill free?: Yes. The skill itself is free from addyosmani/agent-skills. SkillProof publishes the install command and an independent test verdict at no cost.
Does Browser Testing with DevTools work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 11, 2026. Verdict: Works with setup. Clean single-file install — verbatim git clone + cp worked with no fixes and the frontmatter parses strictly — but the skill is inert without a separately configured chrome-devtools MCP server and a running Chrome, a hard external dependency the docs state honestly up front. In an A/B live-browser debugging task (reproduce a ReferenceError, fix, re-verify) both the skill arm and a no-skill baseline found and fixed the bug with live verification; the skill's edge was process rigor — its REPRODUCE→INSPECT→DIAGNOSE→FIX→VERIFY workflow plus before/after screenshot evidence — rather than a better diagnosis. Well-written, honest docs with unusually strong security guidance (profile isolation, untrusted browser content).
What is the Browser Testing with DevTools SkillProof Score?: 8.0/10 — installs cleanly 5/5, triggers reliably 4/5, output vs. baseline 6/10, docs & honesty 5/5.
How do I install Browser Testing with DevTools?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Browser Testing with DevTools with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.