skills.rest
ViperJuice
ViperJuiceCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browser-automation

Automate browser tasks with Playwright and Chrome DevTools Protocol.

Updated Aug 27, 2026
Search Tags:#automation#testing#debugging#playwright#cdp#chrome#browser
One-click install
npx skills add https://github.com/ViperJuice/dotfiles --skill browser-automation-viperjuice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-automation
Source: https://github.com/ViperJuice/dotfiles/tree/main/claude-config/skills/browser-automation
Command: npx skills add https://github.com/ViperJuice/dotfiles --skill browser-automation-viperjuice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide and tools for automating browser interactions, testing web interfaces, and debugging browser-based applications, offering solutions for various scenarios from simple screenshots to complex extension debugging.

Core Features & Use Cases

  • Playwright Plugin: Automates browser tasks like navigation, screenshots, and form filling in an isolated Chromium instance.
  • CDP Connection: Connects to a running headed Chrome instance for real-time inspection and interaction.
  • Extension Debugging: Guides on using CDP or claude-in-chrome for debugging browser extensions.
  • Use Case: Automatically fill out a web form on a staging environment, take a screenshot of the result, and then inspect the browser's console logs for errors.

Quick Start

Use the browser-automation skill to navigate to 'https://example.com' and take a screenshot.

Frequently Asked Questions about browser-automation

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

FAQPage Schema
How do I automate web form interaction and capture screenshots using Playwright?▼

Playwright automates web form interaction by navigating to URLs and filling fields in an isolated Chromium instance, which enables capturing screenshots of the resulting page state. This handles isolated browser tasks without modifying your primary environment.

Can I connect to a running headed Chrome instance for real-time debugging?▼

Yes, you can connect to a running headed Chrome instance via the Chrome DevTools Protocol (CDP) for real-time inspection, interaction, and debugging of browser extensions or active web pages.

What is the best way to handle authenticated sessions during browser automation?▼

Handling authenticated sessions during browser automation is best achieved by utilizing the storageState method, which preserves login contexts and bypasses authentication walls during automated testing.

Do I need specific port configurations for CDP and VNC when debugging browsers?▼

Yes, debugging browsers via CDP and VNC requires specific port configurations to establish the connection, enabling remote inspection and interaction with the headed Chrome instance.

How does the claude-in-chrome tool work with browser extensions?▼

The claude-in-chrome tool works with browser extensions by interfacing with Chrome to facilitate debugging, allowing direct interaction with extension scripts and the inspection of console logs.

Related Skills

Explore More Software Engineering Skills→
huichenhuichen

connect-chrome

Launch headed Chrome with the Side Panel extension via gstack on port 34567.

Community
Advanced
githubgithub
37.6k

webapp-testing

Automate browser-based testing of local web applications with Playwright.

Official
Intermediate
gandazgulgandazgul
14

playwright-cli

Automate browser interactions and generate Playwright test scripts.

Community
Advanced
VertaKhanVertaKhan

connect-chrome

Launch a visible Playwright-controlled Chromium window with the gstack Side Panel extension loaded.

Community
Intermediate