browser-harness

Replace deprecated browser-use 0.13 subcommands with heredoc-based workflows.

40|8|Updated May 14, 2026
One-click install
npx skills add https://github.com/zpoint/vibe-seller --skill browser-harness-zpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-harness
Source: https://github.com/zpoint/vibe-seller/tree/main/app/skills_v2/browser-harness
Command: npx skills add https://github.com/zpoint/vibe-seller --skill browser-harness-zpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

browser-use 0.13 removed all legacy subcommands (open, click, state), breaking existing browser automation workflows that relied on those interfaces. This skill is the mandatory bridge that restores browser control functionality by providing the updated heredoc-based workflow and helper API, preventing command failures for all browser-related tasks.

Core Features & Use Cases

  • Updated browser-use 0.13 Compatibility: Replaces deprecated subcommands with the new heredoc-based Python helper workflow, eliminating compatibility issues with the latest browser-use version.
  • Multi-Store Session Isolation: Manages auto-injected store-specific session IDs and CDP proxy endpoints to ensure each e-commerce store's agent only accesses its own browser instance, preventing cross-store data leakage.
  • Task Type Guardrails: Enforces clear rules for store-specific seller center tasks vs. no-store public web tasks, reducing the risk of accidental account access or policy violations.
  • Use Case: A cross-border seller running separate agents for Amazon US, Noon EG, and Shopify stores can use this skill to ensure each agent safely controls its assigned store's browser for tasks like listing updates, ad optimization, and inventory checks without interfering with other stores' operations.

Quick Start

Invoke the browser-harness skill to automate browser tasks for your assigned e-commerce store, such as updating product listings or adjusting ad campaign settings.

Frequently Asked Questions about browser-harness

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

FAQPage Schema
Why does my browser-use 0.13 browser automation workflow fail with deprecated subcommands?

Browser-use 0.13 browser automation fails because it removed legacy subcommands like open, click, and state. This skill restores browser control functionality by providing the updated heredoc-based Python helper workflow, fixing compatibility issues.

How do I isolate browser sessions for multi-store e-commerce automation?

To isolate browser sessions for multi-store e-commerce automation, this skill manages auto-injected store-specific session IDs and CDP proxy endpoints. This ensures each store's agent only accesses its own browser instance, preventing cross-store data leakage.

Can I use this skill to automate seller center operations across different e-commerce platforms?

Yes, you can automate seller center operations across different e-commerce platforms. It supports isolated multi-store browser control for tasks including listing updates, ad optimization, and inventory checks for various cross-border stores.

What are the task type guardrails for e-commerce browser control?

The task type guardrails for e-commerce browser control enforce clear rules for store-specific seller center tasks versus no-store public web tasks. These restrictions reduce the risk of accidental account access or policy violations during browser automation.

How do I replace deprecated browser-use subcommands with the new heredoc interface?

To replace deprecated browser-use subcommands with the new heredoc interface, invoke this skill. It provides the mandatory bridge that updates your browser automation workflow to the latest browser-use 0.13 compatibility standard.