playwright-skill

Automate browser testing with Playwright scripts written to /tmp.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Blake-John/agent-config --skill playwright-skill-blake-john
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/Blake-John/agent-config/tree/main/.zeroclaw/workspace/skills/playwright-skill
Command: npx skills add https://github.com/Blake-John/agent-config --skill playwright-skill-blake-john

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complete browser automation and testing workflows using Playwright. Auto-detects dev servers, writes clean test scripts to /tmp, and executes them to validate pages, forms, and UX across browsers.

Core Features & Use Cases

  • Auto-detects running dev servers and writes temporary test scripts to /tmp
  • Writes and runs Playwright automation scripts with a visible browser by default
  • Performs common tasks: navigation, form filling, taking screenshots, and testing responsive design

Quick Start

Describe a task to automate and I will generate a Playwright script in /tmp and run it.

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 for a local dev server?

Playwright automation handles this by auto-detecting your running local dev server, generating a temporary test script in the /tmp directory, and executing cross-browser UI flows against it automatically.

Can I run Playwright automation scripts with a visible browser instead of headless mode?

Yes, Playwright scripts run with a visible browser by default. The universal executor supports configurable headless mode, allowing you to watch the automation perform navigation, form filling, and visual checks in real time.

What tasks can I automate using Playwright for UI validation?

Playwright UI automation supports common tasks including page navigation, form filling, taking screenshots, and testing responsive design across different browsers to validate pages and user experience.

Does Playwright automation require manually configuring the target server URL?

No manual server URL configuration is needed. The automation auto-detects running dev servers in your environment, writes the test scripts to /tmp, and targets the detected server automatically for execution.

How do I test responsive design and forms across multiple browsers automatically?

Cross-browser testing for responsive design and forms is done by writing Playwright scripts to /tmp and running them via a universal executor. The executor handles the UI flows and environment headers across target browsers.

Are there limitations to running Playwright test scripts generated to the /tmp directory?

Generated Playwright scripts are written to /tmp as temporary files, meaning they may be cleared by system reboots. Scripts rely on the universal executor and require a running dev server for successful cross-browser execution.