qa

# QA Drive a website with a real browser, judge how well it does the thing the user asked about, and return a **score from 1 (broken) to 5 (excellent)** with evidence. The deliverable is a verdict, not a screenshot dump. ## Inputs From the user's invocation (the text after `/qa`, or their message): - **Target** — a URL (`https://…`) or a local dev server (`localhost:5173`, `:3000`, "the app on 5173"). **Required** — if absent, ask for it before doing anything else. - **What to test** (optional) — a flow or focus ("the signup", "search + filters"). If omitted, test the most obvious happy path and say so in the report. ## Dependency: browser-harness (required — install it yourself) This skill runs the test through **browser-harness** — a separate CLI you install once. It is not optional; QA must run on a real Browser Use cloud browser, never the user's local Chrome. **Before anything else, verify it's available:** ```bash command -v browser-harness && browser-harness <<'PY' print("browser-harness OK") PY ``` If `browser-harness` is **not** on `PATH`, **install it yourself — don't make the user do it.** QA runs on a *cloud* browser, so the CLI is all you need: none of browser-harness's local-browser setup (`chrome://inspect`, the "Allow remote debugging" popup) applies here — skip all of it. The install is one-time (~30s), no clone: ```bash command -v uv || curl -LsSf https://astral.sh/uv/install.sh | sh # the uv installer, only if missing export PATH="$HOME/.local/bin:$PATH" # uv and its tool shims land here; the installer doesn't update the current shell's PATH uv tool install --python 3.12 --upgrade browser-harness # latest stable release from PyPI command -v browser-harness # verify it's on PATH now ``` (No `uv` and can't `curl | sh`? Install uv per https://docs.astral.sh/uv/getting-started/installation/ then re-run the `uv tool install` line — or `pipx install browser-harness`.) Do not attempt to QA with anything other than browser-harness + a cloud browser. ## Procedure 1. **Confirm the target is reachable** (`curl -s -o /dev/null -w "%{http_code}" <url>`), and identify what the app is (title, README) so you can frame a sensible test task. 2. **Read `references/methodology.md`** in this skill directory and follow it exactly. It defines: how to get a Browser Use API key (or self-sign-up), how to tunnel a localhost app and point a cloud browser at it, the field-tested gotchas (host-header rewrite, proxy-off, the per-tab interstitial header, CORS-pinned APIs), the test loop, the 1-5 rubric, and the output format. 3. **Run the test**, then **tear everything down** (stop the cloud browser so it stops billing; kill the tunnel). 4. **Return the verdict**: lead with `Score: N/5`, then task, result, what worked, issues (tagged), edge cases tried, and screenshot evidence — exactly as `references/methodology.md` specifies. Scale effort to the ask: a quick "does X work?" is a few interactions and one score; "thoroughly QA this" warrants more flows and edge cases. Keep the verdict honest, specific, and reproducible.