| name | qa-chrome |
| description | Visual tests and browser debugging via Chrome. Use to test web pages, verify visual rendering, debug with the console, or automate browser actions. Trigger when the user mentions "visual test", "Chrome", "browser", "browser console", "DOM", "screenshot", "GIF". |
| allowed-tools | ["Read","Bash","Grep","Glob"] |
| context | fork |
| disable-model-invocation | true |
| argument-hint | [url-or-page] |
Visual Tests and Chrome Debugging (pointer)
DevTools features (network inspection, profiling, accessibility tree, console replay) are canonical at the Chrome team's MCP server:
ChromeDevTools/chrome-devtools-mcp — github.com/ChromeDevTools/chrome-devtools-mcp (Apache-2.0, maintained by the Google Chrome DevTools team). Configure in .mcp.json to give Claude Code direct programmatic access during a session.
This skill scopes to the manual-review checklist when using Claude Code's --chrome flag — what to look for, not how the API works.
Prerequisites
- Claude Code launched with
--chrome
- "Claude in Chrome" extension v1.0.36+
- Google Chrome open (not Brave/Arc/Firefox; no headless mode; WSL unsupported)
Manual-review checklist
When asked to visually validate a page or flow:
Expected output
Structured report:
- Screenshots/GIFs of issues
- List of console + network errors with source location
- Recommendations sorted by severity
- Overall verdict:
OK / Warnings / Errors
See also
chrome-devtools-mcp (vendor MCP server, programmatic layer) — docs/recipes/recommended-vendor-skills.mdqa-design skill — UI/UX heuristics + responsive/breakpoint testing complementwcag-audit — accessibility gate when contrast/readability issues surface- Audit pilot trace:
specs/marketplace-audit/qa-skills-pilot-2026-05-06.md
