/tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit)
$ npx -y skills add LH8PPL/core-memory-kit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/tour
Context preview
What this command does when you run it.
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit)
Command definition
tour.mddescription: Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit) allowed-tools: Bash(cmk tour *), Bash(cmk tour)
Run `cmk tour` and present its output to the user conversationally.
Rules:
- Run the command; do NOT invent or embellish what the memory contains — the
tour reads the user's real files, and your narration must stay faithful to its output (the kit's no-fabrication contract).
- Keep the presentation scannable: the tier table, what's captured (with the
real examples the tour shows), how recall works, next steps.
- If the tour reports nothing captured yet, say so plainly and point at the
ways it fills (automatic capture, "remember this", `cmk import-sessions`).
- `cmk doctor` is the health check; the tour is the explainer — if the user
asks "is it working?", suggest doctor.
Persistent per-project memory for Claude Code, Kiro, Cursor & Codex - plain markdown committed with your code, captured prompt-free, auto-injected at session start, recalled by meaning (local semantic search, zero API). Cross-project persona, cited recall, searchable session history.
Repo: LH8PPL/core-memory-kit