browser-validator
Validates test scenarios against a running application using Chrome MCP — navigates, interacts, and verifies in a real browser
$ npx -y skills add Anasss/qa-orchestra --agent claude-codeShips with qa-orchestra. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Validates test scenarios against a running application using Chrome MCP — navigates, interacts, and verifies in a real browser
10 standalone QA agents for Claude Code. Each one answers a specific question about your PR — does this diff implement the AC?, what scenarios do I need?, which of my tests will break? — and writes a Markdown report you can paste into GitHub or Jira.
Repo: Anasss/qa-orchestra
Other agents on qa-orchestra.
- automation-writer
Converts test scenarios into executable Playwright, Cypress, or Gherkin test code
Open agent - bug-reporter
Use this agent when qa-output/functional-review.md or qa-output/browser-validation.md reports any gap, failed scenario, or blocked verdict. Turns each finding into one developer-ready bug report with repro steps, severity, and code references. One finding per report — never
Open agent - environment-manager
Checks out PR branches, runs setup commands, and starts the application locally for live testing
Open agent - functional-reviewer
Compares code diff against acceptance criteria to find functional gaps, regression risks, and missing edge cases
Open agent - manual-validator
Guides manual test execution scenario by scenario and produces a structured validation report
Open agent - orchestrator
Routes QA tickets to the right agents in the right order — including environment setup and live browser validation
Open agent