# AI Memory Handoff

Use this skill for any request whose goal is session continuity across agents or time...

- Repository: https://github.com/akitaonrails/ai-memory (14817 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add akitaonrails/ai-memory --skill ai-memory-handoff -g -a claude-code -y`
Codex: `npx skills add akitaonrails/ai-memory --skill ai-memory-handoff -g -a codex -y`
Cursor: `npx skills add akitaonrails/ai-memory --skill ai-memory-handoff -g -a cursor -y`
Gemini CLI: `npx skills add akitaonrails/ai-memory --skill ai-memory-handoff -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add akitaonrails/ai-memory`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- 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_list` is the read-only inspect path: it returns open handoffs without claiming or expiring them. Use it when no SessionStart handoff block is in context (Grok, Zero, and other no-stdout / MCP-only clients), when the user asks what is pending, or when you need an exact id.
- `memory_handoff_accept` consumes one open handoff. Prefer listing first when no prepended block is visible, then pass the listed `handoff_id` to claim that exact row. Omitting `handoff_id` claims the latest eligible open handoff. Use this when the user asks where we left off and no already-fetched handoff block is visible.
- `memory_handoff_begin` creates 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_cancel` expires a mistaken pending handoff by exact handoff id from begin or list.

## 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: after SessionStart consumed it the tool returns no handoff, with `status` `consumed_by_hook` when the client forwards its session id and `none_pending` otherwise.

If no pending handoff block is visible, inspect with `memory_handoff_list` first. Listing does not claim or expire anything. When the user asks where we left off, claim one listed row with `memory_handoff_accept` and that `handoff_id`, using the client-aware project scope below. Do not treat list as a second accept path.

## When a harness was cut off

The rest: https://github.com/akitaonrails/ai-memory/blob/HEAD/crates/ai-memory-core/src/routing_skills/ai-memory-handoff/SKILL.md