handoff SKILL.md skillA
handoff from snapsynapse/skill-provenance is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add snapsynapse/skill-provenance/handoff@git:20260820.3ed2639Pins git:20260820.3ed2639 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- snapsynapse/skill-provenance
- Path
skills/handoff/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260820.3ed2639, committed Aug 20, 2026
- First version recorded
- Apr 12, 2026
- Size
- 3,055 bytes
- Repository stars
- 7
- License
- MIT
Generate a handoff note summarizing skill project state for a future session or collaborator. Use when crossing a non-persistent boundary (e.g., Chat upload), ending a session that made significant decisions, or when the user explicitly asks for a handoff note. Triggers on: "generate a handoff", "write a handoff note", "summarize for next session", "prepare handoff", "what should the next session know".
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
# Skill Provenance: Handoff
Generate a structured handoff note that captures project state for the
next session or a collaborator picking up the work.
## When to use
Run `/skill-provenance:handoff` when:
- Crossing a non-persistent boundary (e.g., uploading to Claude Chat where
filesystem state won't carry over).
- The session made significant decisions not yet reflected in files.
- The user explicitly asks for a handoff note.
- A collaborator or future session needs context beyond what the manifest
and changelog provide.
**When NOT to use:** In filesystem-native environments (Claude Code, IDE)
with a current manifest, changelog, and git history, a handoff note is
usually unnecessary. The manifest and changelog are the handoff.
## Protocol
1. **Read current state.** Load `MANIFEST.yaml` and `CHANGELOG.md` to
understand the bundle's current version and recent history.
2. **Generate the handoff note** with these sections:
- **Current bundle version** — name and semver from the manifest.
- **What was accomplished this session** — summarize the work done,
not just files changed.
- **What is stale and needs attention** — files flagged as behind or
…Read the whole file at its exact version.
How to install
mdr add snapsynapse/skill-provenance/handoff@sha256:2df117cc337d5d73The line at the top of this page pins the label git:20260820.3ed2639, 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_bmivbc2jvhaijx3r)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 12, 2026 and Aug 20, 2026, about one every 130 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260820.3ed2639 latest | 2026-08-20 | 3ed2639 | 3,055 B | A | view · diff |
| git:20260412.2f1c907 | 2026-04-12 | 2f1c907 | 3,028 B | B | 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 (3055 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
snapsynapse/skill-provenance · 7 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bmivbc2jvhaijx3r GET https://markdownregistry.com/api/v1/resolve?ref=snapsynapse/skill-provenance/handoff GET https://markdownregistry.com/api/v1/blob/2df117cc337d5d730b8a6e01190273d61d7d1c7525ac72da779c8c18b8d0aa7f
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 snapsynapse/skill-provenance
Every file in snapsynapse/skill-provenance