gdd-route-dsh SKILL.md skillA
gdd-route-dsh from wxxb789/hoa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wxxb789/hoa/gdd-route-dsh@git:20261118.d4726dePins git:20261118.d4726de in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wxxb789/hoa
- Path
skills/gdd-route-dsh/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261118.d4726de, committed Nov 18, 2026
- Size
- 15,901 bytes
- Repository stars
- 3
- License
- MIT
Use when a bounded task is dispatched to a DeepSeek Harness (`dsh`) headless worker — standalone through the adapter or as one `gdd` stage, instead of or beside the OMP route — a dsh run reports success without doing the work, a run must be resumed, stopped or recovered, or the DSH launcher route needs configuring. Completion comes from the exit code plus the final NDJSON turn event, not the worker's own report. Not for deciding what to build (the goal contract) or the delivery protocol (`gdd`).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# gdd-route-dsh A second headless route for goal-driven delivery: `dsh --profile headless` answers one task per invocation, streams NDJSON events, and resumes a persisted session. Model tool writes are constrained by the permission policy, not by the working directory: with the default `workspace-write` policy, on a host whose harness enforces a sandbox, writes inside the policy's boundary succeed and writes outside it are denied; `--cwd` only selects the run's working directory. Changing the profile or `DSH_PERMISSION_MODE` changes that boundary, so re-confirm it before dispatching (see "Harness facts that bite"). The protocol stays in `gdd`; this skill is the operating method for that route, invoked from the DSH route row of [`../gdd/references/transport.md`](../gdd/references/transport.md). ## When to Use - Dispatching a stage to DSH: `GDD_LAUNCHER=<repo>/skills/gdd/scripts/adapters/dsh-run.py uv run skills/gdd/scripts/gdd.py stage …`, or the same adapter by hand. - Diagnosing a dsh stage that exited 0 but did not do the work, refused to resume, or stalled. - Not for choosing the increment (goal contract / `define-goal`), and not for OMP/Paseo route details …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kgpa4wn6wad4zyyp/ee859942192a67dfa27b544f7d238d734c219c25b18299990652806b2688086e.json
Then /plugin install gdd-route-dsh@markdownregistry-kgpa4wn6wad4zyyp in Claude Code. It installs git:20261118.d4726de, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add wxxb789/hoa/gdd-route-dsh@sha256:ee859942192a67dfThe line at the top of this page pins the label git:20261118.d4726de, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kgpa4wn6wad4zyyp)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in wxxb789/hoa/gdd-route-dsh since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of gdd-route-dsh from somewhere else? Ask it: where did my gdd-route-dsh come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 18, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/gdd-route-dsh/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15901 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wxxb789/hoa · 3 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kgpa4wn6wad4zyyp GET https://markdownregistry.com/api/v1/resolve?ref=wxxb789/hoa/gdd-route-dsh GET https://markdownregistry.com/api/v1/blob/ee859942192a67dfa27b544f7d238d734c219c25b18299990652806b2688086e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.