gsd-debug skillA
gsd-debug is agent-read markdown (skill) from coco-research/coco: Use when a bug, failing test, or unexpected behaviour needs investigation, especially across sessions or context resets. Isolates it in a debugger subagent with persistent .planning/debug state, unlike skills/systematic-debugging..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
<objective> Debug issues using scientific method with subagent isolation. **Orchestrator role:** Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations. **Why subagent:** Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction. **Flags:** - `--diagnose` — Diagnose only. Find root cause without applying a fix. Returns a structured Root Cause Report. Use when you want to validate the diagnosis before committing to a fix. </objective> <available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'): - gsd-debugger — Diagnoses and fixes issues </available_agent_types> <context> User's issue: $ARGUMENTS Parse flags from $ARGUMENTS: - If `--diagnose` is present, set `diagnose_only=true` and remove the flag from the issue description. - Otherwise, `diagnose_only=false`. Check for active sessions: ```bash ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5 ``` </context> <process> ## 0. Initialize Context ```bash INIT=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" state load) …
Read the whole file at its exact version.
How to install
mdr add coco-research/coco/gsd-debug@git:20260914.e75f220mdr add coco-research/coco/gsd-debug@sha256:a9a89f1a347b3216Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_rrv5j72hnpbalcx5)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.e75f220 latest | 2026-09-14 | e75f220 | 5,090 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 4,924 B | A | view |
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 (5090 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
coco-research/coco · 478 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rrv5j72hnpbalcx5 GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/gsd-debug GET https://markdownregistry.com/api/v1/blob/a9a89f1a347b3216f2a822318566f5b321f16f2d51adada2ba0dc4b8f38d61f4
Your agent 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.