playwright

Automate browser interactions from the terminal using Playwright CLI commands.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Estom/aiflex --skill playwright-estom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/openai-skills/playwright
Command: npx skills add https://github.com/Estom/aiflex --skill playwright-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes manual, error-prone browser interactions by providing terminal-first commands to open pages, capture snapshots, interact with elements, and record artifacts so users can automate UI flows, extract data, and debug visual issues without writing full test suites.

Core Features & Use Cases

  • Terminal-first browser automation: Run Playwright CLI commands (via a wrapper) to navigate, click, type, and control pages.
  • Snapshot-driven element references: Create stable element refs with snapshots and re-snapshot after navigation or DOM changes to avoid flaky selectors.
  • Artifact capture and sessions: Capture screenshots, PDFs, traces and isolate work using named sessions; store artifacts under output/playwright to keep results organized.
  • Use Cases: Rapid UI-flow debugging, form filling and submission, targeted web scraping, and reproducible manual automations triggered from the terminal.

Quick Start

Use the playwright skill to open a page, take a snapshot to capture element refs, perform the required clicks or form fills, and save a screenshot to the output/playwright folder.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate browser interactions from the terminal?

You can automate browser interactions from the terminal by running Playwright CLI commands through a wrapper script to navigate, click, type, and capture snapshots without writing full test suites.

How do I create stable element references to avoid flaky selectors during web scraping?

To avoid flaky selectors during web scraping, create stable element refs using snapshots and re-snapshot after navigation or DOM changes to maintain accurate targeting.

Do I need npx installed to use Playwright for UI debugging?

Yes, you need npx or a local Playwright CLI installation to perform terminal-based UI debugging, as the automation relies on invoking wrapper scripts through these dependencies.

What is the best way to capture screenshots and PDFs during terminal-based browser automation?

The best way to capture screenshots, PDFs, and traces during browser automation is to save artifacts directly to the output/playwright folder, keeping results organized within isolated named sessions.

Can I manage multiple isolated browser sessions for form filling and submission?

Yes, you can isolate work and manage multiple browser sessions using named sessions, which ensures that form filling and submission workflows remain reproducible and separated.

Why does my UI-flow automation fail after dynamic DOM changes?

UI-flow automation fails after dynamic DOM changes because element references become outdated; re-snapshot the page after navigation or DOM updates to refresh selectors and resolve the issue.