Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

status

Sterne0

Forks0

Aktualisiert8. Juli 2026 um 13:28

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.

Installation

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.

In Manus ausführen

Quelle

Lucklyric

Lucklyric/turing-mem

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

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

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).
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.
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.

Mehr aus diesem Repository

gleiches Repository

server

Lucklyric/turing-mem

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.

2026-07-150

checkup

Lucklyric/turing-mem

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.

2026-07-130

init

Lucklyric/turing-mem

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.

2026-07-130

link

Lucklyric/turing-mem

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.

2026-07-130

rename

Lucklyric/turing-mem

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.

2026-07-080

consolidate

Lucklyric/turing-mem

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.

2026-07-070

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

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).
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.
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.