본문으로 건너뛰기
cccskills
무료GitHub에 공개

memory-setup

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.

설치 방법 보기

이럴 때 유용합니다

  • Setting up Hindsight for a Bot’s first use
  • Checking the connection after a memory tool fails
  • Separating project memories from shared knowledge
  • Checking which other memory stores can be read

포함된 파일(1)

  • SKILL.md2.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Handing unfinished work to another Bot
  • Resuming a task started by another Bot
  • Sharing findings with Bots outside the current conversation
vectorize-io/hindsight5.1만2026년 10월 17일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing changes after implementation
  • Finding missing tests and unused code
  • Checking Python types and API design
vectorize-io/hindsight5.1만2026년 10월 17일 업데이트

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 a specialized agent that remembers across sessions
  • Build an agent from prepared reference documents
  • Start an empty agent and add knowledge over time
vectorize-io/hindsight5.1만2026년 10월 17일 업데이트

figure

무료

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Explaining request and data flows
  • Illustrating how a background job works
  • Showing feature changes in a pull request
vectorize-io/hindsight5.1만2026년 10월 17일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Plan memory that carries conversation context across sessions
  • Design tags that separate each user's memories
  • Plan summaries of customer preferences and recurring issues
vectorize-io/hindsight5.1만2026년 10월 17일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Save project coding and testing conventions
  • Share failure causes, fixes, and workarounds
  • Retrieve related lessons before starting a task
vectorize-io/hindsight5.1만2026년 10월 17일 업데이트

vectorize-io의 스킬 모두 보기

이 스킬의 문제 신고