Official agent skill

Playwright

A skill your agent uses when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli…

OfficialApache-2.0Auto-check passedTesting & QA

Install Playwright

skills CLI

$ npx skills add JetBrains/skills --skill playwright -a claude-code

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

GitHub CLI

$ gh skill install JetBrains/skills playwright --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/JetBrains/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/playwright .claude/skills/playwright && 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 "playwright" agent skill from https://github.com/JetBrains/skills/tree/main/playwright into .claude/skills/playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright", 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/JetBrains/skills/tree/main/playwright

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 JetBrains/skills --skill playwright -a codex

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

GitHub CLI

$ gh skill install JetBrains/skills playwright --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/playwright .agents/skills/playwright && 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 "playwright" agent skill from https://github.com/JetBrains/skills/tree/main/playwright into .agents/skills/playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright", 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 JetBrains/skills --skill playwright -a cursor

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

GitHub CLI

$ gh skill install JetBrains/skills playwright --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/playwright .cursor/skills/playwright && 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 "playwright" agent skill from https://github.com/JetBrains/skills/tree/main/playwright into .cursor/skills/playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright", 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/JetBrains/skills.git --path playwright

--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 JetBrains/skills --skill playwright -a gemini-cli

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

GitHub CLI

$ gh skill install JetBrains/skills playwright --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/JetBrains/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/playwright .gemini/skills/playwright && 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 "playwright" agent skill from https://github.com/JetBrains/skills/tree/main/playwright into .gemini/skills/playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright", 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 JetBrains/skills playwright

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 JetBrains/skills --skill playwright -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/playwright .github/skills/playwright && 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 "playwright" agent skill from https://github.com/JetBrains/skills/tree/main/playwright into .github/skills/playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright", 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 JetBrains/skills --skill playwright -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 JetBrains/skills playwright --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/playwright .opencode/skills/playwright && 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 "playwright" agent skill from https://github.com/JetBrains/skills/tree/main/playwright into .opencode/skills/playwright/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright", 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
GitHub stars: 363
Used in: 11 other repos
Token cost: ~986 tokens
SKILL.md length: 340 words
Files: 9 (incl. scripts, references, assets)
Skills in repo: 79
Repo updated: Jun 29, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli…

Works in 5 steps: Open the page. → Snapshot to get stable element refs. → Interact using refs from the latest… → …
The task requires automating a real browser from the terminal (navigation
SKILL.md covers Prerequisite check (required), Skill path (set once), Quick start and Core workflow, plus 5 more sections
Runs Shell scripts from its folder; calls npm, node and npx; reaches playwright.dev

What it does

Playwright is an agent skill from JetBrains/skills, published by the product's own GitHub organization. Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `references/cli.md` and `references/workflows.md`).

It sits in Testing & QA, covering Browser testing and Forms and invoices. It works with Playwright. The repository describes itself as: Curated agent skills collection verified by JetBrains. The licence is Apache-2.0.

When your agent uses it

The task requires automating a real browser from the terminal (navigation
Data extraction
UI-flow debugging) via playwright-cli
The bundled wrapper script

Example prompts

“/playwright”

Requirements

Node.js
A Bash shell

Workflow steps

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

Open the page.
Snapshot to get stable element refs.
Interact using refs from the latest snapshot.
Re-snapshot after navigation or significant DOM changes.
Capture artifacts (screenshot, pdf, traces) when useful.

What it can do on your machine

Read from SKILL.md and the folder at commit e0f258b. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- npm
- node
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- playwright.dev
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 loads about 986 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 340 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~986
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~1.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from JetBrains/skills at commit e0f258b, republished under its Apache-2.0 licence (© JetBrains). 340 words, ~986 tokens.

Download SKILL.mdSave it as .claude/skills/playwright/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.

name: playwright
description: Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
metadata.short-description: Automate real browsers from the terminal
metadata.author: OpenAI
metadata.source: https://github.com/openai/skills/tree/main/skills/.curated/playwright

Playwright CLI Skill

Drive a real browser from the terminal using playwright-cli. Prefer the bundled wrapper script so the CLI works even when it is not globally installed. Treat this skill as CLI-first automation. Do not pivot to @playwright/test unless the user explicitly asks for test files.

Prerequisite check (required)

Before proposing commands, check whether npx is available (the wrapper depends on it):

bash

command -v npx >/dev/null 2>&1

If it is not available, pause and ask the user to install Node.js/npm (which provides npx). Provide these steps verbatim:

bash

# Verify Node/npm are installed
node --version
npm --version

# If missing, install Node.js/npm, then:
npm install -g @playwright/cli@latest
playwright-cli --help

Once npx is present, proceed with the wrapper script. A global install of playwright-cli is optional.

Skill path (set once)

bash

export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
export PWCLI="$CODEX_HOME/skills/playwright/scripts/playwright_cli.sh"

User-scoped skills install under $CODEX_HOME/skills (default: ~/.codex/skills).

Quick start

Use the wrapper script:

bash

"$PWCLI" open https://playwright.dev --headed
"$PWCLI" snapshot
"$PWCLI" click e15
"$PWCLI" type "Playwright"
"$PWCLI" press Enter
"$PWCLI" screenshot

If the user prefers a global install, this is also valid:

bash

npm install -g @playwright/cli@latest
playwright-cli --help

Core workflow

Open the page.
Snapshot to get stable element refs.
Interact using refs from the latest snapshot.
Re-snapshot after navigation or significant DOM changes.
Capture artifacts (screenshot, pdf, traces) when useful.

Minimal loop:

bash

"$PWCLI" open https://example.com
"$PWCLI" snapshot
"$PWCLI" click e3
"$PWCLI" snapshot

When to snapshot again

Snapshot again after:

navigation
clicking elements that change the UI substantially
opening/closing modals or menus
tab switches

Refs can go stale. When a command fails due to a missing ref, snapshot again.

Recommended patterns

Form fill and submit

bash

"$PWCLI" open https://example.com/form
"$PWCLI" snapshot
"$PWCLI" fill e1 "user@example.com"
"$PWCLI" fill e2 "password123"
"$PWCLI" click e3
"$PWCLI" snapshot

Debug a UI flow with traces

bash

"$PWCLI" open https://example.com --headed
"$PWCLI" tracing-start
# ...interactions...
"$PWCLI" tracing-stop

Multi-tab work

bash

"$PWCLI" tab-new https://example.com
"$PWCLI" tab-list
"$PWCLI" tab-select 0
"$PWCLI" snapshot

Wrapper script

The wrapper script uses npx --package @playwright/cli playwright-cli so the CLI can run without a global install:

bash

"$PWCLI" --help

Prefer the wrapper unless the repository already standardizes on a global install.

References

Open only what you need:

CLI command reference: references/cli.md
Practical workflows and troubleshooting: references/workflows.md

Guardrails

Always snapshot before referencing element ids like e12.
Re-snapshot when refs seem stale.
Prefer explicit commands over eval and run-code unless needed.
When you do not have a fresh snapshot, use placeholder refs like eX and say why; do not bypass refs with run-code.
Use --headed when a visual check will help.
When capturing artifacts in this repo, use output/playwright/ and avoid introducing new top-level artifact folders.
Default to CLI commands and workflows, not Playwright test specs.

Files

SKILL.md and 8 other files (scripts, references, assets) in playwright of JetBrains/skills.

SKILL.md
LICENSE.txt
NOTICE.txt
agents/openai.yaml
assets/playwright-small.svg
assets/playwright.png
references/cli.md
references/workflows.md
scripts/playwright_cli.sh

Open the folder on GitHubat commit e0f258b

Used in 11 other repositories

We found 12 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in JetBrains/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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

Playwright compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Playwright this skillJetBrains/skills	363	11 repos	~986	Automated safety check: Pass	Apache-2.0	3 mo ago
Playwright CLIsanity-io/sanity	6.4k	18 repos	~1.9k	Automated safety check: Pass	MIT	today
Playwright6BNBN/FlowPilot	134	—	~1k	Automated safety check: Pass	Apache-2.0	6 mo ago
Openai Playwrighttrailofbits/skills-curated	512	—	~945	Automated safety check: Notes	CC-BY-SA-4.0	2 mo ago
Playwright AutomationArabelaTso/Skills-4-SE	253	—	~930	Automated safety check: Pass	Apache-2.0	1 mo ago
Playwright CLItestdino-hq/playwright-skill	385	1 repos	~2.5k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Playwright CLI
sanity-io/sanity
Official
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
6.4k GitHub starsUsed in 18 repos~1.9k tokens
Testing & QAAuto-check passed
Playwright
6BNBN/FlowPilot
A skill your agent uses when the task requires automating a real browser from the terminal in Cursor, including navigation, form filling, snapshots, screenshots, data extraction, and UI-flow…
134 GitHub stars~1k tokensUpdated 6 mo ago
Testing & QAAuto-check passed
Openai Playwright
trailofbits/skills-curated
Official
A skill your agent uses when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli…
512 GitHub stars~945 tokensUpdated 2 mo ago
Testing & QAAuto-check: notes
Playwright Automation
ArabelaTso/Skills-4-SE
Browser automation via Playwright for web testing, screenshots, form filling, scraping, and verification.
253 GitHub stars~930 tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Playwright CLI
testdino-hq/playwright-skill
Automates browser interactions for testing and validating your own web applications using playwright-cli.
385 GitHub starsUsed in 1 repo~2.5k tokens
Testing & QAAuto-check passed
Playwright E2E Authoring
fmflurry/settings-opencode
Scaffold and extend Playwright E2E tests for the gc.platform suite (tests/playwright), wiring every artifact to the real frontend (localhost:4200) + real .NET backend — never mocks.
171 GitHub stars~2.4k tokensUpdated 2 days ago
Testing & QAAuto-check passed

Questions about Playwright

What does Playwright do?

A skill your agent uses when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli…. Playwright is an agent skill from JetBrains/skills, published by the product's own GitHub organization. Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.

When should I use Playwright?

Playwright fits situations like: the task requires automating a real browser from the terminal (navigation; data extraction; UI-flow debugging) via playwright-cli; the bundled wrapper script.

How do I install Playwright in Claude Code?

Run `npx skills add JetBrains/skills --skill playwright -a claude-code`. Or copy the skill folder (playwright in JetBrains/skills) into .claude/skills/playwright in your project. Claude Code loads it when a task matches its description.

How do I install Playwright in Codex?

Run `npx skills add JetBrains/skills --skill playwright -a codex`. Or copy the skill folder (playwright in JetBrains/skills) into .agents/skills/playwright in your project. Codex loads it when a task matches its description.

Can I use Playwright 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 JetBrains/skills --skill playwright -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, .gemini/skills/playwright, .github/skills/playwright and .opencode/skills/playwright in your project.

What does Playwright need to run?

Going by SKILL.md and its folder, Playwright needs a shell for the scripts in its folder and the command-line tools its instructions call (npm, node and npx). Our summary lists: Node.js; A Bash shell.

Does Playwright access the network?

SKILL.md names 1 domain. In commands or code: playwright.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Playwright 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Playwright use?

Playwright is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Playwright use?

About 986 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 932 tokens, read only when the agent opens those files.

What are the alternatives to Playwright?

Skills that share tags, products or a category with Playwright: Playwright CLI (sanity-io/sanity, 6.4k stars), Playwright (6BNBN/FlowPilot, 134 stars), Openai Playwright (trailofbits/skills-curated, 512 stars) and Playwright Automation (ArabelaTso/Skills-4-SE, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Playwright?

JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/skills, which has 363 GitHub stars. The repository holds 79 skills in this directory. The repository was last updated on June 29, 2026.

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

Install Playwright

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

Playwright CLI Skill

Prerequisite check (required)

Skill path (set once)

Quick start

Core workflow

When to snapshot again

Recommended patterns

Form fill and submit

Debug a UI flow with traces

Multi-tab work

Wrapper script

References

Guardrails

Files

Used in 11 other repositories

Compare with similar skills

Similar skills

More from JetBrains/skills

Related

Questions about Playwright