disler/bowser · Archived

claude-bowser

Observable browser automation using Chrome MCP tools. Use when you need to browse websites, take screenshots, interact with web pages, or perform browser tasks in your current Chrome. Keywords - browse, screenshot, browser, chrome, bowser, ui testing, observable.

First seen Feb 22, 2026

Installation

$ npx skills add disler/bowser --skill claude-bowser

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from disler/bowser.

npx skills add disler/bowser

Browse all from disler/bowser

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 254
Default branch main
Open issues 2
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,312 B
  • docs SUMMARY.md 284 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

Claude Bowser

Purpose

Automate browsing using Chrome MCP tools (mcp__claudeinchrome__*) available when Claude Code is started with --chrome. This uses your real Chrome browser — observable, with your existing profile, cookies, and extensions.

Pre-flight Check

Before doing anything, verify Chrome MCP tools are available. Look for tools matching mcp__claudeinchrome__*.

  • If available: proceed with the workflow.
  • If NOT available: stop and reply to the user: "Chrome tools are not available. Please restart Claude Code with the --chrome flag: claude --chrome"

Workflow

  1. Resize the browser window to 1440x900
  2. Execute the user's request using Chrome MCP tools (navigate, click, screenshot, etc.)
  3. Report results back to the user

Limitations

  • No parallel instances. All Chrome MCP connections share a single Chrome extension controller. Only one bowser task at a time.
  • Observable only. This uses your real Chrome — there is no headless mode.