handoff-spec SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
handoff-spec from dzhng/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dzhng/skills/handoff-spec@git:20261002.e497761Pins git:20261002.e497761 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dzhng/skills
- Path
skills/engineering/handoff-spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261002.e497761, committed Oct 2, 2026
- Size
- 1,393 bytes
- Repository stars
- 1,377
- License
- MIT
Hand a spec that is mid-implementation to another machine or another agent.
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
# Handoff Spec I'm moving this spec's work to another machine or another agent. The next session starts **cold**: it has the repository and nothing else. It has none of this conversation, none of this machine's files and none of your memory. Leave the spec so that session can carry on as if it had been here. Collect what this session knows and the spec doesn't yet say, from the discussion and from the work itself, and put it in the spec: - what is done, what is half-done and exactly where it stopped, and what is next; - what I decided or corrected along the way, and how I want the work done; - calls you made where I was silent, and anything still waiting on me; - what is known to be broken or unverified, with what you already found out about it; - anything that lives only on this machine and the next session needs: unpushed branches, uncommitted work, scratch results worth keeping. Write it into the spec's own handoff, in place: the spec stays one current account, not a transcript with a new note on top. Then push, so everything the spec points at exists on the remote. Done when a fresh agent, given only the repository, would pick the same next …
Read the whole file at its exact version.
How to install
mdr add dzhng/skills/handoff-spec@sha256:e902beff153a2242The line at the top of this page pins the label git:20261002.e497761, 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_w35prkcij66v4vwa)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 2, 2026.
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 (1393 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
dzhng/skills · 1,377 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w35prkcij66v4vwa GET https://markdownregistry.com/api/v1/resolve?ref=dzhng/skills/handoff-spec GET https://markdownregistry.com/api/v1/blob/e902beff153a2242f409da8de0333ab8be4871746f29c4d753808844036a1700
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.