C✳CODEZ.WIN
🌐 English

Localized reading guide

playwright-interactivePurpose, usage and source

Persistent browser and Electron interaction through js_repl for fast iterative UI debugging.

Source retrieved:

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

License: License file needs review

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

Persistent browser and Electron interaction through js_repl for fast iterative UI debugging.

How the upstream workflow works

Core Workflow

Write a brief QA inventory before testing: Build the inventory from three sources: the user's requested requirements, the user-visible features or behaviors you actually implemented, and the claims you expect to make in the final response. Anything that appears in any of those three sources must map to at least one QA check before signoff. List the user-visible claims you intend to sign off on.

Upstream passage · L40 ↗

Playwright Interactive Skill

Use a persistent js_repl Playwright session to debug local web or Electron apps, keep the same handles alive across iterations, and run functional plus visual QA without restarting the whole toolchain unless the process ownership changed.

Upstream passage · L6 ↗

Preconditions

js_repl must be enabled for this skill. If js_repl is missing, enable it in ~/.codex/config.toml:

Upstream passage · L10 ↗
Upstream passage · toml ↗
[features]
js_repl = true

Requirements and setup

One-time setup

If you switch to a different workspace later, repeat setup there.

Upstream passage · L26 ↗

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

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
f6c1155d923e6ae3ccc12abfef2266f119f8e9546df2ddeee1f5eb369845a0a1
Back to the full Skill catalog