playwright

Automate browser navigation and UI interactions via Playwright CLI with snapshot-based element targeting.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/wtgoku-create/PopiStudio --skill playwright-wtgoku-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/wtgoku-create/PopiStudio/tree/main/SKILLs/playwright
Command: npx skills add https://github.com/wtgoku-create/PopiStudio --skill playwright-wtgoku-create

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It eliminates the pain of manually repeating browser steps when you need reliable navigation, clicking, form filling, screenshots, and data extraction.

Core Features & Use Cases

  • Browser automation from the terminal: Drive a real browser using Playwright CLI for navigation, UI interaction, and artifact capture.
  • Snapshot-driven element targeting: Generate stable element refs, then interact using those refs and re-snapshot when the UI changes.
  • Debug and inspection workflows: Capture traces, open DevTools console/network views, and iterate on failing UI flows.
  • Common scenarios: Login and form submission, UI regression troubleshooting, and extracting values like titles or page text from dynamic pages.

Quick Start

Use the Playwright skill to open a page, snapshot elements, and then interact with a specific element ref to verify the UI behavior.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate web scraping and browser navigation from the terminal?

You can automate web scraping and browser navigation from the terminal using playwright-cli. It drives a real browser to perform reliable navigation, UI interaction, and artifact capture like screenshots and PDFs.

How do I fix stale element references during dynamic web UI automation?

To fix stale element references during web UI automation, use snapshot-driven element targeting. Generate stable element refs, interact using those refs, and re-snapshot when the UI changes to maintain stable targeting.

Can I capture screenshots and PDFs during automated browser flows?

Yes, you can capture screenshots and PDFs during automated browser flows. The automation supports artifact capture alongside form filling and element-based clicking across pages or tabs.

What is the best way to debug complex multi-step web UI workflows?

The best way to debug complex web UI workflows is by capturing traces and opening DevTools console or network views. This allows you to inspect and iterate on failing UI flows effectively.

Does browser automation with playwright-cli require npx to run?

Yes, browser automation with playwright-cli requires npx to run. It uses a bundled npx-based wrapper for terminal-first execution to drive the real browser and manage snapshot practices.

Why does my automated browser flow fail when the DOM changes?

Automated browser flows fail when the DOM changes because element references become stale. You need to apply snapshot and trace practices to recover from DOM changes and maintain stable element targeting.