Skip to content
Back to search

dsh-superworker

A DSH plugin that draws a .superworker/ pipeline record as a work panel, and answers the pipeline's words inside a session.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 18 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/infraredsqy/dsh-superworker with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/infraredsqy/dsh-superworker'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/infraredsqy--dsh-superworker/badge.svg)](/listings/infraredsqy--dsh-superworker)

HTML

<a href="/listings/infraredsqy--dsh-superworker"><img src="/api/listings/infraredsqy--dsh-superworker/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites: a DSH install with a profile to install into, and a workspace that holds a `.superworker/` pipeline record. The panel's writes are answered in place by its host half (the engine's own words layer), so there is no command to install and no `PATH` entry to arrange. The panel reads the workspace of the session you have selected; with no session selected it says so.

Download the `.tgz` from this repo's [Releases](https://github.com/infraredsqy/dsh-superworker/releases) and point DSH at the file:

dsh plugin --profile <name> add ./dsh-superworker-<version>.tgz
dsh plugin --profile <name> add dsh-superworker                  # the same artifact, by name (npm)

The package ships prebuilt — installing runs no build steps. pnpm may print a few `missing peer` warnings: those packages are provided by DSH itself and resolve at runtime, so the warnings can be ignored. The version policy and the third route (installing from git) live in [docs/publish.md](docs/publish.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 97 lines
  1. # dsh-superworker
  2. English | [中文](README.zh.md)
  3. `dsh-superworker` is a [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin
  4. that renders a `.superworker/` pipeline record as a panel in the DSH Web UI.
  5. The host half reads the record (`.superworker/`) of the current session's workspace and serves it behind a
  6. gateway; the browser half draws it as the **Superworker** panel in the sidebar. Everything on screen —
  7. instructions, node details, the map of who owes whom, the issue pool — comes from that record, and
  8. writes from the panel go back to the same place.
  9. In a session the pipeline is also reachable as the agent-facing `superworker` tool: it answers the
  10. pipeline's words in place. The tool is registered once for the whole host, and the registry asks one
  11. condition on every step, so a session whose workspace holds a `.superworker/` record sees the tool
  12. from its first request, and carries the instructions in force into every step as runtime context —
  13. the same text `instruction list` prints for that workspace, which for a git worktree is its main
  14. tree's listing. Anywhere else the tool appears when one of the `sw-*` skills is loaded, or when a
  15. user invokes one: an `/sw-*` invocation is seen before that step is sent, so the request carrying
  16. the skill's instructions already carries the tool. Until then that session's request header stays
  17. exactly as it would be without this plugin. The record is read on every step, not once: a workspace
  18. that gains one mid-session carries the tool from the next step, and a session that leaves the
  19. workspace stops carrying it.
  20. ## Status
  21. Early, and tied to the DSH developer preview. The manifest declares an `engines.dsh` range, and DSH
  22. refuses to install or boot the plugin outside that range (`incompatible-version`, with an opt-in
  23. exemption command). The range follows DSH's breaking line and starts where this line's own mechanism
  24. does: **0.2.2** is the first DSH whose tool registry asks a registration whether a given step should
  25. see it, and that answer is what keeps the tool out of every session without a pipeline. An older
  26. host honors no condition at all, so the tool would simply never appear there — those hosts are
  27. refused up front. Inside 0.2.x any later rc is admitted, and the range moves when DSH moves to 0.3.
  28. The `.superworker/` record it draws is at the same stage: still being worked out, with plenty left
  29. to refine, and it will keep moving as the design settles. Each change follows what running a real
  30. pipeline teaches, so the shape converges on what a pipeline actually needs — and feedback from a
  31. live pipeline is what steers the next one.
  32. ## Install
  33. Prerequisites: a DSH install with a profile to install into, and a workspace that holds a `.superworker/`
  34. pipeline record. The panel's writes are answered in place by its host half (the engine's own words
  35. layer), so there is no command to install and no `PATH` entry to arrange. The panel
  36. reads the workspace of the session you have selected; with no session selected it says so.
  37. Download the `.tgz` from this repo's [Releases](https://github.com/infraredsqy/dsh-superworker/releases)
  38. and point DSH at the file:
  39. ```sh
  40. dsh plugin --profile <name> add ./dsh-superworker-<version>.tgz
  41. dsh plugin --profile <name> add dsh-superworker # the same artifact, by name (npm)
  42. ```
  43. The package ships prebuilt — installing runs no build steps. pnpm may print a few `missing peer`
  44. warnings: those packages are provided by DSH itself and resolve at runtime, so the warnings can be
  45. ignored. The version policy and the third route (installing from git) live in
  46. [docs/publish.md](docs/publish.md).
  47. ## What you get
  48. - a **Superworker** entry in the Web UI sidebar: views over the record — the map, details,
  49. instructions, the issue pool, and the panel's own settings
  50. - a **Superworker settings** section in the DSH settings: whether archived instructions show,
  51. whether closed issues show, whether a settled line opens its next round by itself, and whether the
  52. instructions in force are carried into the session context
  53. - to verify an install: `dsh --profile <name> --dump-config`, and look for the
  54. `# == dsh-superworker` section
  55. ## Development
  56. ```sh
  57. pnpm install --frozen-lockfile
  58. npm test # unit tests: builds both products, then runs both suites
  59. node tools/css-check.mjs # the style-layer rules
  60. npm pack # the distributable
  61. ```
  62. `npm test` builds both products and runs both suites, the plugin's and the engine package's. What
  63. each file pins, and what is walked by hand instead, is in [tests/AGENTS.md](tests/AGENTS.md);
  64. [docs/publish.md](docs/publish.md) carries the hand pass, and `tools/testbed/` boots an isolated
  65. DSH instance for it.
  66. The repository map and ground rules live in [AGENTS.md](AGENTS.md). Read
  67. [docs/design-principles.md](docs/design-principles.md) before touching the UI, and
  68. [docs/publish.md](docs/publish.md) before shipping a version.
  69. ## Contact
  70. Support for running this in your own pipeline, feedback on how it went, and commercial questions
  71. go to [infraredsaw@gmail.com](mailto:infraredsaw@gmail.com). Bugs and feature requests are better
  72. filed as [issues](https://github.com/infraredsqy/dsh-superworker/issues) — that way the next person
  73. who hits the same wall finds them.
  74. ## License
  75. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.