playwright-browser

What This Skill Does

The playwright-browser skill provides a robust, reliable, and headless automation layer for the Clawdbot agent. By leveraging Playwright’s Chromium-based engine, this tool enables complex browser interaction within WSL (Windows Subsystem for Linux) and Linux-based production environments. It automates the installation of the specific browser binary, ensures all required system-level dependencies (such as NSS and ALSA) are present, and generates the necessary configuration patches for Clawdbot to interact with web interfaces. It is designed to overcome common containerization hurdles, such as sandbox restrictions and missing GUI libraries, by enabling headless operation.

Installation

To get started quickly, run the bundled automation script: ./scripts/setup.sh. This handles installation of Playwright, Chromium binaries, and system libraries. For manual control, execute npx playwright install chromium, verify your library dependencies with apt-get, locate the binary via the find utility, and patch your configuration using clawdbot config patch '{"browser": {"executablePath": "...", "headless": true, "noSandbox": true}}'. You may also install directly via the package manager: clawhub install openclaw/skills/skills/maverick-software/playwright-headless-browser.

Use Cases

This skill is ideal for web scraping, automated regression testing of web applications, performing authenticated actions on modern SPAs, and monitoring data changes on websites that require JavaScript execution. It is particularly useful for developers working in restricted terminal environments where a standard desktop browser cannot be launched.

Example Prompts

1. "Use the playwright browser to navigate to https://status.example.com and tell me if any services are currently reporting an outage."
2. "Open the dashboard at localhost:8080 using headless chromium, find the element with ID 'submit-button', and trigger a click."
3. "Scrape the article titles from the tech news section of the website using the playwright tool and save them to a markdown file."

Tips & Limitations

Always ensure that noSandbox is set to true if you are operating inside a Docker container or WSL, as the kernel namespaces in those environments often conflict with Chromium's default sandbox security model. Note that headless mode is significantly more performant and uses fewer system resources than standard headful mode. If you need to debug a visual issue, you can temporarily switch headless to false, but verify that your environment has X11 forwarding or WSLg properly configured, otherwise the process will fail to initiate a display connection.