Update to XMemo

{
  "description": "Distill a session into concise decisions, durable context, actions, and resumable state for XMemo. Use when extracting outcomes or saving important session results; a summary-only request does not authorize persistence.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 441
    }
  ],
  "name": "xmemo-distill-session",
  "skill_md_contents": "---\nname: xmemo-distill-session\ndescription: Distill a session into concise decisions, durable context, actions, and resumable state for XMemo. Use when extracting outcomes or saving important session results; a summary-only request does not authorize persistence.\n---\n\n# Distill a Session to XMemo\n\nPreserve what remains useful after the conversation disappears. Follow\n**collect → classify → deduplicate → preview → write → receipt**.\n\n## 1. Identify the durable boundary\n\nDetermine the subject, project or scope, and whether the user wants a summary,\na durable save, or both. Do not infer consent for sensitive or ambiguous\nwrites.\n\n## 2. Extract outcomes, not chronology\n\nClassify:\n\n- final decisions and material rationale;\n- stable preferences, rules, constraints, and definitions;\n- verified facts, procedures, fixes, and lessons;\n- concrete commitments and follow-up actions;\n- unresolved questions, choices, or blockers;\n- current verified state and exact next action.\n\nExclude raw transcripts, repeated explanations, long logs, large code blocks,\ncredentials, private traces, and speculative ideas that were not accepted.\n\n## 3. Deduplicate and preview\n\nUse `search_memory` or `recall_context` when duplicate or superseding content is\nplausible. Prefer `update_memory` for a changed concept and `remember` for a\ngenuinely new durable concept.\n\nWhen classification, replacement, or project placement is unresolved, preview\nthe affected candidates and clarify that scope. An explicit request to save a\nclear batch already authorizes it. Label tentative and verified items separately.\n\n## 4. Route confirmed outcomes\n\n- new durable concept → `remember`;\n- corrected durable concept → `update_memory`;\n- concrete action → `todo`;\n- unresolved blocker or unfinished state → `update_state`;\n- significant milestone or handoff → `record_event`.\n\nUse only routes supported by actual outcomes. Return saved, updated,\ncheckpointed, skipped, and unresolved counts plus the exact next action. Read\n`../xmemo-memory-steward/references/workflows.md`,\n`../xmemo-memory-steward/references/memory-policy.md`, and\n`../xmemo-memory-steward/references/tool-routing.md` for details.\n\n## Shared boundaries\n\nBefore any tool call, read and apply\n[plugin boundaries](../xmemo-memory-steward/references/plugin-boundaries.md).\nUse [tool routing](../xmemo-memory-steward/references/tool-routing.md) for unfamiliar\noperations, [temporal queries](../xmemo-memory-steward/references/temporal-queries.md)\nfor dates or chronology, and [memory policy](../xmemo-memory-steward/references/memory-policy.md)\nbefore writes. Reuse existing authorization; clarify only unresolved scope.\nReport failed or unconfirmed operations without claiming success.\n"
}