kanso-handoff SKILL.md skillA
kanso-handoff from blakecyze/kanso is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add blakecyze/kanso/kanso-handoff@git:20260903.7036f15Pins git:20260903.7036f15 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- blakecyze/kanso
- Path
skills/kanso-handoff/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.7036f15, committed Sep 3, 2026
- Size
- 3,971 bytes
- Repository stars
- 5
- License
- MIT
Use when the user wants the current session's context packaged for the next one: "package this session", "carry this context over", "before I /clear", "handoff", "save where we are", "compact this into a prompt for next time". Writes one dense, machine-readable file and prints the resume line. Not for durable repo guidance (kanso-context) or permanent solution notes.
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
# kanso-handoff Packages what this session knows into `.claude/handoff.md` so `/clear` costs nothing. The file is a baton, not a log: each run overwrites the last, the next session reads it and continues, and nothing else is kept. The audience is the next agent session, not a person. Density beats politeness; a fact the next session must not re-derive beats a paragraph about how it was derived. Everything in `kanso-principles` about earning lines applies double here, because every line of the handoff is paid for at the start of every future turn. ## What goes in Header first, one line: date, branch, `HEAD` short sha. The next session diffs against this to detect drift since the handoff. Then these sections, each optional, each tight. `$ARGUMENTS` may narrow the pack to one strand of a mixed session. | Section | Holds | Rule | |---|---|---| | Goal | The task, one or two sentences, user's point of view | Present tense, no history | | State | Done and verified / done but unverified / not started | Verified means a command ran and passed, nothing softer | | Decisions | Each with its one-line reason | A decision without the why gets re-litigated next session | …
Read the whole file at its exact version.
How to install
mdr add blakecyze/kanso/kanso-handoff@sha256:68db15ba0c73facaThe line at the top of this page pins the label git:20260903.7036f15, 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_dvqepuluvc6knfxo)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 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 (3971 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
blakecyze/kanso · 5 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dvqepuluvc6knfxo GET https://markdownregistry.com/api/v1/resolve?ref=blakecyze/kanso/kanso-handoff GET https://markdownregistry.com/api/v1/blob/68db15ba0c73facae5582b1aae5c6dbab389c29d5651075f10d3a5e2b9d9ab7f
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.