playwright-explorer

Explores running web applications via Playwright with natural language interaction and DOM inspection.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/rubrical-works/idpf-praxis-skills --skill playwright-explorer-rubrical-works
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-explorer
Source: https://github.com/rubrical-works/idpf-praxis-skills/tree/main/Skills/playwright-explorer
Command: npx skills add https://github.com/rubrical-works/idpf-praxis-skills --skill playwright-explorer-rubrical-works

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test.

What problem does it solve? Manually inspecting web app UIs and writing selectors for browser automation is slow and error-prone. This Skill connects to a running web application through Playwright, reads the live DOM, and executes natural language actions like clicking buttons or filling forms without writing test code first. ## Core Features & Use Cases - Pre-Flight Verification: Detects Node.js 18+, Playwright, Chromium, and system dependencies, then auto-installs missing components with user confirmation for package installs. - DOM Reading: Extracts visible text, interactive elements, heading/landmark layout, computed styles, and data-testid attributes from the live page. - Natural Language Interaction: Resolves plain-language element descriptions using a priority strategy (data-testid > ARIA role > visible text > CSS) and executes click, fill, type, goto, goBack, and waitForSelector actions. - Session Management: Persists background browser sessions via file-based IPC, runs health checks, and recovers from crashes, timeouts, and orphaned processes. - Use Case: Start your dev server, then ask the assistant to explore the login page, click the submit button, and report what interactive elements and test IDs exist on the page. ## Quick Start Ask the assistant to connect to your running app at localhost:3000 with Playwright and list all interactive elements on the page.

Frequently Asked Questions about playwright-explorer

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

FAQPage Schema
How do I explore a web app with Playwright using natural language?▼

Connect to your running dev server URL, then describe actions in plain language like clicking a button or filling a field. The skill resolves descriptions to selectors using a priority strategy: data-testid first, then ARIA role, visible text, and finally CSS selectors.

How does Playwright selector resolution work for element descriptions?▼

Resolution tries four strategies in order: data-testid attribute matching, ARIA role with accessible name, exact visible text match, and literal CSS selector. If nothing matches, it returns up to five partial matches as suggestions.

What are the requirements to run Playwright browser exploration?▼

You need Node.js 18 or higher, the @playwright/test package, a Chromium binary, and system dependencies on Linux. The pre-flight check detects missing components and auto-installs them, though package installation requires your confirmation.

Can Playwright connect to an Electron app for testing?▼

Yes, it connects to Electron via Chrome DevTools Protocol using chromium.connectOverCDP. Start Electron with --remote-debugging-port=9222 and provide the CDP endpoint such as http://localhost:9222.

Why does my Playwright session disconnect or time out?▼

Sessions end when the target app crashes or closes, or when actions exceed timeouts of 30 seconds for navigation and 10 seconds for element actions. Health checks detect dead browser processes, and cleanup removes orphaned temp files automatically.