handoff SKILL.md skillA
handoff in sutchan/agent-skills-hub is at git:20261017.b913806 (Oct 17, 2026), graded A.
mdr add sutchan/agent-skills-hub/handoff@git:20261017.b913806This copy is 2 versions behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
handoff from alexisbalayre/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexisbalayre/claude-code-config
- Path
.claude/skills/handoff/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.1456344, committed Oct 17, 2026
- First version recorded
- May 23, 2026
- Size
- 940 bytes
- Repository stars
- 3
- License
- MIT
Compact the current conversation into a handoff document for another agent to pick up.
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
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS (`$TMPDIR`, else `/tmp`; `%TEMP%` on Windows) - not the current workspace. Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for. Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead. Redact any sensitive information, such as API keys, passwords, or personally identifiable information. If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
Read the whole file at its exact version.
How to install
mdr add alexisbalayre/claude-code-config/handoff@git:20261017.1456344Pins git:20261017.1456344 in mdr.lock, 2 versions behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6j5mktoayixbxno3/4cbb043950dad2ffd3662ff1a5a0b51ae676004b5cae10e3787e8ee7a4ee69d3.json
Then /plugin install handoff@markdownregistry-6j5mktoayixbxno3 in Claude Code. It installs git:20261017.1456344, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add alexisbalayre/claude-code-config/handoff@sha256:4cbb043950dad2ffThe older copy line above pins the label git:20261017.1456344, 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_6j5mktoayixbxno3)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest sutchan/agent-skills-hub/handoff, and what changed since 4cbb043? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of handoff from somewhere else? Ask it: where did my handoff come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between May 23, 2026 and Oct 17, 2026, about one every 49 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.1456344 latest | 2026-10-17 | 1456344 | 940 B | A | view · diff |
| git:20260917.e147a85 | 2026-09-17 | e147a85 | 894 B | A | view · diff |
| git:20260711.4f85074 | 2026-07-11 | 4f85074 | 878 B | A | view · diff |
| git:20260523.36e5a7e | 2026-05-23 | 36e5a7e | 847 B | A | view |
Copies
Newest: git:20261017.b913806 of handoff in sutchan/agent-skills-hub (skills/handoff/SKILL.md), graded A.
This copy: byte for byte that file's version git:20261007.3e74f1b, which it committed on Oct 7, 2026, before this repository did; graded A, 2 versions behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/handoff/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (940 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
alexisbalayre/claude-code-config · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6j5mktoayixbxno3 GET https://markdownregistry.com/api/v1/resolve?ref=alexisbalayre/claude-code-config/handoff GET https://markdownregistry.com/api/v1/blob/4cbb043950dad2ffd3662ff1a5a0b51ae676004b5cae10e3787e8ee7a4ee69d3
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 alexisbalayre/claude-code-config
Every file in alexisbalayre/claude-code-config