Save Thread

nowledge-co/community/nowledge-mem-pi-package/skills/save-thread

by nowledge-co1f4d7eb61466dbfc93ce8d7a0a806c4d4a196dd0No licenseListed Oct 9, 2026Updated Oct 9, 2026

Create a structured handoff summary when the user asks for a checkpoint. Pi transcript sync is automatic; this skill adds a concise continuation record.

Instructions onlyProductivity & Workflow

AI-generated overview

Creates a structured handoff summary of a session so a future session can resume quickly.

What it does: Guides the agent to write a curated checkpoint of a session as a structured handoff, covering goal, decisions, files, outcome, risks and next steps. It shows how to submit that summary as a thread through the nmem command-line tool with a title, content and source. It also explains the difference between a thread, which preserves session structure, and a memory, which distills a single insight.
When to use it: Use it when the user asks to save, checkpoint or record a session, or when a session ends with important context that a future session should carry forward. It is intended for complex multi-step work that will be resumed, not for routine transcript syncing.
Requirements: Requires the Nowledge Mem Pi package and the nmem command-line tool, which is invoked to create the thread. The skill ships no scripts; it is instructions only.

Save Thread

The Nowledge Mem Pi package automatically syncs completed Pi conversations as searchable threads. This skill creates a structured handoff summary when the user wants a concise checkpoint for a future session.

When to Use

User asks to save the session: "save this", "checkpoint", "record what we did"
Session ending with important context that should carry forward
Complex multi-step work that a future session will resume

Do not use this as routine transcript sync. Use it only when a curated handoff would help a future session resume quickly.

Usage

bash

nmem --json t create \  -t "Session Handoff - <topic>" \  -c "Goal: ... Decisions: ... Files: ... Risks: ... Next: ..." \  -s generic-agent

nmem --json t create \  -t "Session Handoff - <topic>" \  -c "Goal: ... Decisions: ... Files: ... Risks: ... Next: ..." \  -s generic-agent

Content Format

Structure the content as a clear handoff. Include only what a future session needs to continue:

Goal: What the session set out to accomplishDecisions: Key choices made and their rationaleFiles: Important files created or modifiedOutcome: What was achievedRisks: Known risks, open questions, or things that could breakNext: Concrete steps for the next session

Goal: What the session set out to accomplishDecisions: Key choices made and their rationaleFiles: Important files created or modifiedOutcome: What was achievedRisks: Known risks, open questions, or things that could breakNext: Concrete steps for the next session

Example

bash

nmem --json t create \  -t "Session Handoff - Auth Migration to OAuth2" \  -c "Goal: Migrate session auth from JWT to OAuth2 with PKCE.Decisions: Chose Authorization Code flow with PKCE over Implicit for security. Using passport-oauth2 library.Files: src/auth/oauth2.ts (new), src/auth/middleware.ts (updated), tests/auth.test.ts (updated).Outcome: Core flow working, token refresh implemented, tests passing.Risks: Token refresh not tested under clock skew; CSRF state parameter still missing.Next: Add CSRF state parameter, update API docs, deploy to staging." \  -s generic-agent

nmem --json t create \  -t "Session Handoff - Auth Migration to OAuth2" \  -c "Goal: Migrate session auth from JWT to OAuth2 with PKCE.Decisions: Chose Authorization Code flow with PKCE over Implicit for security. Using passport-oauth2 library.Files: src/auth/oauth2.ts (new), src/auth/middleware.ts (updated), tests/auth.test.ts (updated).Outcome: Core flow working, token refresh implemented, tests passing.Risks: Token refresh not tested under clock skew; CSRF state parameter still missing.Next: Add CSRF state parameter, update API docs, deploy to staging." \  -s generic-agent

Thread vs Memory

A thread preserves session structure: goals, sequence, context. A memory distills a single insight or decision. They serve different purposes. Use both when appropriate: save the thread for continuity, distill key decisions as standalone memories.

Source and attribution

Source:nowledge-co/communityinnowledge-mem-pi-package/skills/save-threadat commit1f4d7eb

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Save Thread

Save Thread

When to Use

Usage

Content Format

Example

Thread vs Memory

Links

Source and attribution

More from nowledge-co/community

Read Working Memory

Search Memory

Save Thread

Distill Memory

Search Memory

Save Thread

More in Productivity & Workflow

Morning Note

Dd Meeting Prep

Dd Checklist

Deal Tracker

Client Review

Morning Note