This skill should be used when the user asks to "start the memory server", "open the memory browser", "visualize my memory", "stop the tm server", "is the memory server running", or invokes /tm:server [start|stop|status]. Manages a local read-only HTTP browser for the whole store - global and project memory, paginated lists, keyword search - at http://127.0.0.1:<port>/. Starting is confirmed with the port and store path; stop and status act on a clear ask.
This skill should be used when the user asks to "run a memory checkup", "check up on my memory", "take care of my memory", "tidy up memory", "do whatever memory needs", "what should memory do next", or invokes /tm:checkup. Auto triage across the whole turing-mem surface - one status read, then a priority ladder picks the single best next action (repair, link, doc refresh, consolidate, checkpoint, commit reminder) and dispatches the matching verb. When the project is unresolved it searches the store for candidate folders and presents concrete choices. Every action goes through that verb's own confirm gates; nothing is decided silently.
This skill should be used when the user asks to "set up turing-mem", "initialize the memory store", "init tm", "repair the memory store", accepts an offer to set up after a guard reports a non-OK status, or invokes /tm:init. Creates config.json and the memory dir, adopts an existing store, scaffolds the current project folder, and walks the bootstrap repair flow. Every significant step is confirmed with the user before acting — nothing is created without explicit approval.
This skill should be used when the user asks to "link this folder/project to a memory project", "map this directory to project X", "pin this repo to existing memory", accepts a KEY_MISMATCH repair, or invokes /tm:link [id|path]. Forces the current directory to map to an existing turing-mem project folder by writing project_overrides in config.json — cross-host linking for no-remote projects. The mapping is always confirmed before writing.
This skill should be used when the user asks to "rename the project memory folder", "change the memory folder name", "rename project X in memory", "give this project's memory a different name", or invokes /tm:rename [new-name]. Renames a project's store folder prefix — the -8hex identity suffix is always preserved, so resolution keeps working from every clone and host. Updates the global index row and any config overrides pointing at the folder. The rename is always confirmed before anything moves.
This skill should be used when the user asks to "check turing-mem status", "tm status", "memory status", "is my memory store healthy", "tm health", or invokes /tm:status. Read-only health report — config, store version, project resolution, note and checkpoint counts, consolidation state — with the matching repair verb for anything unhealthy.
This skill should be used when the user asks to "consolidate memory", "merge the log checkpoints", "run consolidation", invokes /tm:consolidate, or accepts the SessionStart nudge reporting unconsolidated log checkpoints. Dispatches the tm-archivist agent to merge project log/ checkpoints into durable notes and MEMORY.md, refresh the index, and prune consolidated logs.
This skill should be used after a meaningful step worth persisting — a decision, a root cause, a non-obvious fix, an environment fact, or a user correction or preference — and when the user says "remember this", "save this to memory", "note this for later", or "make this durable". Appends a project log checkpoint by default; with an explicit gist it writes a durable note plus index row after one confirmation.