browser

Automate Chrome via Chrome DevTools Protocol without extensions or MCP tooling.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/roach88/claude-config --skill browser-roach88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/roach88/claude-config/tree/main/skills/browser
Command: npx skills add https://github.com/roach88/claude-config --skill browser-roach88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need to install browser extensions or configure MCP tools for common browser automation tasks like web scraping, screenshot capture, and page interaction, cutting down time spent on repetitive web workflows.

Core Features & Use Cases

  • No-Extension Chrome Control: Automate Chrome directly via Chrome DevTools Protocol, no extra browser add-ons or MCP setup required.
  • Comprehensive Browser Commands: Extract page content as markdown, capture viewport screenshots, read console logs, navigate to URLs, run JavaScript, dump cookies, and manage CDP processes.
  • Real-World Use Case: Scrape product pricing from e-commerce sites, capture screenshots of web app bugs for documentation, or automate test form submissions without manual browser interaction.

Quick Start

Use the browser skill to extract all text content from the webpage at https://example.com and save a full viewport screenshot to /tmp/example-page.png.

Frequently Asked Questions about browser

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

FAQPage Schema
How do I automate Chrome browser tasks without installing extensions?

You can automate Chrome browser tasks without extensions by using Chrome DevTools Protocol (CDP). This approach enables web scraping, screenshot capture, and page interaction directly through CDP commands.

How do I scrape web page content and capture a screenshot via CDP?

To scrape web page content and capture screenshots via CDP, use the browser-tools CLI utility. It extracts page content as markdown, captures viewport screenshots, and retrieves console logs from a local Chrome instance.

Do I need to launch Chrome with specific settings to use CDP automation?

Yes, CDP automation requires a local Chrome instance launched with CDP enabled on port 9222. You also need the browser-tools CLI utility installed to execute deterministic browser control commands.

What browser automation commands are available through Chrome DevTools Protocol?

Available CDP browser automation commands include extracting page content as markdown, capturing viewport screenshots, reading console logs, running JavaScript, dumping cookies, and managing automated browser navigation workflows.

Does this browser automation approach work without MCP tooling?

Yes, this browser automation approach works without MCP tooling. It leverages Chrome DevTools Protocol directly, removing the need to configure MCP tools or install browser extensions for common web scraping and page interaction workflows.