playwright-cli

Automate browser interactions and Playwright test execution for web pages.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/bastani-inc/atomic --skill playwright-cli-bastani-inc
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: playwright-cli
Source: https://github.com/bastani-inc/atomic/tree/main/packages/subagents/skills/playwright-cli
Command: npx skills add https://github.com/bastani-inc/atomic --skill playwright-cli-bastani-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of manually driving browsers for testing, debugging, and routine web workflows by providing a structured way to inspect pages, act on elements, and verify outcomes.

Core Features & Use Cases

It supports browser opening and navigation, element snapshots and semantic targeting, form interaction, tab and session management, storage handling, request mocking, tracing, and video capture.

It is ideal for running Playwright tests, debugging failing UI flows, reproducing bugs, generating test code from interactions, and inspecting page behavior across multiple isolated browser sessions.

Quick Start

Use playwright-cli to open the target page, inspect the snapshot, and carry out the browser interaction you want to test or automate.

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 and UI testing for web pages?ā–¼

Automate browser interactions by opening target pages, inspecting element snapshots, and orchestrating commands for form entry, navigation, and UI testing. This structured approach replaces manual browser driving with deterministic, inspectable runs for testing and debugging web workflows.

Can I manage multi-tab browser sessions and capture video during test execution?ā–¼

Multi-tab browser session management and video capture are supported during test execution. You can isolate multiple browser sessions, handle storage, and record video to inspect page behavior and reproduce bugs across distinct isolated environments.

What is the best way to debug failing UI flows and reproduce browser bugs?ā–¼

Debug failing UI flows and reproduce browser bugs using tracing and element snapshots. By capturing semantic targeting data and inspecting page behavior in isolated sessions, you can identify failure points and verify outcomes with deterministic test execution.

Does this browser automation approach support request mocking and storage handling?ā–¼

Request mocking and storage handling are supported within the browser automation workflow. You can intercept network requests, mock responses, and manage storage state to ensure deterministic, inspectable runs for UI testing and routine web workflows.

How do I target page elements reliably for web page automation without flaky selectors?ā–¼

Target page elements reliably using snapshot-based semantic targeting for web page automation. Instead of relying on flaky selectors, inspect the page snapshot to identify elements and orchestrate browser commands for deterministic interaction.

Why use snapshot-based element targeting for browser test generation instead of raw selectors?ā–¼

Snapshot-based element targeting provides semantic context for browser test generation, ensuring deterministic and inspectable runs. Unlike raw selectors, snapshots capture the page's accessible structure, allowing reliable form interaction, navigation, and UI testing.