@wxg-prc-cpg/browser-skill-dsh-plugin

BrowserSkill for DeepSeek Harness


Use BrowserSkill in

DeepSeek Harness (dsh) to browse

websites, fill forms, and capture screenshots through native bsk_* tools.

Browser tasks run in Agent Windows, with a live view in the dsh Web UI.

Installation

Before installing the plugin:

• Install DeepSeek Harness and

pnpm, which dsh uses to manage plugins.

• Install the bsk CLI and connect the BrowserSkill extension in Chrome or Edge.

Follow the BrowserSkill setup guide.

• Make sure bsk is on the PATH used to start dsh, or set bskPath in the plugin configuration.

Install the plugin into the web profile, then start it:

dsh plugin --profile web add @wxg-prc-cpg/browser-skill-dsh-plugin
dsh --profile web

Replace web with your profile name if you use a different profile. The plugin

includes the complete browser-skill package; no separate bsk install-skill step is needed.

Its compact entry point loads first; references ship with the plugin and are read only

when needed. Relative paths resolve from the packaged skill directory, not your project.

In a conversation, try:

/browser-skill open example.com and summarize the page.

By default, the browser tools become available when the skill is invoked.

The plugin declares support for DSH ^0.1.5-rc.3 || ^0.2.0-rc.1.

DSH 0.2 checks these peer requirements before loading the plugin; versions outside

this range are not declared compatible. The range preserves the existing 0.1.x

baseline and admits 0.2.x without opting into future 0.3.x hosts.

Updating

Installed plugins do not update automatically. To upgrade this plugin to npm's

latest version, including versions outside the profile's saved dependency range:

dsh plugin --profile web update @wxg-prc-cpg/browser-skill-dsh-plugin --latest

Restart that dsh profile after upgrading. This command updates the plugin; update

the bsk CLI and browser extension separately when a release requires it.

Upgrading to 0.4.1

Update the CLI and restart the running daemon first, install extension 0.4.1,

then update this plugin to 0.4.1. The default target policy requires daemon and

extension protocol 1.8; a successful connection to an older peer does not provide

that capability. Wait for the new extension to be available in your installation

channel before upgrading the plugin. Updating the npm package does not update

the CLI, daemon or extension.

Restart the DSH profile and invoke /browser-skill again in existing conversations.

The six bsk_* tool names remain unchanged. After initial navigation, call

bsk_session action:sync and pass its returned context_id as contextId.

New sessions use target policy: DOM actions can reuse control across supplementary

reads and completed actions, and expect checks protect observed business facts.

Scripts, untargeted keys and visual actions also require the sync's observation_id

as observationId. Human intervention or navigation revokes control; synchronize

and replan. Select policy: "strict" on the first sync to retain the legacy

one-action-per-context workflow. Later syncs and steps preserve the selected policy.

Custom tool integrations must expose and forward these fields. See the

[cooperation reference](skill/references/cooperation.md) for action-specific checks.

Upgrading to 0.4.0

Update the CLI and restart the running daemon first, then update the browser

extension, and finally update this plugin. The 0.4.0 extension requires daemon

protocol 1.6 or later; CLI/daemon 0.3.3 uses 1.3 and cannot connect. Updating the npm

package does not update the CLI, daemon or extension. Use matching 0.4.0 components

for drag, step and saved-observation workflows.

Restart the DSH profile and invoke /browser-skill again in existing conversations.

The six bsk_* tool names remain unchanged. Shared control is now enabled for new

tasks: after initial navigation, call bsk_session action:sync, pass its returned

context identifier as contextId for one action, then synchronize again. Human

edits and changed page evidence can revoke a pending action; synchronize and replan

instead of repeating the old call. Version 0.4.1 changes the default policy as

described above.

Custom tool policies and integrations must allow the new actions they intend to use.

Explicit saveFull results remain as JSON files on the CLI machine until deleted;

closing a browser task or clearing extension storage does not remove them.

See [cooperation](skill/references/cooperation.md) and

[steps and saved observations](skill/references/interaction-details.md#steps-and-saved-observations).

If upgrading from before 0.3.3, also apply the tool-name migration below.

Breaking tool API migration (0.3.3)

The coordinated 0.3.3 release replaces all six browser_* tool names with stable

BrowserSkill-specific names. This avoids collisions with other browser plugins

such as dsh-builtin-browser; both plugins keep their own tools and sessions.

Previous name · New name

browser_session · bsk_session

browser_page · bsk_page

browser_inspect · bsk_inspect

browser_interact · bsk_interact

browser_tabs · bsk_tabs

browser_assist · bsk_assist

The tool-name migration leaves actions, parameters, results and /browser-skill

unchanged. The old tool

names are not registered as aliases. After upgrading, restart the DSH profile and

invoke /browser-skill again in existing conversations to load the new instructions.

Update hardcoded tool calls, allow/deny lists, and toolOrder entries to the new

names. D

…(truncated)