Playwright

Skill zaixincheng174-ai/codex-agent-governance-skills/core/skills/playwright

Codex governance skill pack for AI coding agents: lifecycle gates, repo preflight, diff-scope audit, evidence closeout, and capability-delivery checks.

Install

npx -y skills add zaixincheng174-ai/codex-agent-governance-skills --skill playwright

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

One thing to look at

1 stars1 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.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.7 KB, 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.

Gives 3 of the 12 instructions most e2e browser skills give

Counted across 407 of the 410 authors here whose files we hold, read 2026-08-06

use page object model patternin 35 of 407, across 25 files
Snapshot to get element refshere, and in 24 of 407, across 14 files
keep tests independentin 23 of 407, across 18 files
Interact using refs from the latest snapshothere, and in 23 of 407, across 11 files
clean up test data after each testin 21 of 407, across 15 files
test user behavior not implementationin 20 of 407, across 14 files
quarantine flaky tests explicitlyin 19 of 407, across 10 files
wait for specific network conditionsin 18 of 407, across 8 files
re-snapshot after navigation or dom changeshere, and in 17 of 407, across 10 files
Detect running dev servers before writing test codein 17 of 407, across 7 files
use web-first assertionsin 17 of 407, across 14 files
capture screenshots or videos on test failurein 17 of 407, across 14 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.