browser-use

browser-use: What this skill does

browser-use is a reusable agent skill listed on skills.sh under browser-use/browser-use. skills.sh rank #149, installs 73.2K, GitHub stars 95.3K, first seen Jan 22, 2026.

Fast, persistent browser automation with session continuity across sequential agent commands. Supports three browser modes: headless Chromium, real Chrome with profile support, and cloud-hosted remote browsers with proxy configuration Includes 20+ command categories covering navigation, page inspection, interactions, data extraction, cookie management, JavaScript execution, and wait conditions Offers cloud session management, local server tunneling via Cloudflare, and parallel subagent execution through remote sessions with task monitoring Built-in Python integration for setting variables, accessing the browser object, and running scripts within the automation context

When to use it

• Use this skill when the task matches the package name, repository context, or skills.sh topic: productivity.
• Prefer it when a repeatable workflow is better than a one-off prompt: setup, review, design, deployment, automation, research, media generation, or operational checks.
• For production work, read the linked repository and install command before allowing the agent to run scripts or modify files.

How an agent should use it

1. Confirm the user intent and whether this skill is the right fit.
2. Install or inspect the skill with the official command from skills.sh.
3. Read the local SKILL.md and only load extra files referenced by that skill.
4. Follow the skill's workflow, then verify the result with tests, screenshots, audits, or source-backed checks as appropriate.
5. Record any constraints, missing credentials, tool permissions, or security warnings before handoff.

Quality and safety checks

• Check repository ownership and source reputation: browser-use/browser-use.
• Review security audit signals before installing; skills.sh reports: Gen Agent Trust Hub Fail Socket Pass Snyk Warn.
• Never grant broad shell, browser, cloud, or deployment permissions without user approval.
• Treat generated output as draft until validated by the skill's own acceptance criteria.
• If the skill touches cloud resources, costs, credentials, customer data, or production deploys, require a human review step.

Sources and install

• skills.sh page: https://www.skills.sh/browser-use/browser-use/browser-use
• Repository: https://github.com/browser-use/browser-use
• Install command: npx skills add https://github.com/browser-use/browser-use --skill browser-use

FAQ

Is browser-use an agent, a prompt, or a skill?
It is a skill: a reusable package of task-specific instructions and supporting files that an agent can load when the user's request matches the workflow.

Should I install it automatically?
Only after checking the repository, install command, audit status, and whether the user wants this capability in the current agent environment.

What makes it useful for AIDreamHub users?
It helps users discover practical agent capabilities from the open skills ecosystem and compare them by task, source, install count, and operational risk.