Check a Bot’s connection to Hindsight and set up dedicated and shared memory stores. The skill also creates a user knowledge summary when needed and reports which other memory stores are available to read.
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.
Review the instructions the agent will receive before you install.
Hindsight stores memory in banks. This plugin uses three kinds:
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.grok-bot::shared: what every Bot on this account should know.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.create_bank with its bank_id and a name of "Grok Bot: <Bot name>".grok-bot::shared does not exist, call create_bank with name "Grok Bot: shared".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".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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record task handoffs between Bots in shared Hindsight memory, including progress, remaining work, sources, and caveats. Other Bots can retrieve the record later, continue unfinished work, and report the outcome back through shared memory.
Review changed code against project rules and report missing tests, unused code, typing problems, and style violations. It also checks API design and data isolation, helping developers identify issues after implementation.
Create a specialized Claude Code subagent with Hindsight long-term memory. Start with an empty agent or import prepared documents, then equip it with knowledge pages and memory search to reuse information across sessions.
Create an animated diagram showing request flows, background jobs, or feature changes. The result is a single SVG image for README files, pull requests, issues, or blog posts, with support for light and dark themes.
Plan how an AI application should use Hindsight memory. Identify useful information to retain, define user-scoping tags and memory bank settings, and specify how retrieved facts and synthesized knowledge should reach the model.
Store project conventions, task outcomes, and troubleshooting lessons in a shared Hindsight Cloud memory bank. Retrieve relevant context before new work, or synthesize past experience to guide decisions and help teammates reuse what has been learned.