playwright-browser

Automate browser navigation, interaction, and screenshot capture via Playwright CLI.

5|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/Bind/skillz.sh --skill playwright-browser-bind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-browser
Source: https://github.com/Bind/skillz.sh/tree/main/docs/registry/skills/playwright-browser
Command: npx skills add https://github.com/Bind/skillz.sh --skill playwright-browser-bind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated control of a Playwright browser from the command line, enabling rapid testing, QA checks, and scripted web interactions without a GUI.

Core Features & Use Cases

  • Persistent browser sessions for long-running tasks and debugging.
  • Navigate to URLs, type into elements, click, and capture screenshots.
  • Use Case: Automate a quick site check on a page and save a visual result for QA reports.

Quick Start

Start a persistent session and run a sequence: bun .opencode/skill/playwright-browser/session.js start bun .opencode/skill/playwright-browser/navigate.js https://example.com bun .opencode/skill/playwright-browser/snapshot.js bun .opencode/skill/playwright-browser/type.js "input[name='q']" "skill search" --press Enter bun .opencode/skill/playwright-browser/click.js "link:GitHub" bun .opencode/skill/playwright-browser/screenshot.js --output result.png

Frequently Asked Questions about playwright-browser

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

FAQPage Schema
How do I automate browser interaction and capture screenshots from the command line?

You can automate browser interaction by running Playwright CLI scripts to navigate URLs, type into elements, click, and capture screenshots directly from the command line without a GUI.

Can I maintain a persistent browser session for long-running automated testing tasks?

Yes, you can start a persistent browser session to manage long-running automated testing tasks, allowing you to execute sequential navigation and interaction commands while debugging.

How do I perform web automation on specific page elements using a CLI?

You perform web automation by executing CLI commands that target specific page elements, enabling you to type text into input fields, click links, and capture page snapshots for QA workflows.

Does this browser automation approach require a graphical user interface?

No, this browser automation approach relies entirely on CLI commands to control the Playwright browser, enabling scripted web interactions and rapid QA checks without launching a GUI.

What is the best way to script a quick site check and save a visual result for QA?

The best way to script a quick site check is to start a session, navigate to the target URL, interact with elements, and use a screenshot command to save a visual result for QA reports.

Are there limitations when using CLI commands for web automation instead of a full testing framework?

Relying on CLI commands for web automation limits you to sequential script execution for navigation and interaction, making it best suited for rapid QA checks rather than complex automated testing suites.