← ClaudeAtlas

shellbrainlisted

Use when an agent should remember to ask Shellbrain for targeted recall at task start, subproblem changes, repeated failures, hypothesis changes, or closeout.
cucupac/shellbrain · ★ 11 · AI & Automation · score 67
Install: claude install-skill cucupac/shellbrain
# Shellbrain Recall Workflow ## Purpose Shellbrain is a persistent memory system for agent work. As the working agent, your interface is: ```bash shellbrain recall ``` Recall returns a compact brief synthesized from prior memories, concepts, scenarios, and recent episode context. It is meant to reduce wasted exploration and help you decide where to look next. When the user explicitly asks you to store or teach Shellbrain something, use: ```bash shellbrain teach ``` Teach stores the user-provided statement as evidence and immediately asks Shellbrain's teach agent to turn it into durable memories or concept graph updates. If you changed any files since your last user-facing response, run this exactly once after validation and immediately before your next user-facing response: ```bash shellbrain snapshot ``` Snapshot stores exact repo code state in repo-local shadow Git so the knowledge builder can later attach exact solution deltas to solved problem runs. Do not call Shellbrain internal commands directly. `read`, `events`, `memory`, `concept`, and `scenario` are for Shellbrain's internal agents. ## Quick Start Do not run `shellbrain init` at the start of every session. Use this order: 1. If Shellbrain is missing or broken, run `shellbrain admin doctor`. 2. If doctor says repair is needed, run `shellbrain init`. 3. Otherwise, use `shellbrain recall` with a targeted query and `current_problem`. If `shellbrain` is not found, do a one-time PATH check: ```bash zsh