cyberneticlibrary

Hand off conversations to another agent seamlessly

handoffpluginsetup L217,464
alirezarezvani/claude-skills
What it does

Compact conversations into handoff documents for next agent

Best for

Passing work to a fresh agent when session time/token limits are hit, without losing critical context or exposing secrets.

Inputs
  • · Full conversation thread (auto-captured)
  • · User redaction preferences (on first run)
  • · Save location (OS temp, home, or per-project .handoff/)
Outputs
  • · Markdown handoff document (summary, context, next steps, suggested skills)
  • · Redacted secrets (API keys, passwords, tokens stripped)
  • · Metadata (file location, SessionStart auto-load pointer)
Requires
  • · File system (for .handoff/ folder creation and write)
  • · Session storage (for SessionStart auto-load)
Preconditions
  • · First-run setup asks where to save (prevents project folder clutter)
  • · Conversation must be coherent enough to summarize (thin threads may produce thin handoffs)
  • · SessionStart auto-load requires matching session config
Failure modes
  • · Redaction may miss context-specific secrets (e.g., internal references that look like keys)
  • · Handoff quality depends on conversation coherence (multi-threaded or circular conversations degrade)
  • · SessionStart auto-load may fail if .handoff/ path changes or session config mismatches
Trust signals
  • · Paired with engineering/handoff (distinct productivity variant with extra features)
  • · Redaction enforcement is explicit (strips secrets before write)
  • · SessionStart auto-load reduces manual context copy/paste
  • · Configurable save location prevents accidental project folder pollution