skills.rest
cameronmaske
cameronmaskeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browser-tools

Automate Windows Chrome via DevTools Protocol from WSL.

2|Updated Feb 3, 2026
Search Tags:#web automation#browser#Chrome DevTools Protocol#WSL#automate#remote debugging#Windows Chrome
One-click install
npx skills add https://github.com/cameronmaske/agent-stuff --skill browser-tools-cameronmaske
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-tools
Source: https://github.com/cameronmaske/agent-stuff/tree/main/skills/browser-tools
Command: npx skills add https://github.com/cameronmaske/agent-stuff --skill browser-tools-cameronmaske

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated browser control by connecting to Chrome's DevTools Protocol from WSL to automate a Windows Chrome instance.

Core Features & Use Cases

  • Web navigation, JavaScript evaluation, and content extraction via the Chrome DevTools Protocol from a WSL environment.
  • Cookie inspection, element interaction assistance, and screenshot capture to support frontend testing and automation workflows.
  • Use Case: Automate repetitive browsing tasks across Windows Chrome sessions from your Linux/WSL environment, such as verifying page titles and collecting data.

Quick Start

Use the browser-tools to navigate to https://example.com, evaluate document.title, and save a screenshot.

Frequently Asked Questions about browser-tools

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

FAQPage Schema
How do I automate Windows Chrome from a WSL environment?▼

You can automate Windows Chrome from WSL by connecting to the Chrome DevTools Protocol. This Skill enables remote debugging to control navigation, evaluate JavaScript, and extract content from a visible browser instance.

Can I run frontend tests using Chrome DevTools Protocol in WSL?▼

Yes, frontend testing is supported via Chrome DevTools Protocol in WSL. You can inspect cookies, interact with elements, evaluate JavaScript, and capture screenshots to verify page states and automate repetitive browsing tasks.

What do I need to control a Windows Chrome instance remotely from Linux?▼

You need Chrome with remote debugging enabled to control a Windows Chrome instance remotely. This allows your WSL environment to connect via the DevTools Protocol and execute navigation, data collection, and screenshot scripts.

What is the best way to extract web content and take screenshots from WSL?▼

The best way to extract web content and capture screenshots from WSL is using the Chrome DevTools Protocol. This Skill provides scripts to connect to a real browser, extract data, and save screenshots of web apps.

Does web automation via Chrome DevTools Protocol require a visible browser window?▼

Web automation via Chrome DevTools Protocol requires a visible browser window when using this specific Skill. It connects to a real Windows Chrome instance rather than running headless, making it suitable for tasks requiring visual interaction.

Why use Chrome DevTools Protocol from WSL instead of standard Linux browser automation?▼

Using Chrome DevTools Protocol from WSL allows you to automate a native Windows Chrome instance. This is necessary when your testing or data collection requires interacting with Windows-specific browser sessions rather than a Linux environment.

Related Skills

Explore More Software Engineering Skills→
ViperJuiceViperJuice
8

chrome-devtools-debugging

Inspect console logs, network traffic, and performance via Chrome DevTools Protocol.

Community
Intermediate
lvhuanidlvhuanid

web-reader

Extract text, HTML, and metadata from web pages using z-ai-web-dev-sdk.

Community
Intermediate
tharunramagiritharunramagiri

agent-browser

Automate web navigation, element interaction, and data extraction via a headless browser.

Community
Advanced
jameinghjameingh

chrome-automation

Automate Chrome browser actions via CDP with live visual feedback.

Community
Advanced