ai-memory-handoff
Skill0 starsChanged 3 months agoMITView on GitHub
Use this skill for any request whose goal is session continuity across agents or time: finding a pending handoff, resuming previous work, saving next-session context, wrapping up, or discarding a mistaken handoff. Trigger by semantic intent rather than exact wording.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- ton-anywhere/my-favorite-promptsedited, first seen Nov 8, 2026
- lucas-Oliveira-01/agentsedited, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- ton-anywhere/my-favorite-prompts★ 438% same
- lucas-Oliveira-01/agents★ 155% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-memory-durable-pagesSkill
- ai-memory-learning-maintenanceSkill
- ai-memory-retrievalSkill
- ai-memory-routing-installSkill
- avc-amendSkill
- avc-build-sliceSkill
- avc-freeze-oracleSkill
- avc-live-qaSkill
- avc-retroSkill
- avc-reviewSkill
- avc-scoutSkill
- avc-spikeSkill
- avc-startSkill
- avc-verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill for single-use cross-session handoffs.
- Distinctive: line 21
If no pending handoff block is visible and the user asks where we left off, then use the accept tool.
- Distinctive: line 39
Default to the current project.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- ai-memory-managed: routing-skill -->ai-memory handoff
Use this skill for single-use cross-session handoffs. Handoffs are for the next agent, not durable project documentation.
Tools in this cluster
memory_handoff_acceptconsumes the pending handoff when the user asks where we left off and no already-fetched handoff block is visible.memory_handoff_begincreates a terse next-session handoff only when the user is wrapping up, ending the session, or explicitly asks to save context for the next session.memory_handoff_cancelexpires a mistaken pending handoff by exact handoff id.
Single-use handoff behavior
The SessionStart hook usually fetches and consumes any pending handoff before the agent sees its first prompt. If the current context already contains a pending handoff block, answer from that block directly. Do not call the accept tool again to find it in another project, because handoffs are single-use and the tool will normally return null after SessionStart consumed it.
If no pending handoff block is visible and the user asks where we left off, then use the accept tool. Keep the default current-project scope unless the user explicitly names a sibling workspace and project.
Creating a handoff
Create a handoff only at session end or when the user explicitly asks to save context for the next session. Do not use handoffs for status checks, briefings, project notes, or permanent memory. Keep the summary to two or three concise sentences, and put details in open questions and next steps bullets.
Lifecycle hooks already capture routine prompts and tool calls, so do not manually write a handoff just to record normal progress.
On a shared server, a handoff belongs to the operator who created it. Set shared: true only when the user explicitly wants any operator in the project to receive the baton; do not infer sharing from ordinary collaboration prose.
Canceling a handoff
Cancel only when the user asks to discard a handoff or you created one by mistake. Use the exact handoff id returned by the begin tool. Cancellation is idempotent from the user's point of view, but it should still target only the known handoff.
Accept and cancel normally act only on the caller's own plus shared handoffs. any_owner: true is a root-only recovery action over another operator's context; use it only on an explicit user request.
Scope default
Default to the current project. Pass workspace and project together only when the user names a different project. Never pass scope arguments just because the user says this project, here, we, or our work.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.