recover-killed-session-from-transcript-and-worktree SKILL.md skillA
recover-killed-session-from-transcript-and-worktree from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/recover-killed-session-from-transcript-and-worktree@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/recover-killed-session-from-transcript-and-worktree/SKILL.md- Versions recorded
- 6
- Latest version
- v1.1.0, committed Sep 17, 2026
- First version recorded
- Aug 10, 2026
- Size
- 7,907 bytes
- Repository stars
- 3
- License
- MIT
Recover a prior Claude Code session that crashed or was killed mid task — its plan, its work and what killed it — from its transcript and its leftover worktree.
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
# Recover a killed Claude Code session from its transcript + worktree ## Problem A prior session was doing real work (building a feature, fixing a batch of issues) and got killed mid-task — a hung tool call, an API 529 after a long run, the user quit. It left uncommitted WIP and a half-finished plan, but no handoff. Starting fresh wastes the work AND risks repeating whatever killed it. The session's full intent + state lives in its **transcript JSONL** + its **worktree artifacts** — recover from there. ## Context / Trigger Conditions **Every trigger below depends on a human noticing.** That is this skill's weak point, not its scope: a subagent killed mid-run leaves its partial output sitting in the parent's transcript, and a later session resuming that branch reads it as a finished result. Nothing prompts anyone to reach for this skill at all. The [`resume-gate`](../../hooks/resume-gate/) hook in this same plugin is the automatic trigger. It runs on `SessionStart:resume`, detects the two ways a subagent dies (the harness's own partial-output notice for a synchronous one; a non-`completed` task-notification status for an …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/recover-killed-session-from-transcript-and-worktree@sha256:0f8a79c4dba86160The line at the top of this page pins the label v1.1.0, 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_4dmmyg63pof7bcgc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 10, 2026 and Sep 17, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-09-17 | 9d1df51 | 7,907 B | A | view · diff |
| v1.1.0 | 2026-08-12 | 5811428 | 7,548 B | A | view · diff |
| v1.1.0 | 2026-08-10 | 1445caa | 7,594 B | A | view · diff |
| v1.0.0 | 2026-08-10 | 5b6d8a2 | 6,225 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a58c34c | 6,202 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a39e221 | 7,196 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 (7907 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4dmmyg63pof7bcgc GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/recover-killed-session-from-transcript-and-worktree GET https://markdownregistry.com/api/v1/blob/0f8a79c4dba861609003eba570c44a16e198e570ee207af3f6d9553f07c7280c
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.