playwright-cli

Automate browser interactions and capture evidence using Playwright CLI.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/swongsuddee/windflu-test --skill playwright-cli-swongsuddee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-cli
Source: https://github.com/swongsuddee/windflu-test/tree/main/.agents/toolkit/playwright-skill/playwright-cli
Command: npx skills add https://github.com/swongsuddee/windflu-test --skill playwright-cli-swongsuddee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of reliably automating complex web UI interactions—navigation, form filling, auth state handling, and evidence capture—without writing a full Playwright test from scratch.

Core Features & Use Cases

  • Interactive, ref-based browser automation: Use snapshot-first workflows with element refs to drive clicks, fills, selects, uploads, screenshots, and media capture while minimizing brittle selectors.
  • Debugging and observability for flaky flows: Enable tracing, inspect console output, and monitor network activity to diagnose failures quickly with reproducible artifacts.
  • Deterministic testing via state and network control: Save and restore cookies/localStorage (state-save/state-load) and mock or intercept requests (route/unroute) to create stable scenarios.

Use case: When a regression breaks a login-to-checkout flow, snapshot the page, reproduce the failing step with trace recording, mock unstable third-party calls, and produce screenshots/traces as evidence.

Quick Start

Run browser automation by first opening the app and then taking a snapshot to identify element refs.

Frequently Asked Questions about playwright-cli

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

FAQPage Schema
How do I automate browser interactions for UI testing without writing a full Playwright test script?▼

Browser automation for UI testing can be run directly from the terminal using snapshot-first workflows with element refs to drive clicks, fills, and screenshots without writing a full Playwright test script.

How do I debug flaky web application flows using tracing and network inspection?▼

Debug flaky web application flows by enabling tracing, inspecting console output, and monitoring network activity to diagnose failures quickly with reproducible artifacts like trace recordings.

Can I reuse authenticated sessions and mock network requests for deterministic UI testing?▼

Yes, you can achieve deterministic UI testing by saving and restoring cookies/localStorage via state-save/state-load and mocking or intercepting requests using route/unroute interception.

What is the best way to capture evidence of web application failures during browser automation?▼

The best way to capture evidence of web application failures during browser automation is by taking screenshots and recording traces while reproducing the failing step.

How do I handle brittle selectors when automating complex web UI interactions?▼

Handle brittle selectors when automating complex web UI interactions by using a snapshot-first workflow that identifies element refs to safely drive actions like clicks, fills, and uploads.

Does playwright-cli support state isolation for reproducible testing scenarios?▼

Yes, playwright-cli supports state isolation for reproducible testing scenarios by using named sessions alongside state-save and state-load features to manage cookies and localStorage.