playwright

Automate browser navigation, form filling, screenshots, and data extraction via Playwright CLI.

Updated Sep 1, 2025
One-click install
npx skills add https://github.com/mathur-exe/annotation-notes --skill playwright-mathur-exe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/mathur-exe/annotation-notes/tree/main/PaperNotes/dotfiles/codex/skills/playwright
Command: npx skills add https://github.com/mathur-exe/annotation-notes --skill playwright-mathur-exe

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Drive browser automation from the command line to simplify repetitive UI tasks, testing workflows, and data extraction without relying on a GUI or heavy test scaffolds.

Core Features & Use Cases

  • CLI-first automation: Control a real browser via a lightweight wrapper script, with optional global installs.
  • Open, snapshot, and interact: Navigate pages, capture stable element refs, and perform actions like click, type, and extract data.
  • Artifact capture: Save screenshots, traces, and other artifacts to document flows and troubleshoot issues in CLI workflows.

Quick Start

Open a site, take a snapshot, and perform interactions using the wrapper script.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate browser navigation and form filling from the terminal?

You can automate browser tasks from the terminal using a lightweight wrapper script to execute Playwright actions like navigation, form filling, and data extraction without a GUI. The CLI-driven workflow operates a real browser directly.

Do I need Node.js and npm installed to run CLI browser automation?

Yes, CLI browser automation requires Node.js and npm to be installed. The wrapper script also needs the @playwright/mcp package so it can run via npx when a global CLI is not installed on your local environment.

Can I capture screenshots and traces during CLI-driven browser scripting?

Yes, CLI-driven browser scripting supports artifact capture, allowing you to save screenshots, traces, and other artifacts. This helps document your automation flows and troubleshoot issues directly within your command line workflows.

What is the best way to extract data from web pages without a heavy test scaffold?

Data extraction from web pages without heavy test scaffolds is achieved through CLI-first automation. You control a real browser via a wrapper script to open sites, snapshot stable element refs, and extract data directly from the terminal.

Are there limitations to using a wrapper script for browser automation in local environments?

The wrapper script approach is designed for CLI-driven workflows across local environments. It requires Node.js, npm, and the @playwright/mcp package to run via npx, which may limit execution in environments lacking these dependencies.