Save Thread
Keep the old save-thread skill name working while honestly saving a resumable handoff instead of a fake full-transcript import in generic npx skills runtimes.
Overview
Save Thread is a journey-wide agent skill that preserves the legacy skill name while routing generic runtimes to an honest resumable handoff instead of claiming full transcript import.
Install
npx skills add https://github.com/nowledge-co/community --skill save-threadWhat is this skill?
- Deprecated alias that must not promise lossless transcript import
- Routes users to save-handoff for generic npx skills environments
- Documents runtime limits: no guaranteed session files, history API, or native importer
- Instructs concise resumable handoff via nmem t create with explicit summary-only labeling
- Prevents misleading retrieval that looks like the full original thread
Adoption & trust: 592 installs on skills.sh; 91 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You still call save-thread in a shared skills pack, but your runtime may not expose the real chat transcript—so a “saved thread” could be a lie.
Who is it for?
Migrating old workflows that referenced save-thread in npx skills without overpromising transcript fidelity.
Skip if: Builders who need guaranteed full-session capture—use the host agent’s native connector or importer instead of this compatibility alias.
When should I use this skill?
A prompt or workflow still references save-thread in a generic npx skills environment where real transcript APIs are not guaranteed.
What do I get? / Deliverables
The agent saves a labeled handoff summary via the save-handoff path (e.g. nmem t create) and steers you to native capture when you need the full session.
- Labeled resumable handoff summary
- Explicit disclaimer that output is not transcript-backed
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Pause a long implementation run and file a resumable handoff before closing the IDE.
Capture review context as a labeled summary when switching from one agent to another mid-PR.
Resume incident debugging tomorrow without pretending yesterday’s full transcript was imported.
Hand off scoping notes to a different machine when only skill-level prompting is available.
How it compares
Compatibility shim for naming, not a transcript vault like a native session export.
Common Questions / FAQ
Who is save-thread for?
Solo and indie builders still invoking the deprecated save-thread slug in generic npx skills environments who need backward-compatible behavior without false transcript promises.
When should I use save-thread?
Use it whenever an old prompt names save-thread during Build handoffs, Ship review pauses, or Operate iteration—anytime you must resume later in a runtime that may not expose session history; it should behave like save-handoff and label output as summary-only.
Is save-thread safe to install?
It is a small procedural skill with no special privileges beyond what your agent already has; review the Security Audits panel on this Prism page before trusting third-party packs.
Workflow Chain
Then invoke: save handoff
SKILL.md
READMESKILL.md - Save Thread
# Save Thread (Deprecated Compatibility) > Preserve the old skill name without pretending a generic skill runtime can always import the real session transcript. ## Status This skill name is **deprecated** and kept only for compatibility. Use `save-handoff` for generic `npx skills` environments. ## Why This Cannot Promise Real Thread Save A shared skills package works across many agent runtimes. In many of them, a skill can influence prompting but cannot read the host agent's real session transcript through a stable programmatic API. That means this package must not promise a lossless thread import when the runtime may not expose: - readable session files - a transcript/history API - a native importer surface wired for that specific agent If we claimed real thread save here, users would believe later retrieval reflects the actual full session when it may only contain a summary. ## What To Do Instead In generic skill environments, treat `save-thread` as an alias for `save-handoff`: - save a concise resumable handoff with `nmem t create` - state clearly that this is a handoff summary, not a transcript-backed import - never present the result as the full original session ## When Real Thread Save Is Feasible Use a dedicated native connector when the runtime has a real transcript importer. Examples include Nowledge connectors such as: - Gemini CLI - Claude Code In those environments, `nmem t save --from <runtime>` can read local session files on the client machine and upload normalized thread messages to Mem. ## When To Use Which Save Surface Use **save-handoff** when: - you are in a generic `npx skills` environment - you want a restart point, checkpoint, or concise continuation summary - the runtime does not have a proven native thread importer Use a native **save-thread** only when: - the agent has a dedicated Nowledge connector for that runtime - real transcript import is actually implemented for that runtime - you want the actual session captured for later search and inspection ## Usage In Generic Skills Environments Create a structured handoff instead of pretending to save the real thread: ```bash nmem --json t create -t "Session Handoff - <topic>" -c "Goal: ... Decisions: ... Files: ... Risks: ... Next: ..." -s generic-agent ``` ## Response Format After successful save in a generic skills environment: ``` ✓ Handoff saved Title: {title} Summary: {content} Thread ID: {thread_id} ``` Always explain that this compatibility skill creates a resumable handoff, not a real transcript import. ## Native Connector These skills work in any agent via CLI. For auto-recall, auto-capture, and graph tools, check if your agent has a native Nowledge Mem connector — run the `check-integration` skill or see https://mem.nowledge.co/docs/integrations