Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nowledge-co avatar

Save Handoff

  • 323 installs
  • 148 repo stars
  • Updated August 3, 2026
  • nowledge-co/community

save-handoff is an AI & Agent Building skill that compacts a long coding-agent session into a structured handoff document so another agent or developer can resume goals, decisions, files, and next steps without rereading

About

save-handoff is a Nowledge community agent skill that creates explicit checkpoint summaries only when a developer asks for a resumable handoff, checkpoint, or session summary. When the nmem CLI is available, the skill runs nmem --json t create with goal, decisions, touched files, risks, and next-step fields scoped to Cursor sessions, producing a structured artifact another agent can load. save-handoff does not claim a first-class live Cursor transcript import and instructs agents to explain plainly when nmem is unavailable instead of fabricating a saved thread. Reach for save-handoff at natural breakpoints in long refactors, debugging marathons, or multi-agent handoffs where losing context would force expensive re-discovery. The skill lives in the nowledge-co/community repository and pairs with Nowledge memory tooling for teams standardizing agent continuity across Claude Code and Cursor workflows.

  • Context compaction
  • Session continuity
  • Agent handoffs
  • Resumable tasks

Save Handoff by the numbers

  • 323 all-time installs (skills.sh)
  • +15 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #2,223 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nowledge-co/community --skill save-handoff

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs323
repo stars148
Last updatedAugust 3, 2026
Repositorynowledge-co/community

How do you hand off a long agent session to another developer?

Compact a long Claude Code session into a handoff document so another agent or developer resumes context without re-reading the full transcript.

Who is it for?

Developers pausing long Cursor or Claude Code sessions who need a compact, honest checkpoint another agent can resume from.

Skip if: Automatic transcript archival on every turn or teams expecting silent background session persistence without explicit user request.

When should I use this skill?

The user explicitly asks for a checkpoint, resumable summary, handoff document, or context transfer before switching agents or ending a session.

What you get

Structured handoff document with goals, decisions, file list, risks, and next actions via nmem JSON or an explicit unavailable notice.

  • Structured handoff JSON via nmem
  • Explicit unavailable notice when tooling is missing

By the numbers

  • Handoff template captures five fields: goals, decisions, files, risks, and next steps

Files

SKILL.mdMarkdownGitHub ↗

Save Handoff

Use this only when the user explicitly asks for a checkpoint, resumable summary, or handoff.

Cursor does not yet have a first-class Nowledge live session importer in this plugin, so do not claim a real thread save.

When nmem is available, create a structured handoff summary through the terminal:

nmem --json t create -t "Cursor Session - <topic>" -c "Goal: ... Decisions: ... Files: ... Risks: ... Next: ..." -s cursor

If nmem is unavailable, explain that plainly instead of pretending the handoff was saved.

Related skills

FAQ

When does save-handoff run?

save-handoff runs only when the user explicitly requests a checkpoint, resumable summary, or handoff. The skill is not a background transcript importer and should not activate on routine conversation turns.

What command does save-handoff use with nmem?

save-handoff calls nmem --json t create with a title, structured content covering goals, decisions, files, risks, and next steps, and a -s cursor source flag. If nmem is missing, the agent must state that plainly.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.