← GoodMemCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to GoodMem
Snapshot Sep 30, 2026 · 23:09 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "save-conversation",
"description": "Save a useful conversation to GoodMem as self-contained question-and-answer pairs, including documents shared in the conversation. Use only when the user asks to save, remember, or keep the discussion.",
"included_files": [],
"skill_md_contents": "---\nname: save-conversation\ndescription: Save a useful conversation to GoodMem as self-contained question-and-answer pairs, including documents shared in the conversation. Use only when the user asks to save, remember, or keep the discussion.\n---\n\n# Save a conversation\n\nSave only when the user asks. Capture durable decisions, facts, and conclusions;\nomit greetings, clarifying one-liners, and tool-call chatter.\n\n## Choose the space\n\nCall `goodmem_spaces_list` first. Reuse an obviously matching space or create one\nnamed for the topic, not the date. If the user supplies a name, use it exactly.\nTell the user which space you chose. Keep using that space if they save more of\nthe same session later.\n\nIf no embedder is configured, follow the Quick Start steps in\n`using-goodmem-memory`. After setup, list spaces again and reuse a suitable space\nbefore creating another.\n\n## Save self-contained exchanges\n\nCreate one memory per useful exchange with both sides present:\n\n```text\nQ: What did we decide about the vendor contract?\nA: We chose Cooperativa San Rafael at 6.80 USD/kg, quarterly shipments,\n pending legal review of the termination clause.\n```\n\nCall `goodmem_memories_create` once per pair with metadata such as\n`{\"type\":\"qa_pair\",\"topic\":\"vendor contract\"}`. Never save a bare answer that\nwill lose its meaning outside the current chat.\n\n## Include shared documents\n\nA document discussed in the saved conversation is part of what the user asked to\nkeep. Follow `work-with-documents` to upload each original attachment as one\nmemory with `goodmem_memories_upload`; do not transcribe it into per-page text\nmemories. Use metadata connecting it to the conversation, and name the document\nin the related Q&A answer so later retrieval connects them. Use text creates for\npasted text or explicitly requested excerpts.\n\nIf a file cannot be uploaded or GoodMem reports a processing failure, explain\nthe problem while preserving the useful discussion. Do not silently replace the\noriginal with a transcription or claim that an unsaved file was retained.\n\n## Confirm the result\n\nReport the space name, number of Q&A pairs, and documents saved. If processing is\nstill underway, distinguish \"saved\" from \"searchable\" and follow the processing\nrules in `using-goodmem-memory`.\n\nConfirm the specific memory before deletion. Never bulk-delete unless the user\nexplicitly covers the whole set.\n"
}SHA-256: cfce16014b6250b17f18bf5ae0cedc0e6140c920e397652d78a0f698e295e9c8