Mehmet Kadir Güngör

You can automate browser interactions, test web pages, and work with Playwright test suites. The trace skill additionally lets you inspect trace files from the command line, listing actions, network requests, console logs, errors, snapshots, and screenshots for debugging failed runs.

They target QA engineers, test automation developers, and frontend engineers who write or debug Playwright browser tests. Anyone diagnosing flaky end-to-end tests or validating web page behavior from the command line benefits from the trace inspection and browser automation capabilities.

Both skills execute through Bash commands. The trace skill runs via npx to inspect trace files, while the browser skill uses playwright-cli, npx, and npm to automate interactions and manage tests. A working Node.js environment with Playwright installed is the runtime foundation.

You need Node.js with npm and npx available, plus Playwright and the playwright-cli package installed. For trace inspection, an existing Playwright trace file generated from a prior test run is required to list actions, requests, console output, and screenshots.

Yes. The skills build on Playwright, which is open-source under the Apache-2.0 license, and the skills themselves are published publicly in the registry at no cost. You only need a local Node.js environment; no paid subscriptions or proprietary services are required.