skills.rest
cryptopafi
cryptopafiCOMMUNITY
Explore all skills by this author →
GitHub

handoff

Capture session state, save unsaved skills, and generate structured summaries.

1|Updated Apr 12, 2026
Search Tags:#notion#task-management#memory-management#git-sync#session-handoff#cortex#background-agents
One-click install
npx skills add https://github.com/cryptopafi/nexusos-skills --skill handoff-cryptopafi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/cryptopafi/nexusos-skills/tree/main/handoff
Command: npx skills add https://github.com/cryptopafi/nexusos-skills --skill handoff-cryptopafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates complete session handoff to prevent loss of work, consolidate session artifacts, and prepare a clean state for the next session.

Core Features & Use Cases

  • Scan & Persist: Detect unsaved Cortex items and save them reliably with backup queuing when Cortex or Notion are unreachable.
  • Structured Session Summaries: Create or append a session file with accomplishments, decisions, files changed, Cortex/Notion references, and background agent reports.
  • Memory & Task Maintenance: Compact MEMORY.md into topic files, update per-user task files with a concurrent-write lock, and mark completed or pending tasks with context for next session.
  • Integration & Sync: Validate FORGE format for procedures, handle Notion dashboard updates with exponential backoff, and perform a git sync to persist local project changes.
  • Use Case: At the end of a development or research session, run handoff to capture all created skills, procedures, and pending work so the next session resumes without context loss.

Quick Start

Run the handoff skill to save unsaved work, compact memory, update tasks, check agents, sync git, and generate the final session report.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent data loss when ending a coding session?▼

Preventing data loss when ending a coding session requires a structured handoff that scans unsaved work, compacts memory, updates tasks, and syncs git to securely persist current state.

What is the best way to save session state to Notion and local memory?▼

Saving session state to Notion and local memory involves updating the Notion dashboard with exponential backoff while compacting MEMORY.md into topic files to preserve accomplishments and pending tasks.

How do I manage background agents and memory files when switching sessions?▼

Managing background agents and memory files when switching sessions requires checking active agents, verifying active modes, and compacting MEMORY.md into structured topic files to ensure zero context loss.

Does session handoff work without a continuous connection to Notion?▼

Session handoff works without a continuous Notion connection by utilizing backup queuing and error handling with backoff for transient failures to securely persist data when external services are unreachable.

What is included in a structured session summary for automated restore?▼

A structured session summary for automated restore includes accomplishments, decisions, files changed, Cortex and Notion references, and background agent reports to prepare a clean state for the next session.

Related Skills

Explore More Software Engineering Skills→
JaviMontanoJaviMontano

cli-init

Launch an interactive CLI wizard to initialize client environments and generate discovery context.

Community
Intermediate
HuuBarHuuBar

continue-claude-work

Extract session metadata and summaries from Claude Code artifacts into a resume briefing.

Community
Advanced
mpauloskympaulosky

distributed-mesh

Coordinate cross-machine squad state by synchronizing state files via git mesh transport.

Community
Advanced
cowwoccowwoc
101

cat:spawn-subagent

Launch a Claude Code subagent in an isolated git worktree.

Community
Advanced