Skills
2Files
0Web QA
Test a running web application through a real browser with a coding agent: exploratory testing with reproducible bug reports, console and network errors, performance traces, and regression tests written from the flows that were verified by hand.
Start with /web-qa-explore <url> (for example your local dev server) to explore the app and get a bug report, or /web-qa-regression <flow> to turn a flow into an end-to-end test in the project's own test framework. Browser work is delegated to the web-qa-tester subagent, so page snapshots stay out of the main conversation.
MCP servers: Playwright MCP (https://github.com/microsoft/playwright-mcp, Apache-2.0) drives the browser; Chrome DevTools MCP (https://github.com/ChromeDevTools/chrome-devtools-mcp, Apache-2.0) adds performance traces and network and console inspection, and is configured with Google's usage statistics turned off.
Prerequisites: Node.js and a local Chrome. No account or API key.
The skills and the agent are written by Athenode. For testing applications you own or are authorized to test.
AGENTS.md
Web QA
- Test only applications the user owns or is authorized to test, and prefer a local or staging environment. Ask before testing against production, and never run load or destructive tests there.
- Ask before any action that cannot be undone or reaches real people: deleting data, sending email or messages, making payments, changing account settings.
- Use test accounts the user provides. Never type real credentials into a page you were not told to sign in to, and never put credentials into a report or a test file; read them from environment variables.
Agents
1MCP servers
2- chrome-devtools
- playwright