agentleFS
CodeWithBehnamCodeWithBehnam/cc-docs/skills/testing-quality/claude-bowser/SKILL.md

claude-bowser

Skill2 starsChanged 8 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If available: proceed with the workflow.

    line 16
  2. Very specific:

    If NOT available: stop and reply to the user: _"Chrome tools are not available.

    line 17
  3. Distinctive:

    No parallel instances: All Chrome MCP connections share a single Chrome extension controller.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Claude Bowser

Purpose

Automate browsing using Chrome MCP tools (mcp__claude_in_chrome__*) 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__claude_in_chrome__*.

  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.