/browser-use

name: browser-use
version: 1
description: >-
  Use this skill when the user asks the agent to open, browse, inspect, extract
  content from, click through, fill forms on, screenshot, or verify a web page
  with a browser. Also use it for MoviePilot scenarios that need browser
  interaction, such as checking a site page, confirming a JavaScript-rendered
  result, testing login state, capturing visible errors, or updating and
  validating tracker site cookies.
allowed-tools: browse_webpage recognize_captcha search_web query_sites update_site_cookie test_site update_site

Browser Use

Use MoviePilot's built-in browser and site tools to complete web tasks with observable, step-by-step browser actions.

This skill is adapted from the public `browser-use/browser-use` project:

• Project: `https://github.com/browser-use/browser-use`
• CLI workflow: `open -> state -> indexed action -> verify`
• Useful idea kept here: navigate first, observe the page state, perform one

small action, then verify the resulting state before continuing.

When To Use

• The user asks to open, browse, inspect, screenshot, or operate a web page.
• The page needs JavaScript rendering, button clicks, form filling, dropdowns,

or visual confirmation.

• Web search results are not enough and the target page must be opened.
• A MoviePilot tracker site needs login-state diagnosis, cookie update, or

connectivity verification.

Do not use the browser when a MoviePilot API, CLI skill, slash command, or dedicated tool can complete the task more directly and safely.

Tools

• `browse_webpage` - Persistent browser actions: `goto`, `snapshot`,

`get_content`, `screenshot`, `click`, `click_ref`, `fill`, `fill_ref`, `select`, `select_ref`, `evaluate`, `wait`, `list_tabs`, `open_tab`, `focus_tab`, `close_tab`, `close_session`.

• `recognize_captcha` - Recognize graphic captcha text from an image URL or

`data:image/...;base64,...` value extracted from the page. Pass Cookie and User-Agent when the image requires the current browser session.

• `search_web` - Find current pages or official references before opening a

target URL. It supports DDGS-backed `search_engine` (`auto`, `duckduckgo`, `google`, `brave`, etc.) and `site_url` for limiting results to a specified domain or URL path. It uses the configured system proxy by default.

• `query_sites` - Get MoviePilot site IDs before site-specific operations.

Non-admin callers receive a safe view without Cookie, RSS, Token, or API Key fields.

• `update_site_cookie` - Update a configured site's Cookie and User-Agent using

username, password, and optional two-step code.

• `test_site` - Verify configured site connectivity and login status.
• `update_site` - Update existing site settings when the user explicitly asks.

Core Workflow

1. Prefer Structured Tools First

If the request maps to MoviePilot domain data, use the dedicated MoviePilot tools first. Use the browser only for pages or states that those tools cannot observe.

Examples:

• Query downloads, subscriptions, media, sites, or library state with the

existing MoviePilot skills/tools.

• Use `query_sites`, `update_site_cookie`, and `test_site` for configured

tracker sites before manually browsing their pages.

2. Find Or Open The Target

If the user gave a URL, call:

browse_webpage action="goto" url="https://example.com"

If the user only described the page, search first:

search_web query="official site or page name"

To search within a specific site:

search_web query="release notes" site_url="https://docs.example.com/"

Then open the most relevant result with `browse_webpage action="goto"`.

3. Observe Before Acting

After every navigation or meaningful page change, inspect the returned title, URL, text, and `interactive_elements`. Each interactive element includes a stable `ref` for follow-up operations. If the page is ambiguous or dynamic, use:

browse_webpage action="snapshot"

Use a screenshot only when visual layout, captcha, icons, errors, or rendered state matter:

browse_webpage action="screenshot"

4. Act In Small Steps

Perform one browser action at a time and verify after each action.

Common actions:

browse_webpage action="click_ref" ref="e1"
browse_webpage action="fill_ref" ref="e2" value="..."
browse_webpage action="select_ref" ref="e3" value="..."
browse_webpage action="wait" selector="text=Success"

Prefer element refs from the latest `snapshot` or action result. If a ref is not available, use stable selectors in this order:

1. Visible text selector for buttons and links, such as `text=Save`. 2. Semantic or form attributes, such as `input[name='username']`. 3. Stable IDs, such as `#login-button`. 4. CSS classes only when no better selector exists.

5. Extract With JavaScript Only When Needed

Use `evaluate` for structured extraction, shadow DOM, or page data that is hard to read from text:

browse_webpage action="evaluate" script="() => Array.from(document.querySelectorAll('a')).map(a => ({text: a.innerText, href: a.href})).slice(0, 20)"

Keep scripts read-only unless the user asked for a page operation and the action cannot be completed with `click`, `fill`, or `select`.

6. Verify And Report

Before finalizing, verify the outcome with one of:

• `get_content` for text or data changes.
• `screenshot` for visual state.
• `test_site` for MoviePilot configured tracker connectivity.

Report the result with the final URL, observed status, and any remaining uncertainty. If the page failed, include the visible error text and the action that failed.

MoviePilot Site Workflows

Diagnose A Configured Site

1. Use `query_sites` to find the site ID. 2. Use `test_site` with the site ID. 3. If the site fails and the user provided credentials, use `update_site_cookie`. 4. Run `test_site` again to confirm. 5. Use `browse_webpage` only if the failure message is unclear o