playwright-skill

Playwright browser automation auto-detects running dev servers and writes targeted testing scripts to /tmp. The universal executor then runs these scripts in an isolated environment, enabling reliable QA without manual interaction.

No, you do not need to pre-install Playwright to run browser automation scripts. The universal executor automatically installs Playwright if it is missing from the environment before executing your scripts.

The best way to execute web automation scripts is using a universal executor that writes custom Playwright scripts to /tmp. This ensures runtime execution happens in a clean, isolated environment for safe QA checks.

Yes, you can pass custom headers during Playwright web automation tasks. The skill supports environment-based headers through its helper utilities, allowing robust interaction and navigation during browser testing.

The universal executor handles Playwright script execution by writing prepared scripts to /tmp and running them in a clean environment. It auto-installs Playwright if missing and applies helper utilities for navigation and assertions.

Running browser automation in /tmp provides an isolated environment for QA checks but may lack persistent storage across sessions. Scripts are executed via a universal executor that writes to /tmp to ensure clean runtime execution.