playwright-skill

Automate browser testing with Playwright scripts and dev-server detection.

2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/ShunmeiCho/dotclaude --skill playwright-skill-shunmeicho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/ShunmeiCho/dotclaude/tree/main/skills/playwright-skill
Command: npx skills add https://github.com/ShunmeiCho/dotclaude --skill playwright-skill-shunmeicho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright-based browser automation is often encumbered by boilerplate setup and fragile test scripts. This Skill provides a universal executor, dev-server auto-detection, and ephemeral /tmp script generation to streamline web testing and automation tasks, reducing upfront work and clutter.

Core Features & Use Cases

  • Auto-detects running dev servers and suggests test URLs
  • Writes custom Playwright scripts to /tmp for clean, ephemeral runs
  • Provides robust helpers for reliable interactions, screenshots, waits, and basic QA validations

Quick Start

Install dependencies with npm run setup, then create or run tests using the universal executor:

  • Detect dev servers: cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(s => console.log(JSON.stringify(s)))"
  • Run a script: cd $SKILL_DIR && node run.js /tmp/playwright-test-*.js
  • Inline execution: cd $SKILL_DIR && node run.js "const { chromium } = require('playwright'); const browser = await chromium.launch({ headless: false }); ..."

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 with Playwright without writing boilerplate setup?

Playwright browser automation is streamlined here through a universal executor that generates ephemeral /tmp scripts, reducing boilerplate setup and fragile test scripts. You simply provide the automation logic, and the executor handles the execution environment.

How do I detect a running local dev server for web automation tasks?

Local dev servers are auto-detected by helper functions that scan your environment and suggest test URLs. You can manually trigger detection by executing the detectDevServers helper within the Skill directory.

How do I run inline Playwright scripts for quick UI testing?

Inline execution is supported by passing a JavaScript string directly to the run.js executor. This allows you to run quick browser automation tasks and form interactions without creating a permanent script file.

Does this Playwright automation approach support custom headers and parameterized URLs?

Yes, environment headers injection and parameterized URLs are supported natively. This allows you to configure custom environments and target dynamic endpoints during your end-to-end web testing runs.

What is the best way to handle robust waits and input interactions during browser testing?

Robust waits and input interactions are managed via an integrated helper library. This library provides reliable commands for UI testing, screenshots, and basic QA validations to prevent fragile test scripts.

Are there limitations to running ephemeral Playwright scripts in /tmp directories?

Ephemeral scripts written to /tmp are automatically cleaned up, which means test reports and screenshots must be explicitly saved elsewhere if you need to persist them after the browser automation run finishes.