playwright-skill

Generate and execute Playwright scripts against detected development servers.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Avi977/ace-claude-toolkit --skill playwright-skill-avi977
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/Avi977/ace-claude-toolkit/tree/main/skills/browser-automation/skills/playwright-skill
Command: npx skills add https://github.com/Avi977/ace-claude-toolkit --skill playwright-skill-avi977

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end browser testing workflows by generating and executing Playwright scripts against locally detected development servers, saving time and reducing manual testing effort.

Core Features & Use Cases

  • Auto-detects running dev servers and writes tailored Playwright scripts to /tmp for safe execution.
  • Supports common testing tasks: form filling, navigation, screenshots, responsive checks, login flows, and link validation.
  • Real-world scenario: quickly validate a new web app across desktop and mobile viewports with automatic results and clean-up.

Quick Start

Detect dev servers, generate a Playwright test in /tmp, and run it against the target site.

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 against a running development server?

Automating browser testing against a development server is done by auto-detecting the running dev server, generating a tailored Playwright script in the /tmp directory, and executing it to validate your web application automatically.

Can Playwright capture screenshots across different mobile and desktop viewports?

Playwright can capture screenshots across different viewports by generating test scripts that specify responsive checks, allowing you to validate how your website renders on both desktop and mobile configurations during execution.

What is the best way to validate login flows and form filling in end-to-end testing?

The best way to validate login flows and form filling is by generating tailored Playwright test scripts that programmatically navigate and interact with UI elements, executing these scenarios against your locally detected development server.

Does this approach require manually configuring the target URL for web automation scripts?

This approach does not require manual URL configuration because the testing workflow automatically detects running development servers and dynamically targets them when generating and executing the Playwright automation scripts.

Are there limitations when writing test scripts to the /tmp directory for browser automation?

A limitation of writing test scripts to the /tmp directory is that scripts are intended for safe, temporary execution and automated clean-up, meaning custom test logic must be regenerated for each new testing session rather than persisted permanently.