webapp-testing
Drive a running web application in a browser and report the visible behaviour of a flow.
npx skills add anthropics/skills --skill webapp-testingWrite tests, drive a browser against a running app and verify a change before calling it done.
Start with the layer that is actually broken: missing tests, a flaky suite, or a claim of success nobody verified.
Drive a running web application in a browser and report the visible behaviour of a flow.
npx skills add anthropics/skills --skill webapp-testingSelector and waiting strategy for Playwright suites that have become flaky.
npx skills add currents-dev/playwright-best-practices-skill --skill playwright-best-practicesRecord a browser flow you performed by hand, then replay it as a script.
npx skills add microsoft/playwright-cli --skill playwright-cliNavigate a live page and read a snapshot of what is actually rendered.
npx skills add vercel-labs/agent-browser --skill agent-browserWork in failing-test, passing-test cycles instead of writing tests after the implementation.
npx skills add mattpocock/skills --skill tddA failing test first, then the change, as part of a workflow that ends in verification.
npx skills add obra/superpowers --skill test-driven-developmentNo skill in this category has a full write-up yet.
A testing skill fixes the thing agents do most often wrong: they claim a change works without running anything. The skills on this page cover the three layers of that problem — writing the test, driving the browser to prove the flow, and refusing to call the work finished on stale output.
webapp-testing (anthropics) — exercises a running application in a browser and reports what it saw. It needs the app running; pointed at a stopped process it reports connection errors as findings.playwright-best-practices (currents-dev) — the one to install when the suite exists and is flaky. It is about selectors and waiting strategy: wait for a stable condition, never a fixed number of seconds.playwright-cli (microsoft) — record a flow you perform by hand, then replay it as a script. Record first, script second; a script written from a description is a guess.tdd (mattpocock) — failing test, then passing test. The failing run is the evidence the test measures something.test-driven-development (obra) — the same discipline inside a workflow that ends in verification, which is what you want when several agents touch one repository.waitForTimeout(2000) works on your machine and fails in CI. Wait for state, not time.Do I need both webapp-testing and playwright-best-practices? Yes, for different jobs: the first drives a browser to check behaviour, the second keeps an existing suite from going flaky. Install the second when your CI is already lying to you.
Can it test without a running server? No. Every skill on this page needs the application up. Start it yourself and confirm the URL responds before the run.
Will the agent write the tests I am missing? It will write them from your description of the behaviour. The description is the work — a vague one produces tests that assert on rendering.
How many tests should a change come with? One failing test that proves the bug or the new behaviour, plus the existing suite still passing. More than that is usually scope creep.
What if a test is flaky? Fix the wait or the selector. Skipping it converts a known problem into an unknown one.