Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vellum-browser-use
Browse the web using `assistant browser` CLI commands
Passed 11 of 16 test cases with the skill, and 4 of 16 without it.
and 10 more in the full report
11 fixed4 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
The browser status check indicates the Chrome extension is unavailable and the user declined installing it. Between CDP inspect and local Playwright mode, which backend option should be selected when navigating to https://dashboard.example.com?
| Checked | Without skill | With skill |
|---|---|---|
| Selects cdp-inspect mode over local mode as the preferred fallback | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to browse the web. All browser operations are executed through the assistant browser CLI, invoked via bash or host_bash. Each operation is a subcommand:
| Command | Description |
|---|---|
assistant browser navigate | Navigate to a URL |
assistant browser snapshot | List interactive elements on the current page |
assistant browser screenshot | Take a visual screenshot |
assistant browser click | Click an element |
assistant browser type | Type text into an input |
assistant browser press-key | Press a keyboard key |
assistant browser scroll | Scroll the page or a specific element |
assistant browser select-option | Select an option from a native <select> element |
assistant browser hover | Hover over an element to reveal menus/tooltips |
assistant browser wait-for | Wait for a condition |
assistant browser extract | Extract page text content |
assistant browser wait-for-download | Wait for a file download to complete |
assistant browser fill-credential | Fill a stored credential into a form field |
assistant browser attach | Attach the Chrome debugger to the active tab |
assistant browser detach | Detach the Chrome debugger from the active tab |
assistant browser close | Close the browser page |
assistant browser status | Diagnose browser backend readiness and setup steps |
Before using any browser commands, run assistant browser --json status first to check which browser backends are available. The status command returns JSON with readiness information for each backend mode:
assistant browser --json status
The response includes:
recommendedMode — the best available backend (use this)modes[] — per-mode status with available, summary, and userActions (remediation steps)Use --browser-mode <mode> on the assistant browser parent command to pin the browser backend:
| Value | Backend | Description |
test cases passed, vs 4 / 16 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.