playwright

Automate browser testing with Playwright scripts executed in /tmp.

Updated Oct 9, 2025
One-click install
npx skills add https://github.com/hmps/agent-tools --skill playwright
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/hmps/agent-tools/tree/main/skills/playwright
Command: npx skills add https://github.com/hmps/agent-tools --skill playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets you automate browser interactions using Playwright, enabling you to test websites, validate functionality, and capture UX feedback without manual, repetitive steps. It auto-detects local dev servers, writes deterministic test scripts to /tmp, and runs them via a universal executor so you can focus on the outcome, not the setup.

Core Features & Use Cases

  • Auto-detect dev servers: Identify running local servers for quick, iterative testing.
  • Deterministic test scripts: The Skill writes scripts to /tmp/playwright-test-*.js to keep your project clean.
  • Browser actions: Navigate pages, fill forms, take screenshots, validate responsive design, and verify links and login flows.
  • Reuse existing auth: Uses a Chrome-based debugging session to preserve cookies and login state across runs.

Quick Start

Use the Playwright skill to automate a simple test against a local dev site. The system will auto-detect servers, generate a script in /tmp, and execute it through the universal executor. Example: cd $SKILL_DIR && node run.js /tmp/playwright-test-page.js

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate browser testing workflows with Playwright?

Playwright automates browser interactions by writing deterministic test scripts to /tmp and executing them with a visible browser. The Skill auto-detects local dev servers, handles form filling, screenshots, and login validation without manual setup.

Can I use Playwright to test login flows and preserve authentication state?

Yes. The Skill reuses Chrome-based debugging sessions to preserve cookies and login state across test runs, eliminating the need to re-authenticate for each test.

What are the system requirements for running Playwright scripts?

Playwright requires Node.js 22+ and Playwright 1.57+. Scripts execute via run.js in the Skill directory and are generated in /tmp; the Claude Code workflow with connectToChrome() support is necessary for authenticated sessions.

How do I validate responsive design and UX flows without manual testing?

Use Playwright to navigate pages, fill forms, take screenshots, and verify links programmatically. The Skill generates scripts that validate web functionality and UX across different scenarios deterministically.

Does Playwright work with local development servers running on my machine?

Yes. The Skill auto-detects running local dev servers, allowing you to write and execute test scripts immediately against your development environment for iterative testing.

Why shouldn't I use chromium.launch() directly in Playwright scripts?

The Skill forbids direct chromium.launch() unless you explicitly request a fresh session, because connectToChrome() preserves authentication and reuses the existing browser session for consistent, faster testing.