rekal-dev
UserYour coding agent starts every session blank. Rekal is the memory your team is missing
Categories
Indexed Skills (4)
rekal
Use in a repo with Rekal initialized (.rekal/ exists). 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.
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.
init
Turn on Rekal memory in the current repository by running `rekal init`. Use when the user asks to initialize or set up Rekal here, or when a `rekal` command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a `.rekal/` store — most repos do not want one.
install
Install the Rekal binary on this machine. Use when `rekal` is not on PATH — a command reported `command not found` — or when the user asks to install Rekal. Once per machine, not per repository; to set up a repo that already has the binary, use the init skill instead.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.