C✳CODEZ.WIN
🌐 English

Localized reading guide

playwrightPurpose, usage and source

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.

Source retrieved:

Source repository
openai/skills
SKILL.md
skills/.curated/playwright/SKILL.md
Repository stars
28,420
Repository updated
2026-10-29
Categories
Development
Last collected

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

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.

How the upstream workflow works

Quick start

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

Upstream passage · L43 ↗

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.

Upstream passage · L63 ↗

When to snapshot again

Snapshot again after: clicking elements that change the UI substantially opening/closing modals or menus Refs can go stale. When a command fails due to a missing ref, snapshot again.

Upstream passage · L80 ↗

Requirements and setup

Prerequisite check (required)

Before proposing commands, check whether npx is available (the wrapper depends on it): If it is not available, pause and ask the user to install Node.js/npm (which provides npx). Provide these steps verbatim:

Upstream passage · L12 ↗
Upstream passage · bash ↗
command -v npx >/dev/null 2>&1

Limits and quality checks

Guardrails

Always snapshot before referencing element ids like e12. Re-snapshot when refs seem stale.

Upstream passage · L139 ↗

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
49f948faa9258a0c61caceaf225e179651397431
Source SHA-256
0ffaabcc8e0990627c4725f18bf1c7955534a796c1c199e872909de2013ce6a8
Back to the full Skill catalog