How do I install the Dsh Delegate Runtime skill?

Run npx skillmds@latest add hekmon8/dsh-delegate-runtime in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dsh Delegate Runtime safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dsh Delegate Runtime?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dsh Delegate Runtime free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dsh Delegate Runtime?

hekmon8 (@hekmon8) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dsh Delegate Runtime by hekmon8 — Agent Skill

Name: Dsh Delegate Runtime
Rating: 4.5 (4 reviews)
Author: hekmon8

File contents

dsh bridge runtime contract

Every DeepSeek Harness interaction goes through one script:

node "${CLAUDE_PLUGIN_ROOT}/scripts/dsh-bridge.mjs" <subcommand> [flags] [text]

stdout is the user-facing result; render it verbatim. A nonzero exit means the run failed and stderr carries the reason.

Subcommands

Subcommand	Purpose	Key flags
`check`	readiness probe	`--json`
`setup`	create/verify the multi-turn `cc` profile	`--json`
`review`	read-only code review	`--base <ref>`, `--scope`, `--model`, `--effort`, `--background`
`critique`	structured adversarial critique	same as review
`run`	task execution	`--write`, `--session`, `--resume`, `--fresh`, `--model`, `--effort`, `--background`, `--prompt-file`
`run-resume-candidate`	is a resumable dsh session available?	`--json`
`import`	weak-import this conversation into a resumable session	`--source <jsonl>`
`runs`	list runs / one run's status	`[run-id]`, `--all`
`show`	stored result of a finished run	`[run-id]`
`stop`	kill a run's process tree / the broker	`[run-id]`, `--broker`

Facts that shape correct usage

Sandbox: default runs are read-only; --write grants workspace-write. There is no mid-run approval — permissions are decided before launch.
Fresh runs are one-shot headless dsh sessions and are NOT resumable. Only --session, --resume, and import (broker paths) record resumable session ids.
--model/--effort work on one-shot runs; a --resume keeps the broker's startup model. Plugin defaults when omitted: model deepseek-v4-pro, effort max (one-shot and broker alike).
--background returns immediately with a run id; the actual work continues in a detached worker. Poll runs <id>, fetch show <id>.
stop kills processes; a mid-turn broker stop discards all in-memory dsh sessions for the workspace.
Environment: DSH_BINARY overrides the dsh executable; DSH_CC_SESSION_ID/DSH_CC_TRANSCRIPT_PATH are exported by the SessionStart hook — never set them manually.

Failure handling

"dsh CLI is not installed" → point the user at /dsh:check.
"cc profile" errors on --session/--resume/import → point at /dsh:setup.
"broker is busy" → one run at a time per workspace; wait or stop --broker.
Structured critique that reports "unstructured output" still contains the raw review text; show it.

---name: dsh-delegate-runtimedescription: Internal contract for calling the dsh bridge from commands and the dsh-delegate agent — subcommands, flags, environment, and failure handling. Read before composing any dsh-bridge.mjs invocation.---# dsh bridge runtime contractEvery DeepSeek Harness interaction goes through one script:```bashnode "${CLAUDE_PLUGIN_ROOT}/scripts/dsh-bridge.mjs" <subcommand> [flags] [text]```stdout is the user-facing result; render it verbatim. A nonzero exit means the run failed and stderr carries the reason.## Subcommands| Subcommand | Purpose | Key flags ||---|---|---|| `check` | readiness probe | `--json` || `setup` | create/verify the multi-turn `cc` profile | `--json` || `review` | read-only code review | `--base <ref>`, `--scope`, `--model`, `--effort`, `--background` || `critique` | structured adversarial critique | same as review || `run` | task execution | `--write`, `--session`, `--resume`, `--fresh`, `--model`, `--effort`, `--background`, `--prompt-file` || `run-resume-candidate` | is a resumable dsh session available? | `--json` || `import` | weak-import this conversation into a resumable session | `--source <jsonl>` || `runs` | list runs / one run's status | `[run-id]`, `--all` || `show` | stored result of a finished run | `[run-id]` || `stop` | kill a run's process tree / the broker | `[run-id]`, `--broker` |## Facts that shape correct usage- Sandbox: default runs are read-only; `--write` grants workspace-write. There is no mid-run approval — permissions are decided before launch.- Fresh runs are one-shot headless dsh sessions and are NOT resumable. Only `--session`, `--resume`, and `import` (broker paths) record resumable session ids.- `--model`/`--effort` work on one-shot runs; a `--resume` keeps the broker's startup model. Plugin defaults when omitted: model `deepseek-v4-pro`, effort `max` (one-shot and broker alike).- `--background` returns immediately with a run id; the actual work continues in a detached worker. Poll `runs <id>`, fetch `show <id>`.- `stop` kills processes; a mid-turn broker stop discards all in-memory dsh sessions for the workspace.- Environment: `DSH_BINARY` overrides the dsh executable; `DSH_CC_SESSION_ID`/`DSH_CC_TRANSCRIPT_PATH` are exported by the SessionStart hook — never set them manually.## Failure handling- "dsh CLI is not installed" → point the user at `/dsh:check`.- "cc profile" errors on `--session`/`--resume`/`import` → point at `/dsh:setup`.- "broker is busy" → one run at a time per workspace; wait or `stop --broker`.- Structured critique that reports "unstructured output" still contains the raw review text; show it.

Frequently asked questions

Dsh Delegate Runtime