Playwright Pro

What it does

When your agent uses it

• The user mentions Playwright tests
• End-to-end testing
• Browser automation
• Fixing flaky tests

Example prompts

• “/playwright-pro”

Requirements

• Node.js
• A credential in TESTRAIL_API_KEY
• A credential in BROWSERSTACK_ACCESS_KEY

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

1. 1getByRole() over CSS/XPath — resilient to markup changes
2. 2Never page.waitForTimeout() — use web-first assertions
3. 3expect(locator) auto-retries; expect(await locator.textContent()) does not
4. 4Isolate every test — no shared state between tests
5. 5baseURL in config — zero hardcoded URLs
6. 6Retries: 2 in CI, 0 locally
7. 7Traces: 'on-first-retry' — rich debugging without slowdown
8. 8Fixtures over globals — test.extend() for shared state
9. 9One behavior per test — multiple related assertions are fine
10. 10Mock external services only — never mock your own app

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npx
  • npm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • TESTRAIL_API_KEY
  • BROWSERSTACK_ACCESS_KEY

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Playwright Pro loads about 1.4k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 436 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~90

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 436 words, ~1,414 tokens.

name

playwright-pro

description

Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.

1. /pw:pw-init          → scaffolds config, CI pipeline, and a first smoke test
2. /pw:generate      → generates tests from your spec or URL
3. /pw:pw-review        → validates quality and flags anti-patterns      ← always run after generate
4. /pw:fix <test>    → diagnoses and repairs any failing/flaky tests  ← run when CI turns red

# 1. Generate tests from a user story
/pw:generate "As a user I can log in with email and password"

# Generated: tests/auth/login.spec.ts
# → Playwright Pro creates the file using the auth template.

# 2. Review the generated tests
/pw:pw-review tests/auth/login.spec.ts

# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')
# → Fix applied automatically.

# 3. Run locally to confirm
npx playwright test tests/auth/login.spec.ts --headed

# 4. If a test is flaky in CI, diagnose it
/pw:fix tests/auth/login.spec.ts
# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()

1. getByRole()        — buttons, links, headings, form elements
2. getByLabel()       — form fields with labels
3. getByText()        — non-interactive text
4. getByPlaceholder() — inputs with placeholder
5. getByTestId()      — when no semantic option exists
6. page.locator()     — CSS/XPath as last resort

export TESTRAIL_URL="https://your-instance.testrail.io"
export TESTRAIL_USER="your@email.com"
export TESTRAIL_API_KEY="your-api-key"

export BROWSERSTACK_USERNAME="your-username"
export BROWSERSTACK_ACCESS_KEY="your-access-key"

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 71 other files in engineering-team/playwright-pro/skills/pw of alirezarezvani/claude-skills.

• SKILL.md
• reference/assertions.md
• reference/common-pitfalls.md
• reference/fixtures.md
• reference/flaky-tests.md
• reference/golden-rules.md
• reference/locators.md
• templates/README.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/api/rest-crud.md
• templates/auth
• … and 55 more

Open the folder on GitHubat commit 19392f7

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.

• LeoYeAI/openclaw-master-skillsskills/cs-pwskills/playwright-pro+1 more