What it does
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
Skills ZICQ category:Agent Workflows remote-browser
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Remote Browser; Check the CLI; Start an isolated browser; Inspect and interact; Stop the browser.
File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.
Remote BrowserCheck the CLIStart an isolated browserInspect and interactStop the browser
· allowed-tools:Bash(browser-use:*)
Source category:skills.sh agent-skill
nameremote-browserdescriptionallowed-toolsInvocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "remote-browser" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-5122ad027e7183f6-Remote-Browser.html Save it as .cursor/skills/remote-browser/SKILL.md or .claude/skills/remote-browser/SKILL.md and keep the frontmatter name and description exactly as-is.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/browser-use/browser-use' --list
npx skills add 'https://github.com/browser-use/browser-use' --skill 'remote-browser'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Use this skill when an agent runs on a machine without a usable local Chrome and needs an isolated browser. The current Browser Use CLI runs Python from stdin. Do not use the removed open, state, click, input, tab, cloud connect, or --connect commands.
browser-use --doctor
browser-use skill show
If setup fails, follow the current Browser Use skill.
Authenticate once:
browser-use auth login
Pick a short unique name. r7k2 below is only an example.
browser-use <<'PY'
start_remote_daemon("r7k2")
PY
Use the same name for every command in this browser:
BU_NAME=r7k2 browser-use <<'PY'
new_tab("https://example.com")
wait_for_load()
print(page_info())
PY
Each remote daemon is a separate Browser Use Cloud browser. Use a different name for each parallel task. Remote browsers can bill until they stop or time out.
Helpers are pre-imported. Keep multi-step work in one heredoc when practical.
BU_NAME=r7k2 browser-use <<'PY'
print(page_info())
print(js("document.title"))
fill_input('input[name="q"]', "browser automation")
press_key("Enter")
wait_for_load()
print(page_info())
PY
Useful helpers:
new_tab(url), goto_url(url), wait_for_load()page_info(), js(code), cdp(method, ...)click_at_xy(x, y), type_text(text), fill_input(selector, text), press_key(key), scroll(x, y)list_tabs(), switch_tab(target), close_tab(target)capture_screenshot(), wait_for_element(selector)Prefer the accessibility tree for element discovery:
nodes = cdp("Accessibility.getFullAXTree")["nodes"]
Use a targeted js(...) query when the accessibility tree lacks the element. Verify each action with page_info(), a focused DOM check, or a screenshot.
When the work is done, stop the exact named browser:
browser-use <<'PY'
stop_remote_daemon("r7k2")
PY
Do not leave an unused remote browser running.
Agent Workflows
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…
Agent Workflows
Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…
Agent Workflows
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …
Agent Workflows
Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…