playwright

Automate browser interactions from the terminal using Playwright CLI.

Updated Apr 4, 2026

Search Tags:#screenshots #cli #tracing #playwright #headless #browser-automation #wrapper

Ready to run

npx skills add https://github.com/hellitonsm/genesis-project --skill playwright-hellitonsm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/hellitonsm/genesis-project/tree/main/tools/auto_browser_recorder/playwright
Command: npx skills add https://github.com/hellitonsm/genesis-project --skill playwright-hellitonsm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Drive browser automation from the command line using Playwright CLI, reducing manual testing effort and enabling reproducible workflows.

Core Features & Use Cases

CLI-first automation: open pages, interact with elements, take snapshots, capture traces, and generate artifacts all from shell commands.
Wrapper-friendly: use the bundled wrapper script so the CLI runs even when not globally installed, with optional global install.
Sessions and multi-tab workflows: manage named sessions, multiple tabs, and headed mode for visual validation in automation tasks.

Quick Start

Install the wrapper, set CODEX_HOME and PWCLI, then run a simple open workflow with the wrapper to start browser automation.

Frequently Asked Questions about playwright

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

FAQPage Schema

How do I automate browser interactions from the terminal using Playwright?▼

You can automate browser interactions from the terminal by using the Playwright CLI wrapper script to open pages, fill forms, and capture snapshots without writing test specs. It requires npx availability and supports installation via CODEX_HOME.

Can I capture screenshots and traces in headless browser automation workflows?▼

Yes, capturing screenshots and traces in headless browser automation is supported directly from the shell. The CLI-first automation workflow allows you to generate artifacts and take snapshots across multiple tabs or named sessions.

Do I need to install Playwright globally to run CLI automation scripts?▼

You do not need to install Playwright globally to run CLI automation scripts. The bundled wrapper script ensures the Playwright CLI runs even when not globally installed, though optional global installation is available.

What is the best way to manage multiple tabs and sessions in browser automation?▼

The best way to manage multiple tabs and sessions in browser automation is using the Playwright CLI wrapper. It supports named sessions, multi-tab workflows, and headed mode for visual validation during your automation tasks.

Does this Playwright wrapper support writing traditional test specs?▼

This wrapper emphasizes CLI usage over traditional Playwright test specs. It is designed for CLI-first automation workflows such as opening pages, interacting with elements, and generating artifacts directly from shell commands.

Why are my Playwright CLI snapshots and artifacts not generating correctly?▼

Snapshots and artifacts may fail to generate if the wrapper script is not configured correctly or npx is unavailable. Ensure CODEX_HOME and PWCLI are set properly, as the wrapper provides specific safeguards for snapshot and artifact generation.