rekal
SolidUse in a repo with Rekal initialized (.rekal/ exists), or when the user asks to set Rekal up. Rekal is memory of prior AI sessions — who changed what, why, and when. Before spending a token, decide WHERE the answer lives: TREE / KNOWLEDGE / LEDGER / MAP. Route to one substrate, act, and stay silent when memory is not the tool. Rekal's commands return compact agent-readable text by default; the judgment is yours.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- rekal-dev
- Repository
- rekal-dev/rekal-cli
- Created
- 5 months ago
- Last Updated
- yesterday
- Language
- Go
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
rekal-setup
Use when the user wants to set up Rekal in a repository, asks what Rekal is, or when a `rekal` command reports it is not installed or not initialized. Rekal is git-backed memory of prior AI sessions — why a change was made, what was tried, what was rejected. This skill only installs it. Once `rekal init` has run, the binary installs the full recall skill and that one takes over.
recall-knowledge
Recall knowledge base entries by meaning, not just keywords — hybrid search (lexical ripgrep + local vector embeddings + see-link graph) over `.claude/knowledge/entries/`. Use when looking for prior knowledge, decisions, pitfalls, or context that may be worded differently from the query (e.g. a Japanese query vs English identifiers, or synonyms the entry does not literally contain). Falls back to ripgrep-only when the vector index or its dependencies are absent. On-demand only — it is NOT wired into the per-prompt hook (that stays ripgrep for instant, model-free injection).
memory-search
Searches the project's recorded memory (core-memory-kit) — decisions, conventions, architecture, the reasoning behind choices, and where things live — and returns a curated, cited summary. Fire whenever the answer might be something the project already established in past work, HOWEVER the question is phrased — any prior decision, convention, rationale, or "how/where/why is it this way" question, including oblique or roundabout asks ("why is everything so spread out?", "remind me what we settled on for X", "how come these files are tiny?"). Also fire when a "[core-memory-kit] Memory available" hint appears on the prompt. The examples are illustrative, not a checklist — prefer recalling over re-deriving an answer from the code. The session-start snapshot is a bounded index; this skill reaches the rest. Skip only when the question is purely about uncommitted or just-edited live code that memory cannot know, concerns this conversation only, or the user asked to ignore memory.