Automated summary
Generates, reviews, and fixes Playwright E2E tests using predefined conventions and patterns.
Strengths
- Enforces consistent test structure with Page Object Model
- Provides scaffolding for new tests and page objects
- Includes guides for locators, assertions, and POM patterns
- Automates code review of existing tests
Limitations
- Requires existing Playwright setup and configuration
- Only works within projects that have the Playwright skill configured
- May not cover all custom testing scenarios
Use when adding new E2E tests or refactoring existing ones to follow Playwright best practices.
Do not use for unit tests or integration tests, or when a custom testing framework is in place.
Security analysis
SafeThe skill only references local files and templates for Playwright testing conventions; it does not invoke any external tools, scripts, or dangerous commands.
No concerns found
How this analysis is madeExamples
/playwrightskill/playwrightskill scaffold LoginPage/playwrightskill review/playwrightskill
Invoke the Playwright skill to write, fix, scaffold, or review E2E tests in this repository.
Usage:
/playwrightskill— apply all Playwright conventions to the current task/playwrightskill scaffold <PageName>— generate a new spec + POM pair/playwrightskill review— review open test files for violations
When this skill is invoked, load and follow all rules in .claude/commands/playwright-skill/SKILL.md.
Reference locator patterns from references/locator-guide.md, assertion patterns from references/assertion-guide.md, and POM patterns from references/pom-guide.md.
Use templates in assets/ as the starting point for any new files.
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-mrwake2o/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-mrwake2o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/playwright-skill-mrwake2o/download' --output '.skill-downloads/playwright-skill-mrwake2o/SKILL.md.part' && mv '.skill-downloads/playwright-skill-mrwake2o/SKILL.md.part' '.skill-downloads/playwright-skill-mrwake2o/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
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual 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-mrwake2o/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.