playwright

Automate browser navigation, form filling, and artifact capture via Playwright CLI.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Canepro/codex-skills --skill playwright-canepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/Canepro/codex-skills/tree/main/skills/playwright
Command: npx skills add https://github.com/Canepro/codex-skills --skill playwright-canepro

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Drive a real browser from the terminal using Playwright CLI to automate navigation, form filling, and evidence collection in a CLI-first workflow for development, testing, and debugging.

Core Features & Use Cases

  • Wrapper-driven browser automation that works without a global install, enabling consistent automation in diverse environments
  • Stateful sessions with multi-tab support, element stabilization via snapshots, and artifact capture (screenshots, traces, pdfs) for reproducible results
  • Guardrails and practical patterns for reliable UI flows, debugging, and rapid iteration in engineering and QA

Quick Start

Open a browser with the wrapper and run a simple sequence like open https://playwright.dev followed by a snapshot.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate real browser interactions from the terminal using Playwright?

Browser automation from the terminal uses a wrapper script to drive Playwright CLI, executing navigation, form filling, and evidence capture without a global install. This approach enables consistent, reproducible workflows across diverse environments.

Can I capture screenshots and traces during web automation without a global Playwright install?

Yes, web automation captures artifacts like screenshots, traces, and PDFs through a wrapper-driven script. It leverages Playwright CLI via npx, ensuring reproducible evidence collection in CLI-first workflows without requiring global installation.

Does CLI-first browser automation support multi-tab sessions and element stabilization?

CLI-first browser automation supports stateful sessions with multi-tab navigation and element stabilization via snapshots. This ensures reliable UI flows and stable selectors for deterministic browser actions during testing and debugging.

What do I need to run Playwright browser automation from the command line?

Running Playwright browser automation requires a Node.js environment with npx availability. The wrapper script orchestrates Playwright MCP and CLI dependencies to execute browser actions deterministically without needing a global package install.

What is the best way to debug UI flows during CLI-based web automation?

The best way to debug UI flows during CLI-based web automation involves using snapshots for stable selectors and capturing artifacts like traces. The wrapper provides guardrails and practical patterns for rapid iteration and reliable debugging.

Why use a wrapper script for browser automation instead of running Playwright CLI directly?

A wrapper script orchestrates Playwright CLI and MCP to run browser actions deterministically, providing stateful sessions and guardrails. This ensures reproducible results and consistent automation across diverse environments compared to direct CLI execution.