handoff-doc SKILL.md skillA
handoff-doc from minimax-ai/mcode-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add minimax-ai/mcode-stack/handoff-doc@git:20261028.c889a19Pins git:20261028.c889a19 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- minimax-ai/mcode-stack
- Path
stacks/ronny/skills/handoff-doc/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261028.c889a19, committed Oct 28, 2026
- Size
- 2,376 bytes
- Repository stars
- 495
- License
- MIT
Write a hand-off document so a fresh session or another person can continue the current task without the chat history. Use when switching tasks, after several compactions, before clearing a session, or when asked to write a handoff, brief, or progress doc.
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
# Hand-off Doc Important state should not live only in the context window. A short, readable hand-off doc lets you clear the session, start a new one, or pass the work to someone else, and continue with exactly what you consider important. Companion to MCode Engineering Notes 01 and 03. ## 1. Gather from real sources Before writing, check the actual state instead of relying on memory of the conversation: - `git status`, `git log` for the branch, and the current diff. - The test or build commands that were run and their latest real results. - Any existing design, progress or todo files in the repository. - Open issues, PRs or review comments linked to the task. If something cannot be verified, mark it "unverified". ## 2. Write the doc Save it in the repository (for example `docs/handoff/<task>.md`) or wherever the project keeps working notes. Ask before committing it. Use this template: ```markdown # Hand-off: <task> Updated: <date> Branch: <branch> Last commit: <short sha> ## Goal One or two sentences. What "done" looks like, and the acceptance criteria. ## Decisions made - <decision> - because <reason> ## Constraints to keep …
Read the whole file at its exact version.
How to install
mdr add minimax-ai/mcode-stack/handoff-doc@sha256:d3858865023c7b7dThe line at the top of this page pins the label git:20261028.c889a19, 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_2ytztbf3ikeblq66)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 28, 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 (2376 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
minimax-ai/mcode-stack · 495 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2ytztbf3ikeblq66 GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/handoff-doc GET https://markdownregistry.com/api/v1/blob/d3858865023c7b7dad0950ea342d43e91a3e1f33fa476f3cbe434cc099a2f00f
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.