“Playwright”

Automate real browsers from the terminal for navigation, forms, screenshots, extraction, and UI debugging using playwright-cli.

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging)…

Use when user says "does it work?", "screenshot the page", "show me the form", "check the checkout flow", or "open the browser".

Read before driving the locally running apps: verifying a change in the browser, calling the API, authenticating as an admin, or driving the mobile app.

QA engineering workflows on top of Playwright.

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code…

Automates browser interactions for testing and validating your own web applications using playwright-cli.

Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.

Generate robust, zero-flakiness Playwright E2E tests following OpenMetadata patterns.

Production-grade Playwright testing toolkit.

Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests.

Playwright Tools.

Complete browser automation with Playwright.

Automates browser interactions for web testing, form filling, screenshots, and data extraction.

Headless, invisible Playwright browser over MCP for scripted automation - testing and verifying web apps, scripted data extraction, accessibility snapshots…

Use when validating UI changes in a branch require Playwright E2E testing.

End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration.

Redirect only — this skill was merged into `playwright`.

Drives a live browser through the global `playwright-cli` command to inspect, interact with and capture web pages.

Record browser interactions as video using Playwright.

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests.

Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags…

Automate browser interactions, test web pages and work with Playwright tests.

Use when navigating, testing, or verifying a RHDH instance via playwright-cli.