Playwright generate test
Skill ulpi-io/plugin-marketplace/plugins/github/skills/playwright-generate-test
Generate a Playwright test based on a scenario using Playwright MCPFrom its SKILL.md
npx -y skills add ulpi-io/plugin-marketplace --skill playwright-generate-testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, 153 tokens by cl100k_base, as published. Nobody here has run it
Test Generation with Playwright MCP
Your goal is to generate a Playwright test based on the provided scenario after completing all prescribed steps.
Specific Instructions
- You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.
- DO NOT generate test code prematurely or based solely on the scenario without completing all prescribed steps.
- DO run steps one by one using the tools provided by the Playwright MCP.
- Only after all steps are completed, emit a Playwright TypeScript test that uses
@playwright/testbased on message history - Save generated test file in the tests directory
- Execute the test file and iterate until the test passes
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most e2e browser skills give in 153 tokens
Counted across 408 of the 410 authors here whose files we hold, read 2026-08-07
- Use page object model patternin 34 of 408, across 24 files
- Keep tests independentin 24 of 408, across 19 files
- Interact using refs from the latest snapshotin 24 of 408, across 12 files
- Snapshot to get element refsin 24 of 408, across 14 files
- Clean up test data after each testin 20 of 408, across 14 files
- Test user behavior not implementationin 19 of 408, across 13 files
- Wait for specific network conditionsin 18 of 408, across 8 files
- Quarantine flaky tests explicitlyin 18 of 408, across 9 files
- Re-snapshot after navigation or DOM changesin 17 of 408, across 10 files
- Detect running dev servers before writing test codein 17 of 408, across 7 files
- Use web-first assertionsin 17 of 408, across 14 files
- Ask the user which server to test if multiple are foundin 15 of 408, across 5 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.