Menü
Root-owned persistent memory through the compact six-tool thoth-mem MCP surface.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | thoth-mem |
| description | Root-owned persistent memory through the compact six-tool thoth-mem MCP surface. |
Use exactly mem_recall, mem_save, mem_context, mem_get, mem_project, and mem_session. Do not invent a seventh or harness-specific memory tool.
The root/orchestrator owns session lifecycle, prompt capture, and continuity summaries. Subagents must not own or finalize the root session and must not save prompts. Save only real root-user intent; generated prompts must not be saved as user intent. Exclude assistant, tool, subagent, handoff, and scaffolding traffic, and remove content inside <private> tags before persistence.
Use stable session_id and project identity. Recall with mem_recall(mode="compact"), then mem_recall(mode="context"), and use mem_get only for selected records. Use mem_context for bounded recent continuity and mem_project for project navigation.
Capability states are supported, degraded, and unsupported. Advance lifecycle state only after confirmed MCP success. Compaction is explicit and retry-safe: checkpoint only for a verified root compaction event. Finalization is explicit and retry-safe: summarize only for a verified root terminal event. Failures remain eligible for retry.
A duplicate event is suppressed by stable event identity. Distinct intentional events remain separate effects, while byte-identical same-session prompts inside the existing 30-second window may resolve to one canonical prompt row. Manual recovery stays visible for every degraded or unsupported capability, without disabling unrelated supported operations.
Use thoth-mem whenever an agent needs persistent project memory: resume prior work, recall or save durable lessons, preserve root session continuity, handle compaction or finalization, or recover truthfully when semantic memory is degraded. Do not use it for generic SQLite work, setup, sync, migration, dashboard, or HTTP administration unless the task specifically concerns agent memory behavior.
Use thoth-mem whenever an agent needs persistent project memory: resume prior work, recall or save durable lessons, preserve root session continuity, handle compaction or finalization, or recover truthfully when semantic memory is degraded. Do not use it for generic SQLite work, setup, sync, migration, dashboard, or HTTP administration unless the task specifically concerns agent memory behavior.
Expert guidance for SQLite database with better-sqlite3 Node.js driver including database setup, queries, transactions, migrations, performance optimization, and integration with TypeScript. Use this when working with embedded databases, better-sqlite3 driver, or SQLite operations.
