# Browser

> Automate browser interactions using the Browserbase browse CLI. Use when a task requires navigating websites, reading page state, clicking elements, filling forms, or validating browser results with the browse command. Use when this capability is needed.

- Skill: `tomevault-io/browser-7` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/browser-7`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/browser-7/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/browser-7

---


# Browser Automation

Automate browser interactions using the browse CLI with Claude.

## Setup

Do not install packages during evals. The eval harness provides `browse` on `PATH` and pins it to the active benchmark session.

## Environment Selection

The eval harness pins `browse` to one isolated session and preselects the intended environment.

- Local mode uses local Chrome.
- Remote mode uses Browserbase when credentials are configured.
- Do not switch environments unless the task or harness explicitly requires it.

## Page State

Prefer `browse snapshot` over screenshots. It returns a structured accessibility tree with element refs that can be used for interactions.

Only use screenshots when visual layout or image content is necessary.

Useful state checks:

```bash
browse status
browse get url
browse get title
browse snapshot
```

## Interaction Workflow

Typical flow:

1. Navigate to the starting URL with `browse open <url>`.
2. Run `browse snapshot` to inspect structure and element refs.
3. Interact with refs from the snapshot, selectors, or keyboard actions.
4. Run `browse snapshot` or another state check to verify the result.
5. Repeat until the benchmark instruction is complete.

Common interaction patterns:

```bash
browse click <ref>
browse type <text>
browse press <key>
browse fill <selector> <value>
browse wait timeout <ms>
```

## Best Practices

- Always navigate before interacting.
- Use refs from `browse snapshot` when possible.
- Verify each important action before moving on.
- Keep actions focused on the benchmark instruction.
- Do not edit repository files.
- Do not use browser/network tools outside the provided `browse` command.

## Completion

When finished, report the benchmark result in the exact `EVAL_RESULT` format requested by the harness prompt.

---
> Source: [browserbase/stagehand](https://github.com/browserbase/stagehand) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-24 -->