browser-tools

Automates browser control via ChromeDevToolsProtocol for scraping, testing, and exploration.

Updated Nov 3, 2025
One-click install
npx skills add https://github.com/Thomas-TyTech/browser-skill --skill browser-tools-thomas-tytech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-tools
Source: https://github.com/Thomas-TyTech/browser-skill/tree/main
Command: npx skills add https://github.com/Thomas-TyTech/browser-skill --skill browser-tools-thomas-tytech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires puppeteer-core, and includes scripts (resource) components.

What problem does it solve?

Minimal CDP-based browser automation tools that empower teams to explore, test, and scrape web pages without the overhead of large MCP servers.

Core Features & Use Cases

  • Start Chrome with remote debugging and manage profiles to preserve or avoid cookies.
  • Navigate to URLs, open new tabs, and wait for the DOM to load for reliable interactions.
  • Execute JavaScript in the active page context and format results for analysis.
  • Take viewport screenshots and return the image path for visual debugging.
  • Interactive element selection to identify DOM structure and build robust selectors.
  • Cookie extraction for authenticated scraping and session debugging.

Quick Start

Launch Chrome with remote debugging using browser-tools-start and begin interacting with pages using the remaining tools.

Frequently Asked Questions about browser-tools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate web scraping using Chrome DevTools Protocol?

Automate web scraping using Chrome DevTools Protocol by executing deterministic scripts to navigate URLs, wait for DOM loads, and extract cookies for authenticated sessions. This lightweight approach provides reliable browser control without large server overhead.

Do I need a locally running Chrome instance for puppeteer-core browser automation?

Yes, puppeteer-core browser automation requires a locally running Chrome instance with remote debugging enabled. You must launch Chrome with remote debugging using the dedicated startup tool before interacting with pages or executing JavaScript.

What is the best way to build robust DOM selectors for automated browser testing?

Build robust DOM selectors for automated browser testing using interactive element selection tools. These identify the loaded page's DOM structure, allowing you to construct reliable selectors for deterministic scripting and reliable interactions.

Can I execute JavaScript in an active page context for web scraping?

Yes, you can execute JavaScript in the active page context for web scraping. The toolkit runs custom JavaScript within the active page and formats the execution results specifically for immediate analysis within AI-driven workflows.

How does token-efficient browser automation work for AI workflows?

Token-efficient browser automation works by using a focused set of CLI tools and a minimal MCP-compatible server to interact with Chrome DevTools Protocol. This lightweight footprint minimizes token consumption during AI-driven site exploration and automated testing.

Why does my browser automation script fail to capture authenticated session cookies?

Browser automation scripts fail to capture authenticated session cookies when Chrome profiles are not managed correctly. You must manage profiles to preserve cookies or start a fresh session before extracting cookies for authenticated scraping and session debugging.