conversation-to-memory

Extracts high-value facts from session transcripts into compressed long-term memory entries.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill conversation-to-memory-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conversation-to-memory
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/extended/meta/conversation-to-memory
Command: npx skills add https://github.com/yakeworld/Synthos --skill conversation-to-memory-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running AI sessions accumulate valuable user preferences, environment details, and workflow patterns, but writing everything to memory causes bloat while writing nothing loses hard-won context. This Skill filters session transcripts through a three-question test (growth direction, framework dimension, fermentation potential) so only durable, high-signal facts are persisted within a strict 2,200-character budget. ## Core Features & Use Cases - Three-Question Filtering: Each candidate memory must answer whether it supports system growth, maps to a framework dimension, and has fermentation potential before being saved. - Constitutional Guardrails: Memories that conflict with immutable CONSTITUTION clauses are rejected, and imperative phrasing ("Always use X") is rewritten as declarative facts ("User prefers X"). - Atomic Capacity Management: Updates execute in remove→replace→add order with all-or-nothing semantics, and usage above 80% triggers proactive cleanup to land in the 60-75% target range. - Use Case: After a 12-tool-call session that completes a literature deduplication pipeline, the Skill removes one outdated path entry, adds two annotated entries about the new path and sorting preference, and reports memory usage dropping from 82% to 71%. ## Quick Start Review this session transcript and my current memory, then save only the entries that pass the three-question filter while keeping usage under 75%.

Frequently Asked Questions about conversation-to-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save session context to long-term AI memory without bloat?

Filter each candidate fact through three questions: does it support a growth direction, map to a framework dimension, and have fermentation potential. Facts that fail all three are deprioritized, and completed-task noise like merged PRs is left to session search instead of memory.

What information should be stored in AI agent memory?

Store user preferences and corrections, environment details like paths and ports, and durable workflow methods. Avoid completed tasks, temporary states, and anything retrievable via session search, since those become noise after seven days.

How do I manage memory capacity limits in an AI assistant?

Keep usage in a 60-75% target range of the character budget. When usage exceeds 80%, proactively delete low-priority entries ordered by value: user preferences first, then environment details, then methods, then stale project status.

Why should memory entries be declarative instead of imperative?

Imperative phrasing like "Always use X" gets misinterpreted as a hard rule by the agent in future sessions. Declarative statements like "User prefers X" record facts without overriding higher-priority instructions or constitutional constraints.

What happens when a memory update batch fails?

Updates follow an all-or-nothing policy executed in remove, replace, then add order. If any entry fails validation, such as imperative tone or capacity overflow, the entire batch is rejected and must be cleaned up and resubmitted.