browser-boss

Coordinate browser automation across agent-browser, browser-use, Playwright CLI, and DevTools workflows.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/BFLabsAI/algoritmo-milionario --skill browser-boss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-boss
Source: https://github.com/BFLabsAI/algoritmo-milionario/tree/main/skills/browser-boss
Command: npx skills add https://github.com/BFLabsAI/algoritmo-milionario --skill browser-boss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating browser automation tasks across diverse toolchains is error-prone and time-consuming. This skill provides a single, cohesive framework to manage navigation, form interactions, content scraping, testing, and QA across multiple tooling options.

Core Features & Use Cases

  • Multi-tool orchestration: Seamlessly switch between agent-browser, browser-use, Playwright CLI, and DevTools MCP workflows.
  • UI automation and scraping: Automate navigation, element interaction, DOM inspection, and data extraction across dynamic sites.
  • Test generation and inspection: Generate tests from scenarios and inspect DevTools output, with references and templates.

Quick Start

Start by selecting the appropriate tool and running a guided workflow to automate navigation, form filling, and data extraction across your stack.

Frequently Asked Questions about browser-boss

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

FAQPage Schema
How do I coordinate browser automation across multiple tools like Playwright and DevTools?

Browser automation across multiple tools is coordinated through a unified framework that manages navigation, form filling, and data scraping across Playwright CLI, DevTools, and agent-browser workflows. It enforces cross-tool coordination and session state management for cohesive execution.

What is the best way to automate web navigation and data scraping on dynamic sites?

Automating web navigation and data scraping on dynamic sites requires a multi-tool orchestration framework that handles DOM inspection and element interaction. This approach seamlessly switches between agent-browser and browser-use workflows to extract content from complex pages.

Can I use this to generate UI tests from scenarios and inspect DevTools output?

Yes, you can generate UI tests from scenarios and inspect DevTools output. The framework provides modular references and templates for test generation, applying safe usage patterns across Playwright CLI and DevTools MCP workflows.

Does browser automation across diverse toolchains require managing session state separately?

Managing session state across diverse toolchains does not require separate handling. The framework enforces built-in session and state management, ensuring safe usage patterns and cross-tool coordination during web navigation and form interactions.

When should I not use a unified framework for browser automation tasks?

A unified browser automation framework is not ideal for single-tool, isolated scripts that lack cross-tool coordination needs. If your workflow involves only basic static page scraping without dynamic interactions or session management, simpler standalone tools may suffice.