playwright-skill

Automate browser testing and UI validation with Playwright scripts.

35|5|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/alexei-led/cc-thingz --skill playwright-skill-alexei-led
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/alexei-led/cc-thingz/tree/main/plugins/testing-e2e/skills-codex/playwright-skill
Command: npx skills add https://github.com/alexei-led/cc-thingz --skill playwright-skill-alexei-led

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser testing and automation tasks using Playwright.

Core Features & Use Cases

  • Writes and runs custom Playwright scripts to automate browsing, test flows, and visual checks on localhost or remote servers.
  • Detects dev servers, captures screenshots, and validates UI behavior across viewports and login flows.

Quick Start

Generate and run a Playwright automation script for the requested task using the universal executor.

Frequently Asked Questions about playwright-skill

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

FAQPage Schema
How do I run Playwright scripts for UI testing on a local dev server?

Playwright UI testing on a local dev server works by executing custom automation scripts via a universal executor that auto-detects the dev server, writes temporary test files to /tmp, and uses helper utilities for safe browser actions and error handling.

Can I capture screenshots and validate responsive design across different viewports with browser automation?

Browser automation with Playwright captures screenshots and validates UI behavior across multiple viewports by running custom scripts on localhost or remote servers to verify responsive design and test login flows.

Do I need to manually configure URLs to automate browser tasks on localhost?

No, you do not need to manually configure URLs to automate browser tasks on localhost because the executor auto-detects dev servers, allowing Playwright scripts to target the local environment automatically.

What is the best way to handle errors and perform safe actions during Playwright automation?

Handling errors and performing safe actions during Playwright automation is achieved through built-in helper utilities that manage safe interactions and error handling within the generated test scripts executed by the universal executor.

Does headful browser automation work for visual testing on remote sites?

Headful browser automation supports visual testing on remote sites by executing custom Playwright scripts that navigate flows, capture screenshots, and validate UI behavior across viewports on remote servers.

Are there limitations when writing temporary test files for Playwright UI tests?

Playwright UI tests write temporary test files to the /tmp directory for execution, meaning limitations apply based on available temporary storage and file system permissions on the machine running the automation scripts.