handoff

Use it when:: A session starts without fresh context and you ask "where were we" or want to pick up where you left off.
It does:: Finds the latest session whose directory matches this project, then searches memory for its key files, decisions and errors.
You get:: A short resume: any unanswered question first, then the session's summary, key files and decisions, and one next step.
Needs:: agentmemory's memory server and MCP tools, plus its capture hooks recording your sessions: connecting the tools alone records no sessions.
Unlike handoff documents:: It writes nothing at the end of a session; it reads the sessions agentmemory recorded.

Skill 1 of 8 in the agentmemory bundle, before recall.

TL;DR

Part of agentmemory, a memory server that records coding agents' sessions. handoff resumes work in the current directory, or one you name. The agent fetches the project's sessions and picks the most recent whose working directory is this one, a folder inside it or a folder containing it, so a sibling such as /repo-a-staging is never taken for /repo-a, preferring completed sessions over abandoned ones. With no match it says so and stops, rather than resuming another project's session. If the session ended on a question for you, found in its summary or in recent conversation entries ending in a question mark, that comes first. Then it summarizes the title, key files and key decisions or errors from a memory search on the session's top concepts, keeping only results from that session or project, and ends with one concrete next step.

Summarizes the skill at f0f7378.

npx skills add https://github.com/rohitg00/agentmemory --skill handoff

skills.sh page Source on GitHub All skills from rohitg00/agentmemory

Total Downloads: 14,000 on skills.sh, Nov 9, 2026
Repo stars: 30,216 rohitg00/agentmemory
First seen: May 18, 2026 on skills.sh

Weekly Downloads

256

-32% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	375
Sep 28	329
Oct 5	291
Oct 12	293
Oct 19	304
Oct 26	299
Nov 2	285
Nov 9	256

Category	category:agents category:software-engineering Build agents, orchestrate workers and give agents memory. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:tool Operates a CLI, API, app or bundled script to get something done.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:mcp Needs an MCP server connected.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	memory handoff
Stack	stack:agentmemory

SKILL.md

From rohitg00/agentmemory at f0f7378. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: handoff
description: Resume the most recent agent session for the current working directory, leading with any unanswered question. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context.
argument-hint: "[optional cwd override]"
user-invocable: true

The user wants to resume work. Optional cwd override: $ARGUMENTS

Quick start

memory_sessions { "project": "<current-project-id>", "limit": 20 }

Pick the most recent session whose cwd matches this project, then: memory_recall { "query": "<session top concepts>", "project": "<current-project-id>", "limit": 10 }. When an agent is requested, pass the same agentId to both calls.

Expected output:

Resuming 7f3a9c2 "Auth refresh rework".
Open question: should logout revoke all device tokens or just the current one?
Next step: decide revoke scope, then update auth/logout.ts.

Why

Match the session by directory boundary, not raw prefix, so a sibling repo never gets mistaken for this one. Never invent observations for an empty session.

Workflow

Resolve the project path: if $ARGUMENTS is given, normalize it to absolute (path.resolve(process.cwd(), $ARGUMENTS)); else use the cwd.
Call memory_sessions with the exact project identifier when known, and agentId when requested. Otherwise follow nextCursor until the matching directory is found or pagination ends. Preserve filters between pages. Pick the most recent session whose normalized cwd matches by directory boundary: equality, OR cwd.startsWith(projectPath + sep), OR projectPath.startsWith(cwd + sep). Prefer completed over abandoned. No match: report that this project has no matching session and stop. Do not substitute a different project's session.
If the session ended on an unanswered user-facing question, surface it FIRST. Look in summary or recent conversation observations whose narrative ends in ?.
Summarize: title/summary, key files, key decisions or errors, using memory_recall on the top concepts, limit 10, preserving the chosen project and agent scope. Check each result's session or project provenance before including it; a query alone does not enforce scope.
End with one concrete "next step?" pointer.

Anti-patterns

WRONG: session.cwd.startsWith(projectPath) matches /repo-a-staging when the project is /repo-a, resuming the wrong repo's session.

RIGHT: session.cwd === projectPath || session.cwd.startsWith(projectPath + sep), a directory-boundary check that cannot cross sibling repos.

Checklist

cwd override resolved to an absolute, normalized path.
Match used a directory-boundary check, not a raw prefix.
Unanswered question (if any) leads the response.
Empty session is reported plainly, with an offer to start fresh.

Troubleshooting

See TROUBLESHOOTING.md if memory_sessions or memory_recall is not available.