playwright-cli

Operate a live browser via command line with Playwright.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/tom-xs/nixos-dotfiles --skill playwright-cli-tom-xs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-cli
Source: https://github.com/tom-xs/nixos-dotfiles/tree/main/ai/kimi-skills/skills/playwright-cli
Command: npx skills add https://github.com/tom-xs/nixos-dotfiles --skill playwright-cli-tom-xs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the friction of manual browser testing and automation by allowing you to control a live browser instance directly from your command line, eliminating the need for constant context switching between your editor and the browser.

Core Features & Use Cases

  • Live Browser Control: Navigate, click, type, and interact with web elements in real-time using simple CLI commands.
  • Automated Evidence Capture: Instantly generate screenshots, PDF exports, and network traces for debugging or documentation.
  • Session Management: Isolate multiple browser contexts for concurrent testing, A/B experiments, or authenticated state persistence.

Quick Start

Use the playwright-cli skill to open a browser at the specified URL and take a snapshot of the page elements.

Frequently Asked Questions about playwright-cli

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

FAQPage Schema
How do I control a live browser session from the command line?

You can control a live browser session from the command line by using Playwright CLI to navigate, click, type, and interact with web elements in real-time without switching context to a browser window.

Can I generate screenshots and network traces for debugging without running a full test suite?

Yes, you can generate screenshots, PDF exports, and network traces for debugging or documentation through interactive browser automation, satisfying visual evidence generation requirements without executing a full test suite.

Does Playwright CLI support managing multiple authenticated browser states for A/B testing?

Yes, Playwright CLI supports session management by isolating multiple browser contexts, enabling concurrent testing, A/B experiments, and authenticated state persistence across different interactive browser automation sessions.

What is the best way to inspect web elements and mock network requests during end-to-end testing?

The best way to inspect web elements and mock network requests is using a command-line interface for interactive browser automation, which facilitates direct element inspection and network request mocking for end-to-end testing workflows.

Do I need a full test suite execution to automate headless browser control and state persistence?

No, you do not need a full test suite execution; the Playwright CLI provides headless browser control, state persistence, and automated test generation directly from your terminal for web applications.

Why use a command-line interface for browser automation instead of manual browser testing?

Using a command-line interface for browser automation eliminates the friction of manual testing and constant context switching between your editor and browser, allowing you to drive live browser instances directly from your terminal.