How do I install the Zcode Delegate To Dsh skill?

Run npx skillmds@latest add jeremy9682/zcode-delegate-to-dsh 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 Zcode Delegate To Dsh safe to use?

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

Which AI agents work with Zcode Delegate To Dsh?

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 Zcode Delegate To Dsh free to use?

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

Who published Zcode Delegate To Dsh?

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

Zcode Delegate To Dsh by jeremy9682

Name: Zcode Delegate To Dsh
Author: jeremy9682

Zcode Delegate To Dsh

Delegate a bounded task from ZCode to DeepSeek Harness, agent-run, or Cursor ACP on this machine. Use when the user asks to let DSH / agent-run / Cursor ACP handle a job, or when the work is long-running, mechanical, or needs a governed seat. Triggers on dsh, deepseek harness, agent-run, cursor-agent acp, local-gateway. Never Cursor Cloud.

jeremy9682 fa8b232 3.2 KB Updated Sep 17, 2026

File contents

ZCode → local DSH / agent-run / Cursor ACP

ZCode is a client on this machine. It does not classify seats. Task shape → model/effort stays in this clone's routing-policy.yaml via agent-run (or agent-run-dispatch if install.sh detected a PATH conflict).

Cursor Cloud is not a local socket. Do not call api.cursor.com, do not invent an HTTP gateway, and do not pass --via cloud.

$REPO_ROOT below is the clone of this repository (the directory that contains routing-policy.yaml and scripts/install.sh).

Pick a channel (in this order)

MCP tool dsh_delegate — if dsh appears in ZCode's MCP tool list (config from templates/zcode/config.snippet.json merged into ~/.zcode/cli/config.json or <repo>/.zcode/config.json), call it. One call, one task, committed final answer. This tool spawns dsh --profile headless (DSH_MCP_PROFILE can override; do not set it to web). If the default provider is cursor-acp, the headless profile must already have this clone's adapter and dispatch pack:
```
dsh plugin --profile headless add "$REPO_ROOT/plugins/dsh-llm-cursor-acp"
dsh plugin --profile headless add "$REPO_ROOT/plugins/dsh-dispatch-pack"
```
Web-only installs fail with NO_ADAPTER. Gateway --via dsh is the same profile (DSH_GATEWAY_PROFILE, default headless). Prefer ./scripts/install.sh, which adds both profiles from this clone.

Thin CLI wrapping the same binaries:

node "$REPO_ROOT/gateway/local-gateway.mjs" doctor
node "$REPO_ROOT/gateway/local-gateway.mjs" run --via dsh \
  --cwd /absolute/repo \
  "<complete self-contained task>"

Governed seat (when the user named a task shape or asked for agent-run). Do not guess the shape:

node "$REPO_ROOT/gateway/local-gateway.mjs" run --via agent-run \
  --task-shape ordinary_bug_fix \
  --cwd /absolute/repo \
  "<task>"

Cursor as worker (official ACP stdio, not HTTP):

node "$REPO_ROOT/gateway/local-gateway.mjs" run --via cursor-acp \
  --cwd /absolute/repo \
  "<task>"

ZCode is not an ACP client in the Zed sense; prefer MCP or the CLI. The ACP profile dsh --profile acp is for Zed/JetBrains, not for this session.

What to delegate

Whole bounded units with repo path, goal, constraints, and a verification command.
Long-running or parallel work that does not need this ZCode transcript.

What NOT to delegate

Work that needs this conversation's intermediate state.
Cursor Cloud / any public HTTP URL as if it were agent-run.
Interactive approval-heavy loops (headless uses a one-shot policy).

Guardrails

Verify files/diff after return; never trust the report alone.
Never put API keys in the task text.
One task per call. On failure, retry once with a tighter task text, then stop.

---name: zcode-delegate-to-dshdescription: Delegate a bounded task from ZCode to DeepSeek Harness, agent-run, or Cursor ACP on this machine. Use when the user asks to let DSH / agent-run / Cursor ACP handle a job, or when the work is long-running, mechanical, or needs a governed seat. Triggers on dsh, deepseek harness, agent-run, cursor-agent acp, local-gateway. Never Cursor Cloud.---# ZCode → local DSH / agent-run / Cursor ACPZCode is a **client** on this machine. It does not classify seats. Taskshape → model/effort stays in this clone's `routing-policy.yaml` via`agent-run` (or `agent-run-dispatch` if install.sh detected a PATH conflict).Cursor Cloud is **not** a local socket. Do not call `api.cursor.com`, do notinvent an HTTP gateway, and do not pass `--via cloud`.`$REPO_ROOT` below is the clone of this repository (the directory thatcontains `routing-policy.yaml` and `scripts/install.sh`).## Pick a channel (in this order)1. **MCP tool `dsh_delegate`** — if `dsh` appears in ZCode's MCP tool list (config from `templates/zcode/config.snippet.json` merged into `~/.zcode/cli/config.json` or `<repo>/.zcode/config.json`), call it. One call, one task, committed final answer. This tool spawns `dsh --profile headless` (`DSH_MCP_PROFILE` can override; do not set it to `web`). If the default provider is `cursor-acp`, the **headless** profile must already have this clone's adapter and dispatch pack: ```sh dsh plugin --profile headless add "$REPO_ROOT/plugins/dsh-llm-cursor-acp" dsh plugin --profile headless add "$REPO_ROOT/plugins/dsh-dispatch-pack" ``` Web-only installs fail with `NO_ADAPTER`. Gateway `--via dsh` is the same profile (`DSH_GATEWAY_PROFILE`, default `headless`). Prefer `./scripts/install.sh`, which adds both profiles from this clone.2. **Thin CLI** wrapping the same binaries: ```sh node "$REPO_ROOT/gateway/local-gateway.mjs" doctor node "$REPO_ROOT/gateway/local-gateway.mjs" run --via dsh \ --cwd /absolute/repo \ "<complete self-contained task>" ```3. **Governed seat** (when the user named a task shape or asked for agent-run). Do **not** guess the shape: ```sh node "$REPO_ROOT/gateway/local-gateway.mjs" run --via agent-run \ --task-shape ordinary_bug_fix \ --cwd /absolute/repo \ "<task>" ```4. **Cursor as worker** (official ACP stdio, not HTTP): ```sh node "$REPO_ROOT/gateway/local-gateway.mjs" run --via cursor-acp \ --cwd /absolute/repo \ "<task>" ```ZCode is not an ACP client in the Zed sense; prefer MCP or the CLI. The ACPprofile `dsh --profile acp` is for Zed/JetBrains, not for this session.## What to delegate- Whole bounded units with repo path, goal, constraints, and a verification command.- Long-running or parallel work that does not need this ZCode transcript.## What NOT to delegate- Work that needs this conversation's intermediate state.- Cursor Cloud / any public HTTP URL as if it were `agent-run`.- Interactive approval-heavy loops (headless uses a one-shot policy).## Guardrails- Verify files/diff after return; never trust the report alone.- Never put API keys in the task text.- One task per call. On failure, retry once with a tighter task text, then stop.

Frequently asked questions