Browser Use automation

# Use Browser Use automation in your agent

## Objective
Use the existing browser-use skill only when it directly covers the requested task.

## Prerequisites
- target URL and bounded browser objective
- local Chrome/CDP or Browser Use Cloud execution mode
- explicit authorization for authenticated state and external mutations
- browser-use CLI
- local Chrome or Chromium with CDP remote debugging, or an optional Browser Use Cloud browser
- Browser Use API key and authenticated CLI session for cloud mode

## Permissions
- launch or connect to local or remote browser sessions
- read rendered page content
- access existing cookies, profiles, or SSO state only when explicitly authorized
- interact with page controls and create captures or files when authorized

## External effects
- network requests
- form submissions, messages, purchases, or account changes when explicitly requested
- remote Browser Use Cloud sessions can incur charges until stopped or timed out
- screenshots, recordings, downloads, and other browser artifacts can be written to disk
- authenticated cookies or profiles can be synchronized to a cloud browser when explicitly authorized

## Procedure
- Open the canonical source pinned to revision 950eb03617e67548d759c02beac1ad122c6b6458.
- Read the skill instructions before calling its tools.
- Ask for confirmation before any paid, destructive, or remote effect not already authorized.
- Run the procedure within the requested scope and retain useful evidence.

## When not to use
- server-side HTTP request only
- bypass access controls
- silent production mutation

## Expected result
- browser observations and inspected accessible or DOM state
- interaction results and optional screenshots, recordings, downloads, or other files

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Requires · browser-use CLI
• Requires · local Chrome or Chromium with CDP remote debugging, or an optional Browser Use Cloud browser
• Requires · Browser Use API key and authenticated CLI session for cloud mode

# Verify the Browser Use automation outcome

## Objective
Check that the browser-use skill was used within scope and that its effects match the authorized request.

## Checks
- Compare the source and revision with the manifest.
- Separate local, browser, and external evidence.
- Report any permission or effect that was not disclosed.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:9b004245c244db6fe11e4b8bd423afd09b9c6bfa62494d4b63f71bd42319a89c

# Verify Browser Use automation in your agent

## Result to check
Verify the use of browser-use for the current bounded task.

## Failure signals
- The source or revision does not match the manifest.
- A permission or external effect was not disclosed.
- The output does not match the expected artifacts.
- The skill activated for a declared non-trigger.

## Checks
- Compare the SHA-256 of SKILL.md with sha256:1ae1697ca45c8604110d1b80274a88f9736e45466f81ac15f38954e5ea7efb2b.
- Confirm the permissions actually used and the observed effects.
- Verify artifacts with the narrowest available test.
- Separate local, browser, and external evidence in the report.

## Expected result
- browser observations and inspected accessible or DOM state
- interaction results and optional screenshots, recordings, downloads, or other files

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Requires · browser-use CLI
• Requires · local Chrome or Chromium with CDP remote debugging, or an optional Browser Use Cloud browser
• Requires · Browser Use API key and authenticated CLI session for cloud mode

# Make the Browser Use automation check reusable

## Objective
Turn the successful checks into a bounded checklist for the next use of browser-use.

## Checks
- Keep only observable signals.
- Tie each permission to its expected effect.
- Add an explicit stop if the source or revision changes.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:65ba2272982b6313c4f7fbe7b46d8df2dc8bbd0b1b541dd101e54e6a66d7781d