Memory Setup
Set up and check Hindsight long-term memory for this Bot.
by vectorize-io · MIT
The skill
Set up and check Hindsight long-term memory for this Bot. Use the first time a Bot uses Hindsight, when the user asks to connect or check memory, or whenever a Hindsight tool call fails.
Set up Hindsight memory
Hindsight stores memory in banks. This plugin uses three kinds:
- This Bot's bank,
grok-bot::<bot-name>: what this Bot learns in its own work. Build<bot-name>from the Bot's name, lowercase, with spaces turned into hyphens (a Bot named "Sales Researcher" usesgrok-bot::sales-researcher). When you are not a Grok Bot (for example, an agent in Cursor), this bank is per project instead:cursor::<project-name>, from the open workspace folder's name in the same lowercase, hyphenated form. With no workspace open, ask the user what to call it. Never use another Bot'sgrok-bot::bank as your own; those are read-only to you. - The shared bank,
grok-bot::shared: what every Bot on this account should know. - The user's other banks: memory written by the user's other AI tools, such as Claude Code or ChatGPT. Read these when a task touches that work. Never write to them.
Steps
- Call
list_banks. A successful call proves the connection is real. If it fails, tell the user to reconnect Hindsight in the plugin's settings and stop. Do not guess endpoints or hostnames. - If you are a Grok Bot that still has the default name "Grok Bot", ask the user what to call it before going further. The name becomes the bank id, so a default name would give every unnamed Bot the same bank, and renaming later strands its memory under the old id.
- If this Bot's bank does not exist, call
create_bankwith itsbank_idand anameof "Grok Bot: <Bot name>". - If
grok-bot::shareddoes not exist, callcreate_bankwithname"Grok Bot: shared". - Call
list_mental_modelsongrok-bot::shared. If there is no mental model named "About the user", callcreate_mental_modelon that bank with that name and the source query "Who is this user: their work, current projects, the people they mention most, and their stated preferences". - Tell the user which banks exist and which other banks you can read.
Rules
- Never call
delete_bank,clear_memories,invalidate_memory,delete_documentordelete_mental_model. If something should be deleted, tell the user and let them do it. - Never store passwords, one-time codes, API keys, card or account numbers.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: vectorize-io/memory-setup-4917909289.
Details
- Publisher
- vectorize-io
- Category
- AI & Agents › Memory & context
- License
- MIT
- Updated
- 2026-10-19
References
More from vectorize-io
- Code Review Review changed code against project standards.
- Figure Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub READM…
- Hs Release Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR.
- Ship It Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix,…