Browser logo

Browser

Community
GGPrompts
browser

Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.

Overview

PublisherGGPrompts
RepositoryTabzChrome
Skill namebrowser
Stars
147
Forks
10
Bundled files
10
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 10 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by GGPrompts on GitHub. Read the source before you install it.

Installation

Install the Browser AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/GGPrompts/TabzChrome.git /tmp/TabzChrome
mkdir -p .claude/skills
cp -r /tmp/TabzChrome/plugins/tabz/skills/browser .claude/skills/browser
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Browser in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Browser on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Browser is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

TabzChrome Browser Automation

Control Chrome via MCP tools for screenshots, interaction, debugging, and notifications.

Quick Start

Use mcp-cli to discover and call tools:

bash
# Get tool schema (REQUIRED before calling)
mcp-cli info tabz/tabz_screenshot

# Call tool
mcp-cli call tabz/tabz_screenshot '{}'

Core Workflows

Screenshot a Page

bash
# Get current tab info
mcp-cli call tabz/tabz_get_page_info '{}'

# Take screenshot
mcp-cli call tabz/tabz_screenshot '{}'
# Returns file path - use Read tool to view

Debug Network/API Issues

bash
# 1. Enable capture BEFORE triggering action
mcp-cli call tabz/tabz_enable_network_capture '{}'

# 2. Trigger the action on page

# 3. Get failed requests (status >= 400)
mcp-cli call tabz/tabz_get_network_requests '{"statusMin": 400}'

# 4. Check console for JS errors
mcp-cli call tabz/tabz_get_console_logs '{"level": "error"}'

Test Responsive Design

bash
# Emulate device
mcp-cli call tabz/tabz_emulate_device '{"device": "iPhone 14"}'

# Take screenshot
mcp-cli call tabz/tabz_screenshot '{}'

# Clear emulation
mcp-cli call tabz/tabz_emulate_clear '{}'

Fill and Submit Form

bash
mcp-cli call tabz/tabz_fill '{"selector": "#email", "value": "test@example.com"}'
mcp-cli call tabz/tabz_click '{"selector": "button[type=submit]"}'

Notify User (TTS)

bash
mcp-cli call tabz/tabz_speak '{"text": "Task complete"}'

Performance Profiling

bash
mcp-cli call tabz/tabz_profile_performance '{}'
# Returns: DOM nodes, JS heap, event listeners, timing

DOM Tree Inspection

bash
mcp-cli call tabz/tabz_get_dom_tree '{"maxDepth": 3}'

Tool Categories

CategoryCountKey Tools
Screenshots2screenshot, screenshot_full
Interaction4click, fill, get_element
Network3enable_network_capture, get_network_requests
DOM/Debug4get_dom_tree, get_console_logs, profile_performance
Emulation6emulate_device, emulate_geolocation
Audio/TTS3speak, list_voices, play_audio
Tabs5list_tabs, open_url, switch_tab
Cookies5cookies_get, cookies_list

Important Notes

  • Always run mcp-cli info tabz/<tool> before calling
  • Use explicit tabId when possible - don't rely on "active" tab
  • Tab IDs are large integers (e.g., 1762561083)
  • tabz_screenshot cannot capture Chrome sidebar

References

See references/ for detailed workflows and full tool documentation:

Quick Guides

  • screenshot-workflows.md - Viewport vs full page screenshots
  • network-debugging.md - API request inspection
  • form-automation.md - Clicks, fills, selectors
  • tts-notifications.md - Audio feedback patterns

Full MCP Tool Documentation

  • core-tools.md - Tabs, screenshots, clicks, fills, DOM inspection
  • windows-groups.md - Windows, tab groups, multi-window workflows
  • network-downloads.md - Network capture, downloads, file operations
  • browser-data.md - History, sessions, cookies, bookmarks
  • profiles-and-plugins.md - Terminal profiles, Claude Code plugin management
  • advanced-tools.md - Emulation, performance profiling, notifications

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Browser AI skill do?

Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.

Why use Browser on TypingMind?

Because you install it once and use it with any model. Browser is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/GGPrompts/TabzChrome/tree/main/plugins/tabz/skills/browser. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Browser?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser?

As many as you like. As long as a model supports skills, you can use Browser with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser AI skill free?

Yes. It is published on GitHub by GGPrompts under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇