playwright-skill

Generate and execute custom Playwright scripts for browser testing.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/LuizEduPP/skills --skill playwright-skill-luizedupp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/LuizEduPP/skills/tree/main/playwright-skill
Command: npx skills add https://github.com/LuizEduPP/skills --skill playwright-skill-luizedupp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of spinning up Playwright automation by auto-detecting dev servers, isolating scripts in /tmp, and keeping browsers visible so you can verify web functionality without manual environment tuning.

Core Features & Use Cases

  • Server detection first: Scans common localhost ports, prompts for missing URLs, and keeps you from hardcoding dev targets before writing any automation.
  • Temporary script management: Writes custom Playwright code to /tmp, executes it through the run.js harness, and lets the operating system clean up test files automatically.
  • Visible, responsive testing: Defaults to headed Chromium with configurable viewports, login/form checks, screenshot capture, header injection, and robust helpers for retries and waits.

Quick Start

Ask the skill to auto-detect your dev server, write a responsive Playwright test to /tmp, and run it with visible Chromium to verify the homepage.

Frequently Asked Questions about playwright-skill

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

FAQPage Schema
How do I run visible Playwright tests against a local dev server without hardcoding URLs?

Playwright tests can run visibly by auto-detecting localhost dev servers through common port scanning. This keeps you from hardcoding targets and prompts for missing URLs before generating custom automation scripts for execution.

How do I execute temporary Playwright scripts without cluttering my project directory?

Temporary Playwright scripts are written to /tmp and executed through a dedicated run.js harness, letting the operating system clean up test files automatically. This isolates browser automation code from your main project.

Can I test responsive viewports and validate login forms with headed Chromium?

Headed Chromium supports configurable viewports, login/form validation, and screenshot capture. You can verify responsive UI automation and web application QA scenarios with visible execution to confirm functionality visually.

Does browser automation support custom HTTP headers and retry logic for form validation?

Browser automation supports configurable HTTP header injection alongside robust helpers for retries and waits. This enables reliable form and login flow validation during web application testing.

What is the best way to automate web application QA with temporary script management?

Automating web application QA is best handled by generating custom Playwright code to /tmp and executing it through a harness. This approach auto-detects dev servers and maintains visible headed execution across configurable viewports.

Why should I use auto-detection for localhost ports before writing browser automation?

Auto-detecting localhost ports prevents environment configuration errors by scanning common dev server targets before writing automation. It prompts for missing URLs, ensuring your Playwright scripts target the correct local instance.