bowser
Headless browser automation using Playwright CLI. Use when you need headless browsing, parallel browser sessions, UI testing, screenshots, web scraping, or browser automation that can run in the background. Keywords - playwright, headless, browser, test, screenshot, scrape, parallel.
Install
With your agent
Install OMGSkills skill "disler/pi-vs-claude-code:.pi/skills/bowser" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/disler/pi-vs-claude-code /tmp/pi-vs-claude-code && ln -s /tmp/pi-vs-claude-code/.pi/skills/bowser ~/.claude/skills/bowserFrom README
Playwright Bowser Purpose Automate browsers using playwright-cli — a token-efficient CLI for Playwright. Runs headless by default, supports parallel sessions via named sessions (-s=), and doesn't load tool schemas into context. Key Details Headless by default — pass --headed to open to see the browser Parallel sessions — use -s= to run multiple independent browser instances Persistent profiles — cookies and storage state preserved between calls Token-efficient — CLI-based, no accessibility trees or tool schemas in context Vision mode (opt-in) — set PLAYWRIGHTMCPCAPS=vision to receive screenshots as image responses in context instead of just saving to disk Sessions Always use a named session. Derive a short, descriptive kebab-case name from the user's prompt. This gives each task a persistent browser profile (cookies, localStorage, history) that accumulates across calls.
More skills
Create New Skills
Creates new Agent Skills for Claude Code following best practices and documentation.
create-worktree-skill
Used when the user explicitly asks for a SKILL to create a worktree.
Damage Control
Install, configure, and manage the Claude Code Damage Control security hooks system.