Agent skill

Browser

by wecode-ai in wecode-ai/Wegent

Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed.

Apache-2.0Auto-check passedAgent Workflows

Install Browser

skills CLI
$ npx skills add wecode-ai/Wegent --skill browser -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wecode-ai/Wegent browser --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wecode-ai/Wegent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/backend/init_data/skills/browser .claude/skills/browser && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browser
GitHub stars
868
Token cost
~1k tokens
SKILL.md length
304 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed.

  • Works in 7 steps: Start with the intended action directly… → Use snapshot only when refs are required… → Prefer evaluate for extraction. Return… → …
  • Agent Workflows work in your project
  • SKILL.md covers Goal, Operating Rules, Reliability and Recovery and Screenshot Policy, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Browser is an agent skill from wecode-ai/Wegent. Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Plan, build, and deliver with an open-source, self-hostable AI workspace for coding, collaboration, and automation. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/browser”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Start with the intended action directly (navigate/open/act/evaluate). Do not run status as a pre-check.
  2. Use snapshot only when refs are required for interaction (click/type/select/drag/scrollIntoView).
  3. Prefer evaluate for extraction. Return structured data in one comprehensive call when possible.
  4. Use condition waits by default (loadState/url → selector/text/textGone → fn). Avoid timeMs unless explicitly needed.
  5. Before clicking potentially off-screen elements, run act.scrollIntoView on the ref first.
  6. Keep context stable: once targetId is known, pass it in follow-up calls when supported.
  7. Avoid blind loops: every extra call must have a clear purpose.

What it can do on your machine

Read from SKILL.md and the folder at commit 428f207. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser loads about 1k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 304 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~39
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wecode-ai/Wegent at commit 428f207, republished under its Apache-2.0 licence (© wecode-ai). 304 words, ~1,033 tokens.

Download SKILL.mdSave it as .claude/skills/browser/SKILL.md (or your agent's skills folder).
name
browser
description
Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed.

Browser Control Skill

Goal

Finish the user’s real task reliably.
Prioritize successful completion and correct results over aggressive call minimization.

Operating Rules

  1. Start with the intended action directly (navigate/open/act/evaluate). Do not run status as a pre-check.
  2. Use snapshot only when refs are required for interaction (click/type/select/drag/scrollIntoView).
  3. Prefer evaluate for extraction. Return structured data in one comprehensive call when possible.
  4. Use condition waits by default (loadState/url → selector/text/textGone → fn). Avoid timeMs unless explicitly needed.
  5. Before clicking potentially off-screen elements, run act.scrollIntoView on the ref first.
  6. Keep context stable: once targetId is known, pass it in follow-up calls when supported.
  7. Avoid blind loops: every extra call must have a clear purpose.

Reliability and Recovery

  1. If Ref not found, do not reuse stale refs. Take one fresh snapshot, retry once, then stop if still failing.
  2. For repeated failures with the same cause, stop and explain the blocker clearly instead of retrying endlessly.
  3. Connection recovery is built into the tool. Allow auto-recovery once; if still disconnected, instruct user to install/connect extension.

Screenshot Policy

  1. Default: no screenshot.
  2. Use screenshots only when user asks, or when visual proof is required.
  3. Prefer element screenshots (ref or element) over full-page screenshots.
  4. Use full-page screenshots only for page-level evidence.
  1. Direct action first (navigate/open or immediate act/evaluate).
  2. If interaction needs refs, run snapshot (interactive: true preferred).
  3. Wait for readiness using act.wait with explicit conditions.
  4. Interact (scrollIntoView → click/type/select/drag as needed).
  5. Extract/verify with evaluate (preferred) or snapshot.
  6. Provide screenshot evidence only when necessary.

Connection Handling

Connection recovery is built into the tool. On connection failure, let the tool auto-attach/launch/retry once. If still disconnected, stop and instruct the user to install/connect the extension.

Minimal CLI Usage

Use <BROWSER_TOOL_CMD> for commands:

  • macOS/Linux: ~/.wegent-executor/bin/browser-tool
  • Windows: ~/.wegent-executor/bin/browser-tool.cmd
bash
<BROWSER_TOOL_CMD> '<json>'

Quick Examples

bash
# Navigate directly
<BROWSER_TOOL_CMD> '{"action":"navigate","url":"https://example.com"}'

# Snapshot only when refs are needed
<BROWSER_TOOL_CMD> '{"action":"snapshot","interactive":true}'

# Act on ref
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"click","ref":"e1"}}'

# Ensure element is visible before click (recommended on long pages)
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"scrollIntoView","ref":"e1"}}'

# Condition wait (preferred over fixed sleep)
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"wait","loadState":"domcontentloaded","timeoutMs":15000}}'

# URL-based wait
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"wait","url":"checkout","timeoutMs":10000}}'

# Run JS in page context via act.evaluate (function or expression)
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"evaluate","fn":"() => ({title: document.title, href: location.href})"}}'

# Run JS against a target element ref via act.evaluate
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"evaluate","ref":"e1","fn":"(el) => ({text: el.textContent?.trim() || \"\"})"}}'

# Close current tab (or pass targetId)
<BROWSER_TOOL_CMD> '{"action":"act","request":{"kind":"close"}}'

# Element screenshot (prefer over full-page when only target proof is needed)
<BROWSER_TOOL_CMD> '{"action":"screenshot","ref":"e1","type":"jpeg"}'

# Comprehensive extraction in one evaluate
<BROWSER_TOOL_CMD> '{"action":"evaluate","expression":"(() => ({title:document.title,url:location.href}))()"}'

© wecode-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in backend/init_data/skills/browser of wecode-ai/Wegent.

Open the folder on GitHubat commit 428f207

Compare with similar skills

Browser next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser this skillwecode-ai/Wegent868—~1kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from wecode-ai/Wegent

All 8 skills in this repo
  • Wework Plugin Creator

    wecode-ai/Wegent

    Create or extend Wework plugins, including native Connector login and account authentication for reuse on cloud devices.

    868 GitHub stars~990 tokensUpdated 3 days ago
    Auto-check passed
  • Develop Wework Plugin

    wecode-ai/Wegent

    Create, extend, and debug Wework Core DSH plugins and their optional nested Codex plugins.

    868 GitHub stars~3.5k tokensUpdated 3 days ago
    Auto-check passed
  • Interactive

    wecode-ai/Wegent

    Ask the user questions or present choices via an interactive form.

    868 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Subscription Manager

    wecode-ai/Wegent

    Create and manage scheduled subscription tasks. An agent skill from wecode-ai/Wegent.

    868 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Create Smart App

    wecode-ai/Wegent

    Create or update a Wework Smart app based on DeepSeek Harness, including environment preparation, DSH plugin discovery, composition, built-in-browser verification, packaging, and local installation…

    868 GitHub stars~927 tokensUpdated 3 days ago
    Auto-check: notes
  • Wework Notifications

    wecode-ai/Wegent

    Send Wework in-app notifications when a user requests an alert, greeting, or automation notification.

    868 GitHub stars~604 tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Browser

What does Browser do?

Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed. Browser is an agent skill from wecode-ai/Wegent. Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed.

When should I use Browser?

Browser fits situations like: agent Workflows work in your project.

How do I install Browser in Claude Code?

Run `npx skills add wecode-ai/Wegent --skill browser -a claude-code`. Or copy the skill folder (backend/init_data/skills/browser in wecode-ai/Wegent) into .claude/skills/browser in your project. Claude Code loads it when a task matches its description.

How do I install Browser in Codex?

Run `npx skills add wecode-ai/Wegent --skill browser -a codex`. Or copy the skill folder (backend/init_data/skills/browser in wecode-ai/Wegent) into .agents/skills/browser in your project. Codex loads it when a task matches its description.

Can I use Browser in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wecode-ai/Wegent --skill browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser, .gemini/skills/browser, .github/skills/browser and .opencode/skills/browser in your project.

What does Browser need to run?

SKILL.md names no scripts, command-line tools or credentials: Browser is instructions for the agent only.

Does Browser access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Browser safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser use?

Browser is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Browser use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser?

Skills that share tags, products or a category with Browser: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser?

wecode-ai (a GitHub organization) maintains it in wecode-ai/Wegent, which has 868 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 5, 2026.

Source: wecode-ai/Wegent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.