Playwright Testing
CheckedHelps with Playwright, testing as part of testing, debugging, and quality assurance workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add chongdashu/phaserjs-oakwoods --skill playwright-testing -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
chongdashu
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned chongdashu/phaserjs-oakwoods at b3ccb0c31c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- b3ccb0c31c
- Scanned
- 11 files, 1,286 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill enables AI agents to execute automated browser testing using Playwright, a modern end-to-end testing framework. It allows agents to programmatically control browsers to verify application functionality across different environments.
When to use it
- Validate user flows and interactions on web applications without manual intervention.
- Run regression tests to ensure recent code changes do not break existing features.
- Perform cross-browser compatibility checks by simulating Chrome, Firefox, and WebKit.
- Generate visual regression reports to detect unintended UI layout shifts.
Key capabilities
- Automate browser actions including clicks, typing, and navigation.
- Support for multiple browsers (Chromium, Firefox, WebKit) out of the box.
- Ability to run tests in headless mode for faster CI/CD pipelines.
- Capture screenshots and trace logs for debugging failed test cases.
Example prompts
- "Run a Playwright test suite against my staging environment to check login functionality."
- "Execute a browser automation script that verifies the checkout process on my e-commerce site."
- "Generate a visual regression report comparing the latest build against the production version using Playwright."
Tips & gotchas
Ensure your AI agent has access to a browser installation or a headless environment before running tests. Limit test execution time in CI pipelines by configuring timeouts and parallelism settings within Playwright.