browser-driver

Automate user interactions in existing browser sessions via CDP and Playwright.

12|3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Fei2-Labs/skill-genie --skill browser-driver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-driver
Source: https://github.com/Fei2-Labs/skill-genie/tree/main/skills/browser-driver
Command: npx skills add https://github.com/Fei2-Labs/skill-genie --skill browser-driver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to automate tasks in the user's existing browser session, eliminating the need for re-authentication and session setup.

Core Features & Use Cases

  • Session Reuse: Leverages the user's existing browser session to perform tasks.
  • CDP and Playwright Integration: Utilizes Chrome DevTools Protocol and Playwright for browser automation.
  • Use Case: Use this Skill to automate tasks like navigating through a web application, filling out forms, or interacting with web elements without needing to log in again.

Quick Start

Automate a task in your browser using the browser-driver skill with the command 'browser-driver automate "Navigate to my dashboard and click the submit button."'.

Frequently Asked Questions about browser-driver

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

FAQPage Schema
How do I automate web tasks in an existing browser session without re-authenticating?

Automating web tasks in an existing browser session is possible by leveraging Chrome DevTools Protocol with Playwright. This approach reuses your active login state, eliminating the need to re-authenticate or set up a new session for web application automation.

Can I use Playwright to interact with web elements in an already running browser?

Yes, you can use Playwright to interact with web elements in a running browser. By connecting through the Chrome DevTools Protocol, the browser-driver Skill targets and automates user interactions like form submissions and dashboard navigation within your active session.

What is the best way to perform web automation without breaking my current login state?

The best way to perform web automation without breaking your login state is session reuse via CDP. This technique connects automation scripts directly to your running browser, preserving active cookies and authentication tokens while executing tasks like form submissions.

Do I need a specific browser configuration to use CDP for session reuse?

Yes, you need a running browser with an active session and a compatible browser automation framework. The Skill utilizes Chrome DevTools Protocol and Playwright, requiring your browser to be launched in a mode that accepts CDP connections for session reuse.

What are the limitations of using an existing browser session for web automation?

The primary limitation of using an existing browser session for web automation is the strict dependency on a continuously running browser. If the active session expires or the browser closes unexpectedly, the Playwright automation via CDP will fail to execute tasks.

Why does my Playwright automation require re-authentication instead of using my active session?

Playwright automation requires re-authentication when it launches a new browser context instead of connecting to your active session. To reuse your existing session and skip login, you must connect Playwright to your running browser using the Chrome DevTools Protocol.