Agent skill · operations · borghei
qa-browser-automation
Browser-based QA combining Chrome MCP control with Python analysis tools. Use when performing browser QA testing, visual regression tracking, WCAG accessibility auditing, performance profiling, or health-scoring web applications.
Why this skill is useful
Includes four executable Python scripts for QA automation that provide capabilities beyond standard testing practices.
What it needs
Requires chrome-mcp, python installed locally. About 5k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
QA Browser Automation The agent drives Chrome MCP for live browser testing and uses four Python tools for deterministic health scoring, accessibility auditing, visual regression tracking, and report generation. --- Clarify First Before the QA sweep, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Target URL/app + auth — what to test and how to log in (the subject of the entire sweep) [ ] Testing tier — Quick / Standard / Deep / Exhaustive (sets scope, breakpoints, and duration) [ ] Fix autonomy — auto-fix P3/P4 and commit, vs report-only / ask before any code change (changes whether the working tree is modified) [ ] WCAG target level — A / AA / AAA (sets the accessibility pass bar) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Quick Start Tools Overview Tool Input Output ------ ------- -------- qahealthscorer.py Findings JSON Score 0-100, grade A-F, category breakdown, trend data accessibilityauditor.py HTML file (or stdin) WCAG violations by level with remediation guidance visualregressiontracker.py Baseline + current screenshot dirs Pass/fail per page, change percentages testreportgenerator.py Session data JSON Markdown or JSON report with recommendations All tools support --json for machine output. Health scorer and regression tracker return exit code 1 on failure (CI-friendly). --- Workflow 1: Full Application QA Sweep (11 Phases) Phase 1-2: Pre-flight and authentication. Verify git status is clean. Abort if dirty. Create session directory: .qa-sessions/{timestamp}/ Authenticate via Chrome MCP if needed. Phase 3-4: Orient and explore. Use mcpclaude-in-chromereadpage to build sitemap/page map. Navigate each route. Check readconsolemessages for errors, readnetworkrequests for 4xx/5xx. Test all forms with valid data, empty submissions, and boundary values. Phase 5: State testing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/qa-browser-automation