Skip to content

Playwright Pro Testing Toolkit

Lets your AI agent write, review, fix and migrate Playwright end-to-end browser tests

Stars
29,149
Licence
MIT
Files
15 files

What it does

Once installed, the agent knows how to work on Playwright end-to-end tests for web apps. It can generate test files from a user story or URL, review them for weak locators and missing assertions, diagnose and repair failing or flaky tests, and help migrate suites from Cypress or Selenium. It follows a set of built-in best-practice rules, such as preferring role-based locators and auto-retrying web-first assertions instead of fixed timeouts. Optional commands can also sync with TestRail and run tests on BrowserStack, but those need extra setup and API credentials.

Great for

  • Developers who want Playwright tests written and reviewed to a consistent standard
  • Teams fixing flaky or failing end-to-end tests in CI
  • Engineers migrating an existing Cypress or Selenium suite to Playwright

Skip it if

  • Teams with no web app or browser-based UI to test, since the skill is specific to Playwright
  • Users who want the TestRail or BrowserStack integrations without setup: the files say those MCP servers are not auto-registered and must be enabled manually, and the commands fail until then
  • Anyone running it against production systems without review, since generated or auto-fixed tests are edited in the project and should be checked before committing

Try asking

  • “Generate Playwright tests for this user story: as a user I can reset my password by email”
  • “Review tests/checkout/payment.spec.ts for anti-patterns and missing assertions”
  • “Fix the flaky test in tests/search/filters.spec.ts that fails only in CI”
  • “Migrate our Cypress login tests to Playwright and check coverage parity”
Step-by-step guide: how to use Playwright Pro Testing ToolkitInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 15 original files, the MIT licence and an attribution note.

    pw.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip pw.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip pw.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Always run /pw:pw-review after /pw:generate before committing, as the skill itself recommends
  • Re-run the full suite locally after /pw:fix to catch regressions
  • Keep TestRail and BrowserStack credentials in environment variables rather than in files, and only enable those integrations if you need them

What's inside

  • reference/assertions.md
  • reference/common-pitfalls.md
  • reference/fixtures.md
  • reference/flaky-tests.md
  • reference/golden-rules.md
  • reference/locators.md
  • SKILL.md
  • templates/accessibility/color-contrast.md
  • templates/accessibility/keyboard-navigation.md
  • templates/accessibility/screen-reader.md
  • templates/api/auth-headers.md
  • templates/api/error-responses.md
  • templates/api/graphql.md
  • templates/api/rate-limiting.md
  • templates/README.md

Redistributed unmodified from alirezarezvani/claude-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.