handoff SKILL.md skillA
handoff from umararshad4/honey-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add umararshad4/honey-stack/handoff@git:20261101.60c9199Pins git:20261101.60c9199 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- umararshad4/honey-stack
- Path
skills/handoff/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261101.60c9199, committed Nov 1, 2026
- First version recorded
- Oct 17, 2026
- Size
- 4,856 bytes
- Repository stars
- 4
- License
- MIT
Write or restore a handoff doc so a fresh session can pick up this work.
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
A handoff carries this session's state to a fresh one. The next agent has none of this conversation, so the doc is everything it knows. Write it for a capable stranger who has the repo but not your memory.
Pick the branch from the argument:
- `handoff` or `handoff <focus>`: **Write**. A focus ("next: the billing ticket") tailors the doc to what the next session will do.
- `handoff restore` (or `resume`, `pickup`), optionally with a title fragment or path: **Restore**.
## Write
### 1. Gather state
Read it from the repo, not from memory: `git rev-parse --abbrev-ref HEAD; git status --short; git diff --stat; git log --oneline -10`. Outside git, list the files you edited this session. Take checks from this session's transcript: only commands you ran and whose output you read.
Done when: branch, changed files and check results are in hand.
### 2. Write the doc
Compute the path in shell so the name is sanitized. It goes in the OS temp dir (Windows: `%TEMP%`), outside the workspace, so it never lands in a commit:
```bash
REPO=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]\{1,\}/-/g; s/^-//; s/-$//')
…Read the whole file at its exact version.
How to install
mdr add umararshad4/honey-stack/handoff@sha256:aad7e6518d03b60eThe line at the top of this page pins the label git:20261101.60c9199, 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_irzleg2m37vgz5sv)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 17, 2026 and Nov 1, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261101.60c9199 latest | 2026-11-01 | 60c9199 | 4,856 B | A | view · diff |
| git:20261017.c52b424 | 2026-10-17 | c52b424 | 4,493 B | A | view · diff |
| git:20261017.6c6369a | 2026-10-17 | 6c6369a | 4,468 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 (4856 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
umararshad4/honey-stack · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_irzleg2m37vgz5sv GET https://markdownregistry.com/api/v1/resolve?ref=umararshad4/honey-stack/handoff GET https://markdownregistry.com/api/v1/blob/aad7e6518d03b60e97aa374716fda7aa9c54b4a3dbbe01ad4cc411a85fcc7f8c
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.
More from umararshad4/honey-stack
Every file in umararshad4/honey-stack