From hai-qa-via-cli
Runs an autonomous QA review of a live web UI via a CLI agent. Returns structured findings on accessibility, usability, or correctness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hai-qa-via-cli:hai-qa-via-cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user asks you to QA a web UI / review a deployed page / check a URL for issues:
When the user asks you to QA a web UI / review a deployed page / check a URL for issues:
qa-cli review — full agent loop (~30–90s). Returns a structured ReviewResult JSON with verdict, summary, findings (each with severity, area, issue, suggestion), and steps_taken. Use this for any real review.qa-cli visual — one-shot visual question, returns a short free-text answer. Use for quick "what color is X" / "does the layout look broken" sanity checks.uv run qa-cli review --url <url> --instruction "<what to focus on>"
uv run qa-cli visual --url <url> --question "<single question>"
The CLI logs progress to stderr; the result (JSON for review, text for visual) goes to stdout. Pipe to jq if you want to filter.
For review:
verdict and the headline summary.findings ordered as returned (already high-severity-first). Show each as [severity] area — issue and include the suggestion when actionable.verdict == "fail", make it clear what blocked completion.For visual: just relay the answer.
qa-cli command comes from the computer-use-agents-demos repo. If uv run qa-cli ... errors with "command not found", that repo isn't installed in the current working directory — tell the user to clone it and run uv sync before retrying, or fall back to whichever QA tool is already on PATH.HAI_API_KEY in .env. On a missing key the CLI exits with error: HAI_API_KEY is not set... — relay that to the user verbatim; don't retry.review is expensive (one cloud session per call). Don't run multiple reviews in parallel for the same task — call it once with a focused --instruction.User: "Please QA https://news.ycombinator.com for accessibility." You: Run
uv run qa-cli review --url https://news.ycombinator.com --instruction "focus on accessibility — alt text, form labels, keyboard nav, contrast". Parse JSON. Surface findings.
User: "What color is the main CTA on https://example.com?" You: Run
uv run qa-cli visual --url https://example.com --question "what color is the main call-to-action button?". Return the answer.
npx claudepluginhub hcompai/computer-use-agents-demos --plugin hai-agentsQA tests web apps, native macOS/Electron apps, CLI tools, REPLs via browser/Playwright, computer-use screenshots/clicks, or tmux modes. Delivers health scores, bug fixes, ship-readiness reports.
Runs AI-powered adversarial UI testing via the browse CLI — analyzes git diffs, explores full apps, and tests functional correctness, accessibility, responsive layout, and UX heuristics. Use for QA pull requests, auditing accessibility, or exploratory testing.
QA tests a live website using Firecrawl browser and scrape for exploratory testing, form validation, navigation checks, responsive design, and performance audits with structured reporting.