Playwright E2E Tests
onyx-dot-app/onyx
Write and maintain Playwright end-to-end tests for the Onyx application.
Create, maintain, and verify end-to-end (E2E) tests using Playwright MCP.
Install Write E2E Test
$ npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitovi/ai-enablement-prompts write-e2e-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/playwright/skills/write-e2e-test .claude/skills/write-e2e-test && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-e2e-test" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-test into .claude/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitovi/ai-enablement-prompts write-e2e-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/playwright/skills/write-e2e-test .agents/skills/write-e2e-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-e2e-test" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-test into .agents/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitovi/ai-enablement-prompts write-e2e-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/playwright/skills/write-e2e-test .cursor/skills/write-e2e-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-e2e-test" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-test into .cursor/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bitovi/ai-enablement-prompts.git --path plugins/playwright/skills/write-e2e-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitovi/ai-enablement-prompts write-e2e-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/playwright/skills/write-e2e-test .gemini/skills/write-e2e-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-e2e-test" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-test into .gemini/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bitovi/ai-enablement-prompts write-e2e-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/playwright/skills/write-e2e-test .github/skills/write-e2e-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-e2e-test" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-test into .github/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitovi/ai-enablement-prompts write-e2e-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitovi/ai-enablement-prompts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/playwright/skills/write-e2e-test .opencode/skills/write-e2e-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-e2e-test" agent skill from https://github.com/bitovi/ai-enablement-prompts/tree/main/plugins/playwright/skills/write-e2e-test into .opencode/skills/write-e2e-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-e2e-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
write-e2e-test- GitHub stars
- 121
- Token cost
- ~476 tokens
- SKILL.md length
- 227 words
- Files
- 1
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create, maintain, and verify end-to-end (E2E) tests using Playwright MCP.
- Works in 5 steps: Identify Test Scenarios → Set Up Playwright MCP → Write E2E Test → …
- Flow needs E2E coverage
- SKILL.md covers Purpose, When to Use, Workflow and Checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Write E2E Test is an agent skill from bitovi/ai-enablement-prompts. Create, maintain, and verify end-to-end (E2E) tests using Playwright MCP. Use when a new feature or flow needs E2E coverage, when updating flows, or verifying UI and functional correctness.
Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering End-to-end testing and Browser testing. It works with Playwright and Model Context Protocol. The repository describes itself as: Prompts Bitovi uses for software development. The licence is MIT.
When your agent uses it
- Flow needs E2E coverage
- Verifying UI and functional correctness
Example prompts
- “/write-e2e-test”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify Test Scenarios
- Set Up Playwright MCP
- Write E2E Test
- Run and Verify
- Maintain and Document
What it can do on your machine
Read from SKILL.md and the folder at commit df229b1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Write E2E Test loads about 476 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 227 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bitovi/ai-enablement-prompts at commit df229b1, republished under its MIT licence (© bitovi). 227 words, ~476 tokens.
Download SKILL.mdSave it as
.claude/skills/write-e2e-test/SKILL.md (or your agent's skills folder).- name
- write-e2e-test
- description
- Create, maintain, and verify end-to-end (E2E) tests using Playwright MCP. Use when a new feature or flow needs E2E coverage, when updating flows, or verifying UI and functional correctness.
Write E2E Test Skill
Purpose
Guide the creation, maintenance, and verification of end-to-end (E2E) tests using Playwright MCP.
When to Use
- A new feature or flow is implemented and needs E2E coverage
- Updating or refactoring existing flows
- Verifying UI and functional correctness across user journeys
Workflow
Identify Test Scenarios
- Review the feature spec, user story, or acceptance criteria
- List critical user journeys, edge cases, and error paths
Set Up Playwright MCP
- Ensure Playwright MCP is configured
- Start the dev server if not already running
Write E2E Test
- Create a new Playwright test file in the appropriate directory (e.g.,
e2e/) - Use Playwright MCP to record or script the test, covering:
- Main user flows
- Edge cases and error handling
- Visual verification (screenshots, assertions)
- Use sample data generators for realistic test data where available
- Create a new Playwright test file in the appropriate directory (e.g.,
Run and Verify
- Execute the E2E test(s) against the running app
- Use Playwright MCP to:
- Validate UI state and visual correctness
- Assert expected outcomes and error messages
- Fix any issues or update tests as needed
Maintain and Document
- Update tests when features or flows change
- Document test coverage and known gaps
Checklist
- Test scenarios identified from feature spec/user story
- Playwright MCP configured and running
- E2E test file created
- Main flows, edge cases, and errors covered
- Visual and functional assertions included
- Test passes against running app
- Test documented and referenced in feature/skill
© bitovi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/playwright/skills/write-e2e-test of bitovi/ai-enablement-prompts.
Open the folder on GitHubat commit df229b1
Compare with similar skills
Write E2E Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write E2E Test this skillbitovi/ai-enablement-prompts | 121 | — | ~476 | Automated safety check: Pass | MIT | |
| Playwright E2E Testsonyx-dot-app/onyx | 32k | 1 repos | ~2.8k | Automated safety check: Notes | Custom licence | |
| E2E VerificationChorus-AIDLC/Chorus | 1.2k | — | ~1.5k | Automated safety check: Notes | AGPL-3.0 | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None | |
| Frontend Playwright E2Eansible/ansible-ui | 113 | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Playwright POM Discoverycomet-ml/opik | 22k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
E2E Verification
Chorus-AIDLC/Chorus
A skill your agent uses when manually verifying a Chorus frontend change in a real browser — finding local login credentials, driving the running dev server with the Playwright MCP, logging in…
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Frontend Playwright E2E
ansible/ansible-ui
Write, run, and debug Playwright E2E / integration / live tests.
Playwright POM Discovery
comet-ml/opik
Procedure for choosing stable selectors when building Page Object Models for the Opik E2E suite by exploring the live UI with the Playwright MCP.
Dev Webtest
classmethod/tsumiki
This skill should be used when the user asks to "dev-webtest", "Webテスト", "画面の動作確認", "E2Eテスト", "web test", "visual check", "モンキーテスト", "アクセシビリティチェック", "レスポンシブテスト", "フォームテスト".
More from bitovi/ai-enablement-prompts
All 40 skills in this repoComponent Registry
bitovi/ai-enablement-prompts
Track reusable UI components and unextracted patterns. An agent skill from bitovi/ai-enablement-prompts.
Computed Styles
bitovi/ai-enablement-prompts
Extract and compare computed CSS styles between a baseline URL and a dev/Storybook URL using Playwright MCP evaluate calls.
Create Plugin
bitovi/ai-enablement-prompts
A skill your agent uses when the user asks to "create a plugin", "add a plugin", "make a new plugin", "build a plugin", or wants to package skills into an installable plugin for this marketplace.
Create React Modlet
bitovi/ai-enablement-prompts
Create React components, hooks, or utilities following the modlet pattern.
Create Skill
bitovi/ai-enablement-prompts
A skill your agent uses when the user asks to "create a skill", "add a skill", "make a new skill", "build a skill", or wants to automate a repeated workflow into a reusable prompt.
Create Skill
bitovi/ai-enablement-prompts
Create new Agent Skills for this project. An agent skill from bitovi/ai-enablement-prompts.
Related
Works with
Categories
Questions about Write E2E Test
What does Write E2E Test do?
Create, maintain, and verify end-to-end (E2E) tests using Playwright MCP. Write E2E Test is an agent skill from bitovi/ai-enablement-prompts. Create, maintain, and verify end-to-end (E2E) tests using Playwright MCP.
When should I use Write E2E Test?
Write E2E Test fits situations like: flow needs E2E coverage; verifying UI and functional correctness.
How do I install Write E2E Test in Claude Code?
Run `npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a claude-code`. Or copy the skill folder (plugins/playwright/skills/write-e2e-test in bitovi/ai-enablement-prompts) into .claude/skills/write-e2e-test in your project. Claude Code loads it when a task matches its description.
How do I install Write E2E Test in Codex?
Run `npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a codex`. Or copy the skill folder (plugins/playwright/skills/write-e2e-test in bitovi/ai-enablement-prompts) into .agents/skills/write-e2e-test in your project. Codex loads it when a task matches its description.
Can I use Write E2E Test in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitovi/ai-enablement-prompts --skill write-e2e-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-e2e-test, .gemini/skills/write-e2e-test, .github/skills/write-e2e-test and .opencode/skills/write-e2e-test in your project.
What does Write E2E Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Write E2E Test is instructions for the agent only.
Does Write E2E Test access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write E2E Test safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write E2E Test use?
Write E2E Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write E2E Test use?
About 476 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Write E2E Test?
Skills that share tags, products or a category with Write E2E Test: Playwright E2E Tests (onyx-dot-app/onyx, 32k stars), E2E Verification (Chorus-AIDLC/Chorus, 1.2k stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars) and Frontend Playwright E2E (ansible/ansible-ui, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write E2E Test?
bitovi (a GitHub organization) maintains it in bitovi/ai-enablement-prompts, which has 121 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on September 11, 2026.
Source: bitovi/ai-enablement-prompts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.