browser-tools

Automate browser navigation, DOM inspection, and content extraction via Chrome DevTools Protocol.

1|Updated Sep 10, 2024
One-click install
npx skills add https://github.com/WillChangeThisLater/dotfiles --skill browser-tools-willchangethislater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-tools
Source: https://github.com/WillChangeThisLater/dotfiles/tree/main/pi/.pi/agent/skills/pi-skills/browser-tools
Command: npx skills add https://github.com/WillChangeThisLater/dotfiles --skill browser-tools-willchangethislater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-tools provides a cohesive set of utilities to automate interactions with web pages through the Chrome DevTools Protocol, enabling scripted navigation, DOM inspection, JavaScript evaluation, and visual checks without manual browser interaction.

Core Features & Use Cases

  • Automated browser control: start Chrome with remote debugging, connect to a session, and drive navigation.
  • DOM inspection and interaction: pick elements, read cookies, execute custom JavaScript, and capture page state.
  • Content extraction and testing: extract readable content to markdown, screenshot UI states for verification, and collect dynamic data from dashboards.
  • Use case: QA engineers can automate regression checks on web apps or developers can script data collection from dashboards.

Quick Start

Run browser-start.js to launch Chrome with remote debugging and then use browser-nav.js to browse to a URL.

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 tasks using Chrome DevTools Protocol?

Automating web tasks with Chrome DevTools Protocol involves starting Chrome with remote debugging and connecting a session to drive navigation, evaluate JavaScript, and inspect the DOM for automated testing or dynamic page scraping.

How do I extract dynamic content from web pages for scraping?

To extract dynamic content during web scraping, you can connect to a Chrome debugging session, navigate to the target URL, execute custom JavaScript to collect dashboard data, and extract readable page content directly to markdown format.

Can I use this for automated UI verification and regression testing?

Yes, you can use it for automated UI verification and regression testing by driving browser navigation to target web applications, executing DOM interactions, and capturing screenshot UI states to verify visual output without manual checks.

What is the best way to inspect DOM elements and read cookies in an automated browser session?

The best way to inspect DOM elements and read cookies is to connect to an active Chrome DevTools Protocol session, which allows you to programmatically pick elements, read session cookies, and capture the current page state.

Does browser automation via Chrome DevTools require specific dependencies or frameworks?

Browser automation via Chrome DevTools requires no external dependencies or frameworks, as it directly applies the Chrome DevTools Protocol to control navigation and content extraction through standalone scripts like browser-start.js and browser-nav.js.

Why should I use Chrome DevTools Protocol instead of other browser automation tools for dynamic pages?

Using the Chrome DevTools Protocol for dynamic pages provides direct control over browser navigation and JavaScript evaluation, offering a cohesive utility set for automated DOM inspection and content extraction without relying on external wrapper frameworks.