# Save Thread

> Synthesize and save the current conversation as a thread note in OpenAugi/Threads/. Use when this capability is needed.

- Skill: `tomevault-io/save-thread` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/save-thread`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/save-thread/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/save-thread

---


# Save Thread

Synthesize the current conversation and write it to OpenAugi via `write_thread`.

## What to capture

Not the transcript — the signal:

- **What was the intent?** The original question or goal behind the conversation
- **How did thinking evolve?** Key pivots, realizations, or direction changes
- **What was decided?** Choices made, approaches agreed on, things ruled out
- **What was learned?** Concrete discoveries, non-obvious insights
- **What's still open?** Unresolved questions, next steps, things to revisit
- **What was produced?** Any documents written, code created, plans made

## Format

Write `content` as markdown. Use headers and bullets. No fixed schema — structure it to fit the session. A short session might be a few bullets. A long one might have sections.

Example structure (adapt as needed):

```markdown
## Intent
[What the user was trying to figure out or accomplish]

## What happened
[How the conversation evolved — key pivots or realizations]

## Decisions
- [Choice made]

## Learned
- [Non-obvious thing discovered]

## Open
- [Unresolved question or next step]

## Produced
- [Title of any document or artifact created]
```

## Steps

1. Re-read the conversation to identify intent, evolution, decisions, and output
2. Write a one-line `description` (goes in frontmatter — make it scannable)
3. Choose a short `topic` that names the session (e.g. "write-back MCP tools design")
4. Call `write_thread` with topic, description, and content
5. Confirm the path written

---
> Source: [bitsofchris/openaugi](https://github.com/bitsofchris/openaugi) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-24 -->

