Browser Skill logo

Browser Skill

OrganizationPopular
Tencent
browser-skill

Browser automation through six injected domain tools.

Overview

PublisherTencent
RepositoryBrowserSkill
Skill namebrowser-skill
Stars
4K
Forks
287
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Tencent on GitHub. Read the source before you install it.

Installation

Install the Browser Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Tencent/BrowserSkill.git /tmp/BrowserSkill
mkdir -p .claude/skills
cp -r /tmp/BrowserSkill/packages/dsh-plugin-browserskill/skill .claude/skills/browser-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Browser Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Browser Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Browser Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

browser-skill for DeepSeek Harness

All browser work must use the injected tools directly, in an Agent Window with existing logins. Do not control the browser through another process. Use the loaded action schemas for parameters.

For remote setup or pairing, follow the remote guide before using these tools.

Mandatory workflow

  1. Define success. Start a session and retain sessionId. For a new page:

    text
    browser_session({ action: "start" })
    browser_page({ action: "navigate", session: "<id>", url: "https://example.com" })
    browser_inspect({ action: "observe", session: "<id>" })
  2. For an existing user tab, borrow it instead. Replace example IDs/refs with actual results. Pass session when more than one exists; never use foreign IDs.

  3. Observe after page changes; check ambiguous results once. Stop acting when success is visible. On success or failure, call browser_session({ action: "stop", session: "<id>" }) unless keeping the session open is part of the user's request. Stopping returns borrowed tabs, leaving them open in the user's window.

Read and interact

Prefer observe for text/refs; use snapshot for static accessibility, html for exact markup, and screenshot for visuals. Console/network are bounded read-only diagnostics; follow sequence cursors. Wait only for expected navigation.

To fill an observed field @e3:

text
browser_interact({ action: "fill", session: "<id>", target: "@e3", value: "text" })

Refs invalidate after navigation; large DOM changes may stale them too. Observe again. Prefer refs for frames/shadow roots; selectors search the main document. Use observe for ordinary controls, including before acting on HTML or screenshot findings. Select options by value, not visible label.

  • Hover markers like [hover first: Shoes | Bags] list labels, not refs. Hover the trigger, observe, then use the item's ref. Click the trigger only if its action is wanted.
  • scroll-to returns ancestor-clipped bounds in top-level viewport CSS pixels. Partial visibility suffices; hidden/fully clipped targets fail. It does not test occlusion.
  • wheel uses signed deltaX/deltaY, at least one nonzero. Optional target is scrolled into view first; otherwise it uses the viewport centre. It reports input, not scrolling success: observe afterwards. Focus/blur change focus states.

Borrowing and human help

Use browser_tabs to list IDs before acting. Borrow for the immediate step and return promptly. Browser Automation settings govern confirmation and help; never change them to bypass a prompt or repeat pending/denied/expired borrows. Inspect unknown outcomes; follow version-error hints. Remote reads/actions require task-created or borrowed tabs; popups gain no control. An unowned tab inside the Agent Window needs a user move to a user window before borrowing.

With help enabled, use browser_assist action request-help for login, CAPTCHA, OTP, payment confirmation, consent, or after two attempts without progress. Supply a precise prompt and fresh targets; completion criteria need a stable success signal. Resume only on continued / completed, then observe. Cancellation/timeout blocks the step; do not repeat the request. Navigation alone is not success. browser_assist also resizes windows or emulates a device for one tab.

With help disabled, do not request help or re-enable it. disabled confirms no human action or new permission. Re-observe; use existing logins, authorized inputs and viable alternatives within task/host rules. Vision models may try graphical verification where authorized. Phone-only QR scans, face verification, missing SMS codes or image-only tasks for text-only models may remain blocked. Report missing inputs/capabilities or exhausted alternatives; continue independent work. Never repeat unknown effects or switch backends to bypass limits. Borrow confirmation still applies.

Recover

  • Stale ref: observe, then retry the intended action once.
  • Unknown tab/session: list owned resources or start a session; never guess IDs.
  • Timeout/unknown effect: inspect before retrying; the action may have happened.
  • Unconfirmed fill: read the field. Formatting may satisfy the goal; correct only a remaining difference instead of blindly refilling or requesting help.
  • Other errors: follow the hint; on unrecoverable failure, report and stop the owned session.

Arbitrary page-script evaluation and interaction recording are intentionally unsupported. Do not invent tools or bypass these limits.

Canvas and continuation

@eN canvas [visual:screenshot] is text, not an image. Screenshot the ref when needed; never infer Canvas names/controls from nearby labels. If images cannot be understood, ask for an image-capable model and continue with available semantics.

text
browser_inspect({ action: "screenshot", session: "<id>", ref: "@e3" })
browser_interact({ action: "click", session: "<id>", target: "@e3", captureId: "<capture-id>", imageX: 100, imageY: 50 })

Use the returned captureId and a point actually seen in ORIGINAL PNG pixels, not resized display/viewport coordinates. Captures are single-use, last 2m, and expire on ref replacement or a newer screenshot of that ref. captureUnavailable means view-only: observe and screenshot again before clicking. Counts 1/2 and buttons/ modifiers work; Canvas fill/IME/drag/hover/HTML do not. Repainting is allowed; verify results and use DOM refs for revealed controls. Inspect effect_state=unknown before retrying with a new capture.

No default token cap. With maxTokens, follow nextCursor using observe's cursor for remaining content. Each page replaces refs: use them before continuing, never reuse old ones. Continuation reads the same capture without refresh/depth changes; new observe/snapshot or changed page identity invalidates it.

Frequently asked questions

What does the Browser Skill AI skill do?

Browser automation through six injected domain tools.

Why use Browser Skill on TypingMind?

Because you install it once and use it with any model. Browser Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Tencent/BrowserSkill/tree/main/packages/dsh-plugin-browserskill/skill. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Browser Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser Skill?

As many as you like. As long as a model supports skills, you can use Browser Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser Skill AI skill free?

Yes. It is published on GitHub by Tencent under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇