skills.rest
Sacred-G
Sacred-GCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

playwright-interactive

Orchestrate a persistent Playwright session for debugging local web and Electron apps.

2|1|Updated Apr 2, 2026
Search Tags:#automation#debugging#qa#playwright#electron#web#persistent-session
One-click install
npx skills add https://github.com/Sacred-G/oh-my-claw --skill playwright-interactive-sacred-g
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-interactive
Source: https://github.com/Sacred-G/oh-my-claw/tree/main/secure-openclaw/skills-main/skills/.curated/playwright-interactive
Command: npx skills add https://github.com/Sacred-G/oh-my-claw --skill playwright-interactive-sacred-g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines debugging of local web and Electron apps by maintaining a persistent Playwright session, so you don't have to reinitialize handles between iterations.

Core Features & Use Cases

  • Persistent session throughout QA cycles to reuse browser, context, and page handles across runs.
  • Cross-context debugging for both web and Electron apps with unified tooling.
  • Integrated setup guidance to enable js_repl and install Playwright for immediate use.

Quick Start

Install Playwright in your workspace and run the setup steps to initialize a persistent session.

Frequently Asked Questions about playwright-interactive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep a Playwright session persistent across multiple QA runs?▼

A persistent Playwright session reuses browser, context, and page handles across iterative QA runs without reinitializing them. You maintain this state by enabling js_repl and following the setup steps to configure the environment.

Can I use Playwright to debug both web and Electron apps in the same workflow?▼

Yes, you can debug both web and Electron apps within the same workflow using unified tooling. The session orchestrates cross-context debugging, allowing you to handle both web and Electron targets seamlessly across runs.

What do I need to install to start debugging local web apps with Playwright?▼

To start debugging local web apps, you must install Playwright in your workspace and enable js_repl. Following the integrated setup steps initializes the environment and prepares the persistent QA session for immediate use.

Why do I have to restart browser handles every time I run Playwright QA tests?▼

You face restarting handles because standard sessions reinitialize the browser on every run. Using a persistent Playwright session solves this by maintaining and reusing browser, context, and page handles across iterative QA cycles.

Does persistent Playwright debugging work without enabling js_repl?▼

No, persistent Playwright debugging does not work without enabling js_repl. Enabling js_repl is a required prerequisite to orchestrate the persistent session and reuse handles across your QA workflows.

What are the limitations of reusing a single Playwright context for Electron and web debugging?▼

The main limitation is the strict environment configuration; you must enable js_repl and install Playwright properly. While it unifies web and Electron debugging, failing to follow setup steps prevents the persistent session from initializing.

Related Skills

Explore More Software Engineering Skills→
jaypatrickjaypatrick

playwright-interactive

Manage persistent Playwright sessions for web and Electron app debugging.

Community
Intermediate
hellitonsmhellitonsm

playwright-interactive

Maintain persistent Playwright and Electron QA sessions for iterative UI debugging.

Community
Advanced
pczhao1210pczhao1210

playwright-interactive

Maintain persistent Playwright sessions for iterative browser and Electron UI debugging.

Community
Advanced
atomeamatomeam
2

browser-session-persistence

Save and load Playwright browser session states for authenticated automation.

Community
Intermediate