browser-use

Automate multi-step web workflows with persistent browser sessions via the browser-use CLI.

5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill browser-use-marchatton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-use
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/00-utilities/browser-use
Command: npx skills add https://github.com/marchatton/agent-skills --skill browser-use-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides fast, persistent browser automation, allowing for multi-step web workflows without the need to write complex Playwright scripts. It also supports using your existing logged-in Chrome session.

Core Features & Use Cases

  • Persistent Sessions: Browser sessions persist across multiple commands, ideal for complex workflows.
  • Element Indexing: Interact with web elements using a simple index system after a state command.
  • Multiple Browser Modes: Supports headless Chromium, headed Chromium, real Chrome (for logged-in sessions), and remote browsers.
  • Use Case: Automate the process of logging into a web application, filling out a multi-step form, and then extracting data from the resulting page, all within a single, persistent session.

Quick Start

Use the browser-use skill to open the URL https://example.com and then list the elements on the page.

Frequently Asked Questions about browser-use

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

FAQPage Schema
How do I automate multi-step web workflows without writing complex Playwright scripts?

Persistent browser automation allows you to automate multi-step web workflows by executing sequential commands to open URLs, inspect elements, and perform actions without writing complex Playwright scripts.

Can I use my existing logged-in Chrome session for web scraping automation?

Yes, web scraping automation supports using your existing logged-in Chrome session, allowing you to interact with authenticated pages and perform tasks without needing to handle login credentials.

How do I interact with web elements using the browser-use CLI?

You interact with web elements using the browser-use CLI by running a state command to inspect the page, which generates an index system that you use to perform actions like clicking and inputting text on specific elements.

Does persistent browser automation support headless and remote browser integration?

Persistent browser automation supports headless Chromium, headed Chromium, real Chrome sessions, and remote browser integration, ensuring deterministic web task execution across various environments.

What is the best way to maintain browser state across multiple CLI commands?

The best way to maintain browser state across multiple CLI commands is using persistent sessions, which keep your browser context active between commands for complex workflows like filling out multi-step forms.

When should I not use this approach for web automation?

You should avoid this approach for web automation when you require highly parallelized, isolated test runs rather than sequential, stateful workflows, as it focuses on persistent sessions across multiple commands.