claude-handoff SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
claude-handoff from miklschmidt/archboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add miklschmidt/archboard/claude-handoff@git:20261025.3b43540Pins git:20261025.3b43540 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- miklschmidt/archboard
- Path
.agents/skills/claude-handoff/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261025.3b43540, committed Oct 25, 2026
- Size
- 1,301 bytes
- Repository stars
- 4
- License
- a license file GitHub does not identify
Hand the current conversation off to a fresh background agent that picks up the work immediately.
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 summary of the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the summary as its prompt: `claude --bg --name "<descriptive name>" "<handoff summary>"`. It starts in the current working directory and returns immediately; the user manages it with `claude agents`. Always pass `-n`/`--name` with a descriptive name (e.g. `--name "Fix login bug"`); it sets the display name shown in the job list, session picker, and terminal title. Include a "suggested skills" section in the summary, 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, since the summary becomes the agent's prompt. If the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly.
Read the whole file at its exact version.
How to install
mdr add miklschmidt/archboard/claude-handoff@sha256:6738e8b7c7899ea0The line at the top of this page pins the label git:20261025.3b43540, 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_y3j7rglkkzmpnyoi)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 25, 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 (1301 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
miklschmidt/archboard · 4 stars · license a license file GitHub does not identify · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y3j7rglkkzmpnyoi GET https://markdownregistry.com/api/v1/resolve?ref=miklschmidt/archboard/claude-handoff GET https://markdownregistry.com/api/v1/blob/6738e8b7c7899ea0038fb7a5c859ca1b90c7b1eb40123dcdbe94c51b5b119f12
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 miklschmidt/archboard
Every file in miklschmidt/archboard