playwright-skill

Automate browser tasks and testing with Playwright scripts.

Updated Nov 19, 2025
One-click install
npx skills add https://github.com/paulokakoma/ecokambio --skill playwright-skill-paulokakoma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/paulokakoma/ecokambio/tree/main/.cursor/skills/playwright-skill
Command: npx skills add https://github.com/paulokakoma/ecokambio --skill playwright-skill-paulokakoma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser tasks and testing using Playwright to simplify web QA.

Core Features & Use Cases

  • Auto-detects running dev servers and selects the target URL
  • Writes custom Playwright scripts to /tmp/playwright-test-*.js to avoid project clutter
  • Executes automation via the universal run.js wrapper with visible browser by default
  • Parameterizes URLs and supports environment-based header injection for automated traffic identification
  • Provides helper utilities (lib/helpers.js) for robust interactions, waiting, and common patterns

Quick Start

Describe the browser task and I will auto-detect dev servers, generate a /tmp/playwright-test-*.js script, and run it via 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 automate web testing and validate login flows against a local dev server?

Browser automation for QA works by writing custom Playwright scripts that execute via a universal run.js wrapper with a visible browser by default. It reduces manual web QA by automating interactions, waiting, and capturing screenshots against local dev servers or provided URLs.

What's the best way to capture screenshots and check responsive design during web automation?

Playwright browser testing requires the Playwright package to be installed in your environment. The automation skill handles script generation, dev server auto-detection, and execution via run.js, but it does not install the underlying Playwright dependency itself.

Do I need Playwright installed to run browser testing scripts for form validation?

Playwright automation supports parameterizing URLs and injecting environment-based headers for automated traffic identification. This allows you to configure scripts dynamically and route automated browser traffic through specific proxies or identify it within network monitoring tools.

Can I inject custom headers for automated traffic identification in Playwright automation?

Playwright web automation keeps your project clean by writing generated test scripts to the /tmp directory as temporary files. This avoids project clutter while allowing the universal run.js executor to run the browser tasks seamlessly without modifying your codebase.

Why does browser automation write scripts to /tmp instead of my project directory?

Playwright browser testing can validate forms, capture screenshots, check responsive design, and validate login flows. Helper utilities provide robust interactions and waiting patterns to handle common browser automation challenges against local dev servers or provided URLs.