web-browser

Automate browser tasks via Chrome DevTools Protocol with 36 scripts.

18|3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Dwsy/agent --skill web-browser-dwsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-browser
Source: https://github.com/Dwsy/agent/tree/main/skills/web-browser
Command: npx skills add https://github.com/Dwsy/agent --skill web-browser-dwsy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill eliminates the tedium of manual web automation by providing a fully isolated, script-driven browser automation toolkit that runs a standalone Chrome/Chromium instance via the Chrome DevTools Protocol (CDP).

Core Features & Use Cases

  • Independent browser instance ensures your main browser remains unaffected.
  • 36 scripts cover navigation, form interactions, data extraction, storage, network monitoring, and debugging for web tasks.
  • Use cases include web research, data extraction, automated testing, and monitoring across dynamic sites.
  • It supports persistent cookies and localStorage between restarts for session reuse.

Quick Start

Run node demo.js to verify the setup and experience end-to-end browser automation.

Frequently Asked Questions about web-browser

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

FAQPage Schema
How do I automate web scraping with a standalone Chrome instance using CDP?

Web scraping automation is achieved by controlling an isolated Chrome/Chromium instance via the Chrome DevTools Protocol (CDP). This Skill provides 36 scripts spanning navigation, interaction, and data extraction to automate tasks across dynamic sites without affecting your main browser.

Can I use puppeteer-core for form automation while keeping persistent cookies and localStorage?

Form automation with persistent cookies and localStorage is supported through puppeteer-core and CDP integration. The Skill maintains an isolated browser environment that preserves session storage between restarts, enabling seamless session reuse for repeated automated testing or monitoring tasks.

Does browser automation through Chrome DevTools Protocol require an isolated browser environment?

Chrome DevTools Protocol automation requires an isolated browser instance to ensure your main browser remains unaffected. This Skill manages standalone Chrome/Chromium execution with dedicated port management and persistent storage, providing a safe environment for web research and automated testing.

What is the best way to monitor network requests during automated web testing with puppeteer-core?

Network monitoring during automated web testing is handled by the Skill's dedicated network scripts built on puppeteer-core and chrome-remote-interface. It captures network activity within the isolated CDP browser session, allowing detailed debugging and monitoring across diverse sites.

How to run end-to-end browser automation scripts for web data extraction?

End-to-end browser automation scripts for data extraction are executed by running the provided demo.js file. This verifies the setup and demonstrates the 36 scripted capabilities, covering navigation, form interactions, and data extraction through the standalone Chrome instance.

Why should I use a standalone Chromium instance instead of my main browser for automated testing?

A standalone Chromium instance ensures your main browser configuration, cookies, and sessions remain completely unaffected by automated testing. This isolation prevents data corruption and allows persistent storage management tailored specifically for CDP-driven web scraping and monitoring tasks.