Agent skill

Adding E2E Tests

by spencerpauly in spencerpauly/awesome-cursor-skills

Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.

CC0-1.0Auto-check passedTesting & QA

Install Adding E2E Tests

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills adding-e2e-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/adding-e2e-tests .claude/skills/adding-e2e-tests && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "adding-e2e-tests" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests into .claude/skills/adding-e2e-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-e2e-tests", 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

$skill-installer install https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests

Type 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.

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills adding-e2e-tests --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/adding-e2e-tests .agents/skills/adding-e2e-tests && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "adding-e2e-tests" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests into .agents/skills/adding-e2e-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-e2e-tests", 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.

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills adding-e2e-tests --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/adding-e2e-tests .cursor/skills/adding-e2e-tests && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "adding-e2e-tests" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests into .cursor/skills/adding-e2e-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-e2e-tests", 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

$ gemini skills install https://github.com/spencerpauly/awesome-cursor-skills.git --path resources/adding-e2e-tests

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills adding-e2e-tests --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/adding-e2e-tests .gemini/skills/adding-e2e-tests && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "adding-e2e-tests" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests into .gemini/skills/adding-e2e-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-e2e-tests", 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.

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills adding-e2e-tests

Installs 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).

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/adding-e2e-tests .github/skills/adding-e2e-tests && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "adding-e2e-tests" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests into .github/skills/adding-e2e-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-e2e-tests", 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.

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills adding-e2e-tests --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/adding-e2e-tests .opencode/skills/adding-e2e-tests && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "adding-e2e-tests" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/adding-e2e-tests into .opencode/skills/adding-e2e-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-e2e-tests", 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: adding-e2e-tests
GitHub stars: 842
Token cost: ~522 tokens
SKILL.md length: 185 words
Files: 1
Skills in repo: 57
Repo updated: Aug 2, 2026
First seen: Oct 7, 2026
Licence: CC0-1.0

At a glance

Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.

Works in 7 steps: Install Playwright → Configure playwright.config.ts → Create a smoke test — write a basic test… → …
Tasks that involve End-to-end testing
SKILL.md covers Steps and Notes
Calls npm and npx

What it does

Adding E2E Tests is an agent skill from spencerpauly/awesome-cursor-skills. Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.

Its SKILL.md is about 520 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. The repository describes itself as: A curated list of awesome skills for Cursor. The licence is CC0-1.0.

When your agent uses it

Tasks that involve End-to-end testing
Tasks that involve Browser testing

Example prompts

“/adding-e2e-tests”

Requirements

Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Install Playwright
Configure playwright.config.ts
Create a smoke test — write a basic test that verifies the app loads
Add page object pattern (optional) — for larger apps, create a tests/pages/ directory with page objects that encapsulate selectors and…
Add npm scripts
Add to .gitignore
CI integration — add a GitHub Actions step that runs npx playwright install --with-deps then npm run test:e2e. Use the official…

What it can do on your machine

Read from SKILL.md and the folder at commit 99cd265. 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
Shell commands in SKILL.md call:
- npm
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.
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

Adding E2E Tests loads about 522 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 185 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~33
When it runs · the whole SKILL.md, loaded when a task matches: ~522

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 spencerpauly/awesome-cursor-skills at commit 99cd265, republished under its CC0-1.0 licence (© spencerpauly). 185 words, ~522 tokens.

Download SKILL.mdSave it as .claude/skills/adding-e2e-tests/SKILL.md (or your agent's skills folder).

name: adding-e2e-tests
description: Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.

Add E2E Tests (Playwright)

Use this skill when the user asks to add end-to-end tests, browser tests, integration tests, or set up Playwright.

Steps

Install Playwright
bash
```
npm init playwright@latest
```
This creates playwright.config.ts, a tests/ directory, and installs browsers. If the project already has a test runner, install manually:
bash
```
npm install -D @playwright/test
npx playwright install
```
Configure playwright.config.ts
- Set baseURL to the local dev server URL (e.g. http://localhost:3000).
- Configure webServer to start the dev server automatically:
  ts
```
webServer: {
  command: "npm run dev",
  url: "http://localhost:3000",
  reuseExistingServer: !process.env.CI,
},
```
- Enable only chromium for local dev speed; enable all browsers in CI.

Create a smoke test — write a basic test that verifies the app loads:

import { test, expect } from "@playwright/test";

test("homepage loads", async ({ page }) => {
  await page.goto("/");
  await expect(page).toHaveTitle(/.+/);
});

Add page object pattern (optional) — for larger apps, create a tests/pages/ directory with page objects that encapsulate selectors and actions.

Add npm scripts

json

{
  "test:e2e": "playwright test",
  "test:e2e:ui": "playwright test --ui"
}

Add to .gitignore

test-results/
playwright-report/
blob-report/

CI integration — add a GitHub Actions step that runs npx playwright install --with-deps then npm run test:e2e. Use the official actions/upload-artifact to save the HTML report on failure.

Notes

Use data-testid attributes for selectors instead of CSS classes.
Use test.describe to group related tests.
Run npx playwright codegen to record tests interactively.

Files

Just SKILL.md in resources/adding-e2e-tests of spencerpauly/awesome-cursor-skills.

Open the folder on GitHubat commit 99cd265

Compare with similar skills

Adding E2E Tests 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.

Adding E2E Tests compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Adding E2E Tests this skillspencerpauly/awesome-cursor-skills	842	—	~522	Automated safety check: Pass	CC0-1.0	2 mo ago
Web Application Testinganthropics/skills	180k	51 repos	~966	Automated safety check: Pass	Apache-2.0	3 days ago
playwright-cli Browser Automationgithub/gh-aw	5.4k	24 repos	~2.8k	Automated safety check: Pass	MIT	today
Write and Verify Playwright Testsappsmithorg/appsmith	41k	—	~2.9k	Automated safety check: Notes	Apache-2.0	today
Cucumber and Playwright E2E Testslanggenius/dify	158k	—	~682	Automated safety check: Pass	Custom licence	today
E2E Testinglangflow-ai/langflow	156k	—	~3.3k	Automated safety check: Pass	MIT	today

Similar skills

Web Application Testing
anthropics/skills
Official
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
180k GitHub starsUsed in 51 repos~966 tokens
Testing & QAAuto-check passed
playwright-cli Browser Automation
github/gh-aw
Official
Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.
5.4k GitHub starsUsed in 24 repos~2.8k tokens
Testing & QAAuto-check passed
Write and Verify Playwright Tests
appsmithorg/appsmith
Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.
41k GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check: notes
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
158k GitHub stars~682 tokensUpdated today
Testing & QAAuto-check passed
E2E Testing
langflow-ai/langflow
Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.
156k GitHub stars~3.3k tokensUpdated today
Testing & QAAuto-check passed
Handsontable Playwright E2E Tests
handsontable/handsontable
Guides writing and changing Playwright end-to-end tests for Handsontable using page objects, data-testid hooks and deterministic waits.
22k GitHub stars~1.8k tokensUpdated today
Testing & QAAuto-check passed

Questions about Adding E2E Tests

What does Adding E2E Tests do?

Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration. Adding E2E Tests is an agent skill from spencerpauly/awesome-cursor-skills. Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.

When should I use Adding E2E Tests?

Adding E2E Tests fits situations like: tasks that involve End-to-end testing; tasks that involve Browser testing.

How do I install Adding E2E Tests in Claude Code?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a claude-code`. Or copy the skill folder (resources/adding-e2e-tests in spencerpauly/awesome-cursor-skills) into .claude/skills/adding-e2e-tests in your project. Claude Code loads it when a task matches its description.

How do I install Adding E2E Tests in Codex?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a codex`. Or copy the skill folder (resources/adding-e2e-tests in spencerpauly/awesome-cursor-skills) into .agents/skills/adding-e2e-tests in your project. Codex loads it when a task matches its description.

Can I use Adding E2E Tests 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 spencerpauly/awesome-cursor-skills --skill adding-e2e-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-e2e-tests, .gemini/skills/adding-e2e-tests, .github/skills/adding-e2e-tests and .opencode/skills/adding-e2e-tests in your project.

What does Adding E2E Tests need to run?

Going by SKILL.md and its folder, Adding E2E Tests needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.

Does Adding E2E Tests access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Adding E2E Tests 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 Adding E2E Tests use?

Adding E2E Tests is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Adding E2E Tests use?

About 522 tokens (SKILL.md is roughly 2.1k 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 Adding E2E Tests?

Skills that share tags, products or a category with Adding E2E Tests: Web Application Testing (anthropics/skills, 180k stars), playwright-cli Browser Automation (github/gh-aw, 5.4k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars) and Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Adding E2E Tests?

spencerpauly (a GitHub user) maintains it in spencerpauly/awesome-cursor-skills, which has 842 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 2, 2026.

Source: spencerpauly/awesome-cursor-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Adding E2E Tests

Install Adding E2E Tests

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Add E2E Tests (Playwright)

Steps

Notes

Files

Compare with similar skills

Similar skills

Web Application Testing

playwright-cli Browser Automation

Write and Verify Playwright Tests

Cucumber and Playwright E2E Tests

E2E Testing

Handsontable Playwright E2E Tests

More from spencerpauly/awesome-cursor-skills

Babysitting PR

Best Of N Solving

Grinding Until Pass

Parallel CI Triage

Parallel Exploring

Profiling Performance

Questions about Adding E2E Tests

Install Adding E2E Tests

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Add E2E Tests (Playwright)

Steps

Notes

Files

Compare with similar skills

Similar skills

More from spencerpauly/awesome-cursor-skills

Related

Questions about Adding E2E Tests