browser-tools

Automate Chrome navigation, evaluation, and observation via the Chrome DevTools Protocol from the command line.

97|17|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/antoniolg/agent-kit --skill browser-tools-antoniolg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-tools
Source: https://github.com/antoniolg/agent-kit/tree/main/skills/browser-tools
Command: npx skills add https://github.com/antoniolg/agent-kit --skill browser-tools-antoniolg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates Chrome navigation, evaluation, and observation through the Chrome DevTools Protocol from the command line.

Core Features & Use Cases

  • Browser automation via DevTools: navigate, evaluate JS, take screenshots, inspect DOM, and capture cookies.
  • Debug and automate repetitive tasks: collect logs, search content, and interact with pages programmatically for QA automation or data gathering.
  • Use Case: Imagine you need to verify a page loads within a performance window and capture a screenshot for each step; this tool lets you script those actions from the CLI.

Quick Start

Launch Chrome in remote-debugging mode and use the CLI to drive navigation, evaluation, and screenshots from the command line.

Frequently Asked Questions about browser-tools

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

FAQPage Schema
How do I automate Chrome navigation and take screenshots from the CLI?

To automate Chrome DevTools from the CLI, launch Chrome in remote-debugging mode, then use CLI subcommands like nav and screenshot to drive headless or headed sessions through puppeteer-core.

What is Chrome DevTools Protocol automation used for in browser testing?

Chrome DevTools Protocol automation is used for page navigation, in-page script execution, DOM inspection, and cookie access. It enables QA automation, data gathering, and repetitive task debugging across headless or headed browser sessions.

Do I need puppeteer-core and a TypeScript runtime to use this CLI tool?

Yes, you need puppeteer-core and a TypeScript runtime like tsx or Bun. The tool connects to a local Chrome remote-debugging port and requires these dependencies to execute its CLI subcommands for browser automation.

Can I execute in-page scripts and inspect DOM elements via command line?

Yes, you can execute in-page scripts and inspect DOM elements via command line. The CLI exposes eval and inspect subcommands that evaluate JavaScript and inspect the DOM directly through the Chrome DevTools Protocol.

What's the best way to capture console logs and search page content during browser automation?

The best way to capture console logs and search page content is using the console and search CLI subcommands. These commands collect logs and search content programmatically during headless or headed Chrome sessions via DevTools.

How do I access browser cookies and kill Chrome sessions from the command line?

You access browser cookies and kill Chrome sessions using the cookies and kill CLI subcommands. These commands capture cookies and terminate active debugging sessions connected through puppeteer-core.