playwriter

Control the active Chrome tab via the Playwriter CLI for UI inspection and scripted actions.

357|29|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/brianlovin/agent-config --skill playwriter-brianlovin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwriter
Source: https://github.com/brianlovin/agent-config/tree/main/skills/playwriter
Command: npx skills add https://github.com/brianlovin/agent-config --skill playwriter-brianlovin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows for direct control and inspection of the user's currently open Chrome tab without launching a new browser instance, enabling real-time UI analysis and scripted interactions.

Core Features & Use Cases

  • Live UI Inspection: Inspect the current state of a live web page, including DOM structure and console output.
  • Scripted Browser Actions: Execute actions like clicks, typing, and hovering directly on the active tab.
  • Debugging & Reproduction: Capture console logs and reproduce frontend issues by interacting with the user's tab.

Quick Start

Use Playwriter to attach to the active browser tab and log the current URL.

Frequently Asked Questions about playwriter

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

FAQPage Schema
How do I inspect a live web page in my active Chrome tab?

Inspect a live web page in your active Chrome tab by attaching the Playwriter CLI to the browser to capture DOM structure, interact with UI elements, and read console output directly without launching a new browser instance.

Can I automate scripted browser actions on an existing Chrome tab?

Automate scripted browser actions on an existing Chrome tab by executing clicks, typing, and hovering directly on the active page using the Playwriter CLI, enabling real-time UI analysis and interaction without launching a new browser instance.

What do I need to debug frontend issues on an active browser tab?

Debugging frontend issues on an active browser tab requires the Playwriter CLI and a compatible Chrome extension installed and enabled to attach to the active tab, capture console logs, and reproduce issues through scripted interactions.

How does capturing console output from a live page help with debugging?

Capturing console output from a live page helps debugging by allowing you to read runtime logs and errors directly from the active Chrome tab, enabling you to reproduce frontend issues by interacting with the current UI state.

What is the best way to analyze dynamic UI elements in Chrome?

The best way to analyze dynamic UI elements in Chrome is attaching the Playwriter CLI to the active tab to inspect the live DOM structure, capture console output, and run scripted browser actions like clicks and typing on the existing page.