Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Write or update the repository's Playwright E2E tests. An agent skill from PrairieLearn/PrairieLearn.
Install Playwright Testing
$ npx skills add PrairieLearn/PrairieLearn --skill playwright-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PrairieLearn/PrairieLearn playwright-testing --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/PrairieLearn/PrairieLearn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/playwright-testing .claude/skills/playwright-testing && 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 "playwright-testing" agent skill from https://github.com/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testing into .claude/skills/playwright-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-testing", 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/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testingType 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 PrairieLearn/PrairieLearn --skill playwright-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PrairieLearn/PrairieLearn playwright-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PrairieLearn/PrairieLearn.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/playwright-testing .agents/skills/playwright-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "playwright-testing" agent skill from https://github.com/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testing into .agents/skills/playwright-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-testing", 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 PrairieLearn/PrairieLearn --skill playwright-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PrairieLearn/PrairieLearn playwright-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PrairieLearn/PrairieLearn.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/playwright-testing .cursor/skills/playwright-testing && 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 "playwright-testing" agent skill from https://github.com/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testing into .cursor/skills/playwright-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-testing", 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/PrairieLearn/PrairieLearn.git --path .agents/skills/playwright-testing--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 PrairieLearn/PrairieLearn --skill playwright-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PrairieLearn/PrairieLearn playwright-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PrairieLearn/PrairieLearn.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/playwright-testing .gemini/skills/playwright-testing && 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 "playwright-testing" agent skill from https://github.com/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testing into .gemini/skills/playwright-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-testing", 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 PrairieLearn/PrairieLearn playwright-testingInstalls 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 PrairieLearn/PrairieLearn --skill playwright-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PrairieLearn/PrairieLearn.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/playwright-testing .github/skills/playwright-testing && 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 "playwright-testing" agent skill from https://github.com/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testing into .github/skills/playwright-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-testing", 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 PrairieLearn/PrairieLearn --skill playwright-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PrairieLearn/PrairieLearn playwright-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PrairieLearn/PrairieLearn.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/playwright-testing .opencode/skills/playwright-testing && 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 "playwright-testing" agent skill from https://github.com/PrairieLearn/PrairieLearn/tree/master/.agents/skills/playwright-testing into .opencode/skills/playwright-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-testing", 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
playwright-testing- GitHub stars
- 512
- Token cost
- ~280 tokens
- SKILL.md length
- 136 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write or update the repository's Playwright E2E tests. An agent skill from PrairieLearn/PrairieLearn.
- Tasks that involve Browser testing
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve End-to-end testing
What it does
Playwright Testing is an agent skill from PrairieLearn/PrairieLearn. Write or update the repository's Playwright E2E tests.
Its SKILL.md is about 280 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 Browser testing and End-to-end testing. It works with Playwright. The repository describes itself as: Online problem-driven learning system.
When your agent uses it
- Tasks that involve Browser testing
- Tasks that involve End-to-end testing
Example prompts
- “/playwright-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit 076bf1b. 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
Playwright Testing loads about 280 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 136 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 136 words (~280 tokens).
“New E2E tests should be created in apps/prairielearn/src/tests/e2e. Each test file should be named *.spec.{ts,tsx} and contain tests for a specific feature or user flow.”
- name
- playwright-testing
Files
Just SKILL.md in .agents/skills/playwright-testing of PrairieLearn/PrairieLearn.
Open the folder on GitHubat commit 076bf1b
Compare with similar skills
Playwright Testing 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 |
|---|---|---|---|---|---|---|
| Playwright Testing this skillPrairieLearn/PrairieLearn | 512 | — | ~280 | Automated safety check: Pass | Custom licence | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| playwright-cli Browser Automationgithub/gh-aw | 5.3k | 23 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Write and Verify Playwright Testsappsmithorg/appsmith | 41k | — | ~2.9k | Automated safety check: Notes | Apache-2.0 | |
| Cucumber and Playwright E2E Testslanggenius/dify | 158k | — | ~682 | Automated safety check: Pass | Custom licence | |
| E2E Testinglangflow-ai/langflow | 156k | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
playwright-cli Browser Automation
github/gh-aw
Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.
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.
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.
E2E Testing
langflow-ai/langflow
Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.
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.
More from PrairieLearn/PrairieLearn
Element Runtime Assets
PrairieLearn/PrairieLearn
A skill your agent uses when creating a new PrairieLearn element or changing an element's runtime dependencies, scripts, styles, or bundled assets.
Element Validation
PrairieLearn/PrairieLearn
A skill your agent uses when changing or reviewing PrairieLearn element question.html contracts, including schema-level attributes/children, Python semantic validation, docs, and AI HTML validation…
Express Request Validation
PrairieLearn/PrairieLearn
Conventions for validating PrairieLearn Express request parameters, query strings, bodies, and action forms with Zod.
Trpc
PrairieLearn/PrairieLearn
Conventions for writing tRPC routers and procedures. An agent skill from PrairieLearn/PrairieLearn.
Element Backwards Compat
PrairieLearn/PrairieLearn
Backwards compatibility rules when changing element controllers in apps/prairielearn/elements/.
Groups And Teams
PrairieLearn/PrairieLearn
Dealing with groups and teams in PrairieLearn, and confusion about table/column/variable names.
Related
Works with
Categories
Questions about Playwright Testing
What does Playwright Testing do?
Write or update the repository's Playwright E2E tests. An agent skill from PrairieLearn/PrairieLearn. Playwright Testing is an agent skill from PrairieLearn/PrairieLearn. Write or update the repository's Playwright E2E tests.
When should I use Playwright Testing?
Playwright Testing fits situations like: tasks that involve Browser testing; tasks that involve End-to-end testing.
How do I install Playwright Testing in Claude Code?
Run `npx skills add PrairieLearn/PrairieLearn --skill playwright-testing -a claude-code`. Or copy the skill folder (.agents/skills/playwright-testing in PrairieLearn/PrairieLearn) into .claude/skills/playwright-testing in your project. Claude Code loads it when a task matches its description.
How do I install Playwright Testing in Codex?
Run `npx skills add PrairieLearn/PrairieLearn --skill playwright-testing -a codex`. Or copy the skill folder (.agents/skills/playwright-testing in PrairieLearn/PrairieLearn) into .agents/skills/playwright-testing in your project. Codex loads it when a task matches its description.
Can I use Playwright Testing 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 PrairieLearn/PrairieLearn --skill playwright-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/playwright-testing, .gemini/skills/playwright-testing, .github/skills/playwright-testing and .opencode/skills/playwright-testing in your project.
What does Playwright Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Playwright Testing is instructions for the agent only.
Does Playwright Testing 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 Playwright Testing 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 Playwright Testing use?
Playwright Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Playwright Testing use?
About 280 tokens (SKILL.md is roughly 1.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 Playwright Testing?
Skills that share tags, products or a category with Playwright Testing: Web Application Testing (anthropics/skills, 180k stars), playwright-cli Browser Automation (github/gh-aw, 5.3k 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 Playwright Testing?
PrairieLearn (a GitHub organization) maintains it in PrairieLearn/PrairieLearn, which has 512 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: PrairieLearn/PrairieLearn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.