Openai skills playwright 1.0.1

Skill VRIL-LABS/skill-jam/skills/browser-automation/openai-skills-playwright-1.0.1

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.From its SKILL.md

Install

npx -y skills add VRIL-LABS/skill-jam --skill openai-skills-playwright-1.0.1

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

4 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.
0 stars0 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.
runs commandsInstructs the agent to run 8 commands, including `command -v npx >/dev/null 2>&1` and 7 more.
fetches URLsInstructs the agent to fetch 3 URLs, including https://playwright.dev and 2 more.

SKILL.md

3.7 KB, 894 tokens by cl100k_base, as published. Nobody here has run it

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):

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:

# 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)

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:

"$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:

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:

"$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

"$PWCLI" open https://example.com/form
"$PWCLI" snapshot
"$PWCLI" fill e1 "[email protected]"
"$PWCLI" fill e2 "password123"
"$PWCLI" click e3
"$PWCLI" snapshot

Debug a UI flow with traces

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

Multi-tab work

"$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:

"$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.

What ships with it: 8 files

18.6 KB alongside SKILL.md, 1 of them executable

Gives 1 of the 12 instructions most e2e browser skills give in 894 tokens

Counted across 499 of the 513 authors here whose files we hold, read 2026-09-06

Capture screenshots, videos, and traces on failurein 32 of 499, across 23 files
Close the browser when donein 22 of 499
Interact with elements using snapshot refshere, and in 21 of 499, across 20 files
Wait for specific network responses instead of fixed timeoutsin 20 of 499, across 10 files
Keep tests independent with no shared statein 19 of 499, across 17 files
Use Page Object Model classes to encapsulate page interactionsin 19 of 499, across 9 files
Locate elements with data-testid attributesin 19 of 499, across 10 files
Quarantine flaky tests with fixme or skipin 17 of 499, across 7 files
Upload test artifacts after every CI runin 17 of 499, across 8 files
Wait on conditions instead of using fixed sleepsin 17 of 499, across 13 files
Clean up test data after each testin 17 of 499, across 16 files
Test user-visible behavior, not implementation detailsin 16 of 499, across 10 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.