Playwright E2E Builder
CheckedAutomatically generates end-to-end playwright tests from user stories or requirements, streamlining test creation.
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 davila7/claude-code-templates --skill playwright-e2e-builder -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
davila7
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 davila7/claude-code-templates at 79182c51fb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 79182c51fb
- Scanned
- 1 file, 641 lines
About this skill
The playwright-e2e-builder skill automates the creation of robust end-to-end (E2E) testing suites using Playwright, enabling AI agents to generate scripts that verify full application workflows across different browsers. It streamlines the setup process by handling configuration files and defining test structures without requiring manual boilerplate coding.
When to use it
- You need to validate critical user journeys, such as login flows or checkout processes, across multiple browser environments simultaneously.
- Your development team requires automated regression testing to ensure new code changes do not break existing functionality.
- You want to rapidly prototype test cases for a web application before investing in complex CI/CD pipeline integrations.
- You are building an AI agent workflow that needs to inspect dynamic DOM elements and simulate real user interactions like clicking, typing, or waiting for network requests.
Key capabilities
- Generates Playwright configuration files tailored to specific project needs.
- Creates test scripts that interact with web pages using modern selectors and locators.
- Supports cross-browser testing setups including Chrome, Firefox, and WebKit.
- Facilitates the definition of E2E test suites that cover complete application scenarios from start to finish.
Example prompts
- "Create a Playwright E2E test suite for my e-commerce site that verifies the 'Add to Cart' and 'Checkout' flows on both desktop and mobile views."
- "Generate a configuration file and initial test script using Playwright to automate login verification across Chrome and Firefox browsers."
- "Write an end-to-end test case that simulates a user signing up, uploading a profile picture, and verifying the success message appears correctly."
Tips & gotchas
Ensure your target web application is stable and accessible before running generated E2E tests, as browser automation can be sensitive to dynamic content loading delays. While this skill excels at generating boilerplate and structure, you may need to manually refine selectors if the application relies heavily on non-standard or rapidly changing DOM structures.