browser-qa · c0x12c — Claude Code skill: what it does, how to install
Drives Playwright in Chromium to test pages, interactive UI elements, and responsive layouts before merging pull requests or deploying.
npx skills add c0x12c/ai-toolkit --skill browser-qa -a claude-codeWhat browser-qa does
The skill directs an assistant to inspect client-side applications using headless Chromium. It traverses discovered views, tracking HTTP response codes, missing assets, and uncaught script exceptions inside console.error. Testing covers two distinct profiles: 1280px desktop displays and 375px mobile viewports with touch event emulation enabled.
During execution, the tool verifies core user interactions without running persistent daemons. It clicks buttons, verifies modal visibility, confirms navigation links, and checks form validation logic. Any failed step captures a screenshot to document regressions accurately.
On applications running live websockets or recurring polling requests, standard networkidle listeners freeze execution indefinitely, which requires switching checks to domcontentloaded or explicit element selectors. The skill delivers a structured breakdown of failures first without altering codebase files automatically.
What it helps with
- inspect web pages for broken network requests and console errors
- verify layout consistency on 1280px and 375px viewports
- validate interactive buttons, modal dialogs, and form submissions
- capture failure screenshots during pre-release smoke testing
Example prompts for the agent
- Run browser-qa on the local frontend build to inspect responsive layouts and console issues
- Use browser-qa to verify form validation and check for broken navigation links before opening a PR
How to install browser-qa
1Skills CLI (Vercel)
npx skills add c0x12c/ai-toolkit --skill browser-qa -a claude-code2Manually: put the files in place
~/.claude/skills/browser-qa/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/browser-qa/
1Skills CLI (Vercel)
npx skills add c0x12c/ai-toolkit --skill browser-qa -a codex2Manually: put the files in place
.agents/skills/browser-qa/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add c0x12c/ai-toolkit --skill browser-qa -a cursor2Manually: put the files in place
.cursor/skills/browser-qa/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install c0x12c/ai-toolkit browser-qa2Manually: put the files in place
.github/skills/browser-qa/SKILL.md1Skills CLI (Vercel)
npx skills add c0x12c/ai-toolkit --skill browser-qa -a gemini-cli2Platform CLI
gemini skills install https://github.com/c0x12c/ai-toolkit --path toolkit/skills/browser-qaManually: put the files in place
.devin/skills/browser-qa/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add c0x12c/ai-toolkit --skill browser-qa -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about browser-qa
How to install browser-qa in Claude Code?
Run npx skills add c0x12c/ai-toolkit --skill browser-qa -a claude-code. The file will be written to ~/.claude/skills/browser-qa/SKILL.md.
What does the browser-qa skill do?
It spins up Playwright to navigate application routes, interact with buttons and forms, test responsive viewports, and generate an evaluation report with failure screenshots.
Does browser-qa report framework console warnings?
No, non-critical warnings such as React hydration notices are skipped. The skill flags actual network failures and explicit console.error events only.
Similar skills
All skills for Testing and QA →browser-qa by other authors comes first.