Browser Automation

VerifiedSafe

Automate web browser interactions using natural language CLI commands. Supports local and remote environments.

Sby Skills Guide Bot
DevelopmentBeginner
7/23/2026
Claude Code
#browser-automation#stagehand#cli#web-scraping#natural-language

Recommended for

Automated summary

Automates web browser interactions via natural-language CLI commands, with automatic fallback between local and remote browser environments.

Strengths

  • Natural language interface reduces need for scripting
  • Automatic environment selection between local and remote (Browserbase) without user prompting
  • Supports navigation, actions, data extraction, screenshots, and element observation

Limitations

  • Requires initial setup (npm install) and optionally Chrome or Browserbase API keys
  • May struggle with complex interactions or dynamic content
  • Performance depends on environment (remote is slower)
When to use it

When you need to quickly interact with web pages, extract data, or test web applications without writing browser automation code.

When not to use it

When you need high-performance scraping at scale or complex multi-step workflows with extensive conditional logic.

Security analysis

Safe
Quality score88/100

The skill only runs standard npm install/link and browser automation commands. No destructive actions, no exfiltration beyond intended usage, no encoded payloads. Using Browserbase API keys from .env is part of normal operation.

No concerns found

How this analysis is made

Examples

Screenshot a page
Navigate to https://example.com and take a screenshot
Fill and submit a form
Go to https://example.com/login, fill in the username field with 'user' and password field with 'pass', then click the submit button
Extract search results
Search Google for 'climate change' and extract the titles and URLs of the first 10 results

name: browser description: Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications. allowed-tools: Bash

Browser Automation

Automate browser interactions using Stagehand CLI with Claude.

First: Environment Selection (Local vs Remote)

The skill automatically selects between local and remote browser environments:

  • If Browserbase API keys exist (BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID in .env file): Uses remote Browserbase environment
  • If no Browserbase API keys: Falls back to local Chrome browser
  • No user prompting: The selection happens automatically based on available configuration

Setup (First Time Only)

Check setup.json in this directory. If setupComplete: false:

npm install    # Install dependencies
npm link       # Create global 'browser' command

Commands

All commands work identically in both modes:

browser navigate <url>                    # Go to URL
browser act "<action>"                    # Natural language action
browser extract "<instruction>" ['{}']    # Extract data (optional schema)
browser observe "<query>"                 # Discover elements
browser screenshot                        # Take screenshot
browser close                             # Close browser

Quick Example

browser navigate https://example.com
browser act "click the Sign In button"
browser extract "get the page title"
browser close

Mode Comparison

| Feature | Local | Browserbase | |---------|-------|-------------| | Speed | Faster | Slightly slower | | Setup | Chrome required | API key required | | Stealth mode | No | Yes | | Proxy/CAPTCHA | No | Yes | | Best for | Development | Production/scraping |

Best Practices

  1. Always navigate first before interacting
  2. View screenshots after each command to verify
  3. Be specific in action descriptions
  4. Close browser when done

Troubleshooting

  • Chrome not found: Install Chrome or use Browserbase mode
  • Action fails: Use browser observe to discover available elements
  • Browserbase fails: Verify API key and project ID are set

For detailed examples, see EXAMPLES.md. For API reference, see REFERENCE.md.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/browser-automation-mrwakb72/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/browser-automation-mrwakb72' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/browser-automation-mrwakb72/download' --output '.skill-downloads/browser-automation-mrwakb72/SKILL.md.part' && mv '.skill-downloads/browser-automation-mrwakb72/SKILL.md.part' '.skill-downloads/browser-automation-mrwakb72/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/browser-automation-mrwakb72/SKILL.md' && test -s '.skill-downloads/browser-automation-mrwakb72/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/browser' && cp -R '.skill-downloads/browser-automation-mrwakb72' '.claude/skills/browser'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/browser-automation-mrwakb72'

openskills read 'browser-automation-mrwakb72'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/browser-automation-mrwakb72/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills