Agent Skills › outworked/outworked › Web Browser

Web Browser

GitHub

提供网页浏览、截图及交互能力。支持导航、点击、表单填写（含富文本输入）、JS执行及手动登录辅助，适用于在线调研、网站检查、表单提交和页面状态验证。

electron/skills/browser/SKILL.md outworked/outworked

Trigger Scenarios

需要浏览或抓取网页内容需要截取网页屏幕快照需要在网站上填写表单或进行交互操作

Install

npx skills add outworked/outworked --skill Web Browser -g -y

More Options

Non-standard path

npx skills add https://github.com/outworked/outworked/tree/main/electron/skills/browser -g -y

Use without installing

npx skills use outworked/outworked@Web Browser

指定 Agent (Claude Code)

npx skills add outworked/outworked --skill Web Browser -a claude-code -g -y

安装 repo 全部 skill

npx skills add outworked/outworked --all -g -y

预览 repo 内 skill

npx skills add outworked/outworked --list

SKILL.md

Frontmatter

{
    "name": "Web Browser",
    "emoji": "🌐",
    "tools": [
        "browse:navigate",
        "browse:snapshot",
        "browse:screenshot",
        "browse:click",
        "browse:fill",
        "browse:type",
        "browse:evaluate",
        "browse:show",
        "browse:login"
    ],
    "runtime": "browser",
    "description": "Browse the web, take screenshots, interact with pages, fill forms. Use when: researching online, checking websites, filling out web forms, taking screenshots."
}

Web Browser Skill

You can browse the web using the browse:* tools. A managed browser window handles navigation and interaction.

Available Tools

browse:navigate — Navigate to a URL. Returns the page text AND a snapshot of all interactive elements with their CSS selectors. Start here. Params: url (string).
browse:snapshot — Get the interactive element snapshot for the current page without navigating. Use after a click to see what changed. No required params.
browse:screenshot — Take a screenshot of the current page. Returns an actual image you can see. Use to visually verify state. No required params.
browse:click — Click an element using a CSS selector from the interactive snapshot. Returns the updated snapshot after clicking. Params: selector (string).
browse:fill — Fill a form field by setting its value. Works for standard <input> and <textarea> elements. Params: selector (string), value (string).
browse:type — Type text using simulated keyboard input. Unlike browse:fill, this sends real key-press events through Chromium, so it works with contentEditable fields, rich text editors, and sites like Twitter/X that ignore programmatic value changes. Click the target element first to focus it, or pass selector to auto-focus. Params: text (string, required), selector (string, optional), clearFirst (boolean, optional).
browse:evaluate — Execute JavaScript in the page context. Use as a last resort — prefer the other tools. Params: script (string).
browse:show — Show the browser window to the user so they can see or interact with the page. Displays a "Done" banner. Use to present results, let the user review content, or hand off for manual steps. Params: url (string, optional), message (string, optional).
browse:login — Show the browser window so the user can log in manually. Params: url (string, optional), message (string, optional).

Workflow

Navigate to the target URL with browse:navigate — the response includes all interactive elements with selectors
Click or fill using the selectors from the snapshot — no need to probe the DOM
After a click, the response includes the updated snapshot so you can see what changed
Use browse:screenshot if you need to visually verify the page state
Use browse:snapshot to refresh the interactive element list without navigating

Best Practices

Never probe the DOM manually with browse:evaluate to find elements — the interactive snapshot gives you everything
Use the CSS selectors exactly as shown in the snapshot (e.g. [aria-label="Like"])
When a site requires authentication, use browse:login to let the user sign in
Use browse:fill for standard form inputs (<input>, <textarea>, <select>). Use browse:type for rich text editors, contentEditable fields, or any site where browse:fill doesn't work (Twitter/X, Notion, Google Docs, etc.)
A typical interaction should be 2-3 tool calls: navigate → click → done