memory-setup
/memory-setup
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.
- Author
- vectorize-io ↗
- Repository
- hindsight ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Steps
- Rules
SKILL.md preview
--- name: memory-setup description: 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" uses `grok-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's `grok-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 1. 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. 2. 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. 3. If this Bot's bank does not exist, call `create_bank` with its `bank_id` and a `name` of "Grok Bot: <Bot name>". 4. If `grok-bot::shared` does not exist, call `create_bank` with `name` "Grok Bot: shared". 5. Call `list_mental_models` on `grok-bot::shared`. If there is no mental model named "About the user", call `create_mental_model` on 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". 6. Tell the user which banks exist and which other banks you can read. ## Rules - Never call `delete_bank`, `clear_memories`, `invalidate_memory`, `delete_document` or `delete_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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · vectorize-io/hindsight | 100 | MIT |
| uhstray-io/huhhb | 100 | MIT |
| LeoYeAI/openclaw-master-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 575d53b1e059 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100memory-context
Load relevant long-term memory from Hindsight before starting work. Use at the start of every task or request, before planning or answering, and whenever the user mentions people, projects, decisions, preferences or anything done before. - 100tanstack-ai-memory-hindsight
Use when wiring hindsight() from @tanstack/ai-memory/hindsight — a hosted memory adapter that buckets memory per conversation and exposes retain/recall/reflect tools to the model. Requires the optional @vectorize-io/hindsight-client peer. - 90hindsight-coding-agent
How this machine's Hindsight coding-agent memory works — the plugin behind the 🧠 banner. Use when the user says "store/remember this in hindsight", asks what the memory/knowledge pages are, wants to configure per-repo memory (disable, rename banks, git depth), or something… - 100hindsight-memory
Interact with and integrate Hindsight long-term AI memory in Claude Code via the `hindsight` CLI. Use for recalling past context, reflecting over a memory bank, retaining facts/decisions, managing banks/entities/mental-models, and understanding the auto-recall/auto-retain hooks… - 100memory-upgrade
Coaches the user on using memory well on their harness, then connects an optional memory service, Mem0 or Hindsight, on top of the built-in markdown memory. Use when the user says "how do I use memory", "does it remember", "upgrade my memory", "connect Mem0", "connect… - 86memory-bridge
Retain, recall, or reflect through the optional Hindsight and Jev memory bridge. Use when explicitly requesting these memory actions through that bridge.