status

name	status
description	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.

tm — status

Read-only health report for the turing-mem setup. It writes nothing itself; the one action it may propose is the confirm-gated doc refresh for STALE_DOCS below.

Steps

1. Run:

   ${CLAUDE_PLUGIN_ROOT}/scripts/tm-status.sh "$PWD"
   

   It prints the guard's KEY=VALUE block (TM_STATUS, MEMORY_DIR, PROJECT_ID, PROJECT_PATH, PROJECT_EXISTS, OVERRIDE, STORE_VERSION, PLUGIN_STORE_VERSION, plus KEY_MISMATCH=true when flagged) followed by CONFIG_FILE and, when resolvable, GLOBAL_NOTES, PROJECT_COUNT, STORE_GIT (own-repo | nested | none), STORE_DIRTY, STALE_DOCS (+ STALE_DOC_LIST when non-zero — plugin-owned store docs older than the plugin's current copies), PROJECT_NOTES, PROJECT_LOGS, UNCONSOLIDATED_LOGS, LAST_CONSOLIDATED, LAST_CHECKPOINT (newest log stamp, UTC).

2. Present a short report (5-10 lines, no tables needed):

   • Health: TM_STATUS in one word, plus store version vs plugin pin.
   • Store: MEMORY_DIR, global note count, project count, git state (own-repo / nested / none; note uncommitted changes when STORE_DIRTY=true).
   • Project: id, path, whether an override is active, key mismatch if flagged.
   • Activity: project notes, log checkpoints, unconsolidated count, last consolidated, last checkpoint — call out capture staleness when LAST_CHECKPOINT is never or its date is more than ~a week old on an active project.

3. If anything is unhealthy, end with the single matching repair verb:

   • TM_STATUS=NEED_INIT or NEED_ADOPT → /tm:init
   • NEED_MIGRATE / READ_ONLY → store/plugin version mismatch; explain which side is older
   • PROJECT_EXISTS=false → /tm:init (create) or /tm:link (attach to an existing folder)
   • KEY_MISMATCH=true → /tm:link
   • UNCONSOLIDATED_LOGS ≥ 10 → suggest /tm:consolidate
   • STORE_DIRTY=true → remind that memory changes are uncommitted (own-repo: commit/push; nested: the parent repo's sync workflow)
   • STALE_DOCS > 0 → the store's references//AGENTS.md/CLAUDE.md predate the current plugin; offer to refresh them (list the files, confirm via AskUserQuestion, then run ${CLAUDE_PLUGIN_ROOT}/scripts/tm-scaffold.sh refresh <MEMORY_DIR> — it overwrites only plugin-owned docs, never notes/logs/MEMORY.md/indexes)

Codex fallback

Same script, installed at ~/.agents/skills/scripts/tm-status.sh; present the same report in plain text.