playwright-skill

Generate and execute Playwright browser automation scripts in /tmp.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill playwright-skill-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/playwright-skill
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill playwright-skill-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repetitive browser testing and interaction tasks by generating and running Playwright scripts through a universal executor, saving time and reducing manual QA effort.

Core Features & Use Cases

  • Auto-detects running dev servers and uses them automatically for localhost testing.
  • Writes custom Playwright scripts to /tmp/playwright-test-*.js and executes them via run.js to keep projects clean.
  • Supports parameterized URLs, multi-browser execution (Chromium, Firefox, WebKit), and environment-based headers for automated traffic identification.
  • Includes helper utilities (lib/helpers.js) for robust actions like safe clicking, waiting, and data extraction.

Quick Start

Install the skill, run from the skill directory, then describe the browser task you want automated and Claude will detect dev servers, generate a /tmp/playwright-test-*.js script, and execute it with a visible browser.

Frequently Asked Questions about playwright-skill

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

FAQPage Schema
How do I automate browser testing tasks with Playwright without cluttering my project directory?

Playwright automation handles dev server detection automatically by scanning for running local development servers. Once detected, it parameterizes localhost URLs and uses the active server for immediate testing without requiring manual URL entry.

How do I inject custom HTTP headers into automated browser tests for traffic identification?

Inject custom HTTP headers into automated browser tests using environment-based header configuration. This identifies automated traffic during execution, allowing you to filter or route test requests separately from regular development traffic on your server.

Do I need a running development server to use Playwright for localhost testing?

A running development server is not strictly required but is auto-detected when available for localhost testing. If a dev server is running, the automation uses it automatically; otherwise, you can parameterize URLs to target any accessible endpoint.

What is the best way to generate Playwright scripts for repetitive web interaction tasks?

The best way to generate Playwright scripts for repetitive web interactions is describing the task to automate, which triggers script generation in /tmp and execution via a universal run.js file. This approach includes error handling safeguards and helper utilities for robust actions.