Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remote-browser
Controls a local browser from a sandboxed remote machine.
Passed 16 of 21 test cases with the skill, and 7 of 21 without it.
and 10 more in the full report
10 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
In an active remote browser tab, I need to fetch current page status metadata and evaluate a custom JavaScript expression `document.title` via pre-imported stdin helpers. What calls should be made?
| Checked | Without skill | With skill |
|---|---|---|
| Retrieves page metadata using page_info. | Missed | Passed |
| Evaluates custom JavaScript expressions using js. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
test cases passed, vs 7 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.