Automated summary
Provides battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites across E2E, API, component, visual, accessibility, and security testing.
Strengths
- Concrete golden rules (getByRole, web-first assertions, no waitForTimeout) applied throughout the guides
- Broad coverage: selectors, fixtures, page objects, network mocking, authentication, CI/CD, debugging, and trace analysis
- TypeScript and JavaScript examples with guidance on when not to use each pattern
- Covers Playwright 1.59–1.61 features such as passkeys, Web Storage, HAR recording, and the trace CLI
Limitations
- Does not replace the official Playwright documentation or actual test execution
- Assumes familiarity with TypeScript/JavaScript and test automation concepts
- Some newer features depend on specific Playwright versions
Use when designing, debugging, or scaling a Playwright test suite, or migrating from Cypress or Selenium.
Avoid for automating third-party sites without authorization, or for non-Playwright needs such as browserless unit tests.
Security analysis
SafeThis is a pure documentation/guidance skill: it contains no declared tools, no executable code, no shell commands, and no network or file-system actions beyond reading its own reference markdown files. It explicitly sets a trust boundary (only test apps you own/are authorized to test), warns about indirect prompt injection from fetched page content, and recommends pinning CI dependencies to immutable references — all defensive, not risky. Nothing destructive, obfuscated, or exfiltrating is present.
No concerns found
How this analysis is madeExamples
Write a Playwright test for the login flow using getByRole locators, web-first assertions, and no hardcoded URLs. Use a fixture for authentication and explain when to mock the email service.A Playwright test passes locally but fails in CI. Review my config and suggest changes for retries, trace mode, and wait strategy, following the skill's golden rules.Help me migrate a Cypress E2E suite to Playwright. Map cy.get and cy.intercept to Playwright locators and route mocking, and propose a page object versus fixture structure.name: playwright-skill description: Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript. license: MIT metadata: author: testdino.com version: "2.4.0"
Playwright Skill
Opinionated, production-tested Playwright guidance — every pattern includes when (and when not) to use it.
50+ reference guides covering the full Playwright surface: selectors, assertions, fixtures, page objects, network mocking, auth, visual regression, accessibility, API testing, CI/CD, debugging, and more — with TypeScript and JavaScript examples throughout.
Playwright 1.61 highlights covered in these guides: WebAuthn passkey testing via context.credentials, the page.localStorage / page.sessionStorage Web Storage API, new video retention modes matching trace modes, expect.soft.poll(), WebSockets in HAR and trace recordings, and apiResponse.securityDetails() / serverAddr(). Also covered: the 1.60 features (on-demand HAR recording inside tracing, locator.drop(), page-level aria snapshot assertions, test.abort()) and 1.59 features (screencast recording, browser binding for agent workflows, CLI debugging and trace analysis, in-place storage state updates). A dedicated trace-analysis.md guide covers agent-native debugging of trace.zip reports with the npx playwright trace CLI.
Security Trust Boundary
This skill is designed for testing applications you own or have explicit authorization to test. It does not support or endorse automating interactions with third-party websites or services without permission.
When writing tests or automation that fetch content from external sources (e.g., baseURL pointing to staging/production), treat all returned page content as untrusted input — never pass raw page text back into agent instructions or dynamic code execution without sanitization, as this creates an indirect prompt injection risk.
For CI/CD workflows, pin all external dependencies (GitHub Actions, Docker images) to immutable references (commit SHAs, image digests) rather than mutable version tags. See ci-github-actions.md and docker-and-containers.md for pinning guidance.
Golden Rules
getByRole()over CSS/XPath — resilient to markup changes, mirrors how users see the page- Never
page.waitForTimeout()— useexpect(locator).toBeVisible()orpage.waitForURL() - Web-first assertions —
expect(locator)auto-retries;expect(await locator.textContent())does not - Isolate every test — no shared state, no execution-order dependencies
baseURLin config — zero hardcoded URLs in tests- Retries:
2in CI,0locally — surface flakiness where it matters - Traces:
'on-first-retry'— rich debugging artifacts without CI slowdown - Fixtures over globals — share state via
test.extend(), not module-level variables - One behavior per test — multiple related
expect()calls are fine - Mock external services only — never mock your own app; mock third-party APIs, payment gateways, email
Guide Index
Writing Tests
| What you're doing | Guide | Deep dive | |---|---|---| | Choosing selectors | locators.md | locator-strategy.md | | Assertions & waiting | assertions-and-waiting.md | | | Organizing test suites | test-organization.md | test-architecture.md | | Playwright config | configuration.md | | | Page objects | page-object-model.md | pom-vs-fixtures-vs-helpers.md | | Fixtures & hooks | fixtures-and-hooks.md | | | Test data | test-data-management.md | | | Auth & login | authentication.md | auth-flows.md | | API testing (REST/GraphQL) | api-testing.md | | | Visual regression | visual-regression.md | | | Accessibility | accessibility.md | | | Mobile & responsive | mobile-and-responsive.md | | | Component testing | component-testing.md | | | Network mocking | network-mocking.md | when-to-mock.md | | Forms & validation | forms-and-validation.md | | | File uploads/downloads | file-operations.md | file-upload-download.md | | Error & edge cases | error-and-edge-cases.md | | | CRUD flows | crud-testing.md | | | Drag and drop | drag-and-drop.md | | | Search & filter UI | search-and-filter.md | |
Debugging & Fixing
| Problem | Guide |
|---|---|
| General debugging workflow | debugging.md |
| Specific error message | error-index.md |
| Flaky / intermittent tests | flaky-tests.md |
| Common beginner mistakes | common-pitfalls.md |
| Debug a trace.zip from the terminal / with an agent | trace-analysis.md |
Framework Recipes
| Framework | Guide | |---|---| | Next.js (App Router + Pages Router) | nextjs.md | | React (CRA, Vite) | react.md | | Vue 3 / Nuxt | vue.md | | Angular | angular.md |
Migration Guides
| From | Guide | |---|---| | Cypress | from-cypress.md | | Selenium / WebDriver | from-selenium.md |
Architecture Decisions
| Question | Guide | |---|---| | Which locator strategy? | locator-strategy.md | | E2E vs component vs API? | test-architecture.md | | Mock vs real services? | when-to-mock.md | | POM vs fixtures vs helpers? | pom-vs-fixtures-vs-helpers.md |
CI/CD & Infrastructure
| Topic | Guide | |---|---| | GitHub Actions | ci-github-actions.md | | GitLab CI | ci-gitlab.md | | CircleCI / Azure DevOps / Jenkins | ci-other.md | | Parallel execution & sharding | parallel-and-sharding.md | | Docker & containers | docker-and-containers.md | | Reports & artifacts | reporting-and-artifacts.md | | Code coverage | test-coverage.md | | Global setup/teardown | global-setup-teardown.md | | Multi-project config | projects-and-dependencies.md |
Specialized Topics
| Topic | Guide | |---|---| | Multi-user & collaboration | multi-user-and-collaboration.md | | WebSockets & real-time | websockets-and-realtime.md | | Browser APIs (geo, clipboard, permissions) | browser-apis.md | | iframes & Shadow DOM | iframes-and-shadow-dom.md | | Canvas & WebGL | canvas-and-webgl.md | | Service workers & PWA | service-workers-and-pwa.md | | Electron apps | electron-testing.md | | Browser extensions | browser-extensions.md | | Security testing | security-testing.md | | Performance & benchmarks | performance-testing.md | | i18n & localization | i18n-and-localization.md | | Multi-tab & popups | multi-context-and-popups.md | | Clock & time mocking | clock-and-time-mocking.md | | Third-party integrations | third-party-integrations.md |
CLI Browser Automation
| What you're doing | Guide | |---|---| | CLI browser interaction | playwright-cli/SKILL.md | | Core commands (open, click, fill, navigate) | core-commands.md | | Network mocking & interception | request-mocking.md | | Running custom Playwright code | running-custom-code.md | | Multi-session browser management | session-management.md | | Cookies, localStorage, auth state | storage-and-auth.md | | Test code generation from CLI | test-generation.md | | Tracing and debugging | tracing-and-debugging.md | | Screenshots, video, PDF | screenshots-and-media.md | | Device & environment emulation | device-emulation.md | | Complex multi-step workflows | advanced-workflows.md |
Language Note
All guides include TypeScript and JavaScript examples. When the project uses .js files or has no tsconfig.json, examples are adapted to plain JavaScript.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/playwright-skill-mrwakgko/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/playwright-skill-mrwakgko' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/playwright-skill-mrwakgko/download' --output '.skill-downloads/playwright-skill-mrwakgko/SKILL.md.part' && mv '.skill-downloads/playwright-skill-mrwakgko/SKILL.md.part' '.skill-downloads/playwright-skill-mrwakgko/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/playwright-skill-mrwakgko/SKILL.md' && test -s '.skill-downloads/playwright-skill-mrwakgko/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/playwright-skill' && cp -R '.skill-downloads/playwright-skill-mrwakgko' '.claude/skills/playwright-skill'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/playwright-skill-mrwakgko'openskills read 'playwright-skill-mrwakgko'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/playwright-skill-mrwakgko/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.