
save-thread
Deprecated compatibility skill. In generic npx skills environments this must degrade honestly to a resumable handoff, because real transcript-backed thread import is not guaranteed. Prefer save-handoff here, and use native connectors when you need actual session capture.
- Installs
- 692
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/nowledge-co/community --skill save-thread- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads save-thread automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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 skillsenvironment - 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:
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
FAQ
What does the save-thread skill do?
Deprecated compatibility skill. In generic npx skills environments this must degrade honestly to a resumable handoff, because real transcript-backed thread import is not guaranteed. Prefer save-handoff here, and use native connectors when you need actual session capture.
How do I install save-thread?
Run npx skills add https://github.com/nowledge-co/community --skill save-thread in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/save-thread/ (personal) or .claude/skills/save-thread/ (project).
Which AI agents can use save-thread?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is save-thread safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains save-thread?
It is published by nowledge-co in nowledge-co/community. It has 692 recorded installs.
More from nowledge-co/community
read-working-memory
nowledge-co/community
Read your daily Working Memory briefing to understand current context. Contains active focus areas, priorities, unresolved flags, and recent knowledge changes. Load this automatically at the beginning of sessions for cross-tool continuity.
distill-memory
nowledge-co/community
Capture breakthrough moments and valuable insights as searchable memories in your knowledge base.
search-memory
nowledge-co/community
Search Nowledge Mem memories and prior threads for past decisions, procedures, and context with normal, deep, or progressive retrieval; automatically show a focused graph of successful Memory results.
save-handoff
nowledge-co/community
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.