brain-save
Skill1 starsChanged 5 months agoMITView on GitHub
Save an insight or knowledge from the current conversation into the brain. Lighter version of /brain-add designed for in-context capture.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jeremylongshore/bobs-big-brain-plugintheir own version, first seen Jul 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jeremylongshore/bobs-big-brain-plugin★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- brain-addSkill
- brain-add-videoSkill
- brain-checkSkill
- brain-digestSkill
- brain-processSkill
- brain-searchSkill
- client-onboardSkill
- consulting-deckSkill
- good-morningSkill
- harvestSkill
- logSkill
- taskSkill
- weekly-reviewSkill
- wrap-sessionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 12 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
By Claude: When the CARL brain-capture rule fires and user approves a suggested save
- Distinctive: line 24
If argument provided: use it as the core content/description
- Distinctive: line 25
If no argument: review the recent conversation context and identify the most brain-worthy insight, learning, or reference discussed
- Distinctive: line 26
If invoked after a brain-capture suggestion, save the specific item suggested
- Distinctive: line 40
Add 3-5 inline [[wiki-links]] for key concepts
- Distinctive: line 41
Keep it focused — one insight per note.
- Distinctive: line 45
Check for duplicates first — if similar note exists, suggest updating it instead
- Very specific: line 49
Add to related: if strong matches found
- Very specific: line 53
Add new entry in the appropriate category section: - [[note-name]](category/subcategory/note-name.md) — One-line summary.
- Distinctive: line 54
Update the note count in the header and the section header count
- Distinctive: line 55
Update "Last updated: YYYY-MM-DD"
- Distinctive: line 58
Use Bash to append directly without reading:
- Distinctive: line 74
Keep notes atomic — one concept per note.
- Distinctive: line 75
Write the note as standalone knowledge, not as "during our conversation we discussed..." — strip conversation context.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/brain-save [description]
Capture knowledge from the current conversation and file it in the brain.
When this is invoked
- By user:
/brain-saveor/brain-save "description of what to save" - By Claude: When the CARL brain-capture rule fires and user approves a suggested save
Steps
- Read
brain-config.mdfor taxonomy and filing rules. - Identify what to save:
- If argument provided: use it as the core content/description
- If no argument: review the recent conversation context and identify the most brain-worthy insight, learning, or reference discussed
- If invoked after a brain-capture suggestion, save the specific item suggested
- Determine note type and category:
- Insight/opinion →
note - Factual information →
reference - How-to discovered in conversation →
guideorprocess - Idea sparked →
idea - Cross-referenced answer synthesizing multiple brain notes →
synthesis(usesource: "brain-query", list consulted notes inrelated:) - Match against filing signals for category/subcategory
- Insight/opinion →
- Create a concise, well-structured note:
- YAML frontmatter with
source: "conversation"and today's date - Body: distill the insight into clear, standalone prose (not conversation transcript)
- The note should make sense to someone reading it weeks later without conversation context
- Add 3-5 inline [[wiki-links]] for key concepts
- Keep it focused — one insight per note. If multiple things to save, create multiple notes.
- YAML frontmatter with
- File the note:
- Path:
brain/{category}/{subcategory}/{kebab-case-title}.md - Check for duplicates first — if similar note exists, suggest updating it instead
- Path:
- Quick connection check:
- Grep for shared tags/topics in existing notes
- Add to
related:if strong matches found
- Update index.md:
- Read
brain/index.md - Add new entry in the appropriate category section:
- [[note-name]](category/subcategory/note-name.md) — One-line summary. Tags: tag1, tag2 - Update the note count in the header and the section header count
- Update "Last updated: YYYY-MM-DD"
- Read
- Append to log.md (do NOT read the file — append only):
- Use Bash to append directly without reading:
echo '## [YYYY-MM-DD] ingest | {note-title} Filed to: {category}/{subcategory}. Source: conversation. {X} wiki-links created. ' >> brain/meta/log.md
- Use Bash to append directly without reading:
- Confirm:
🧠 Saved to brain/{category}/{subcategory}/{filename}.md Tags: #tag1 #tag2
Important
- This skill can be invoked by Claude (disable-model-invocation: false) when the brain-capture CARL rule suggests a save and the user confirms.
- Keep notes atomic — one concept per note. Suggest multiple /brain-save calls if there are several things to capture.
- Write the note as standalone knowledge, not as "during our conversation we discussed..." — strip conversation context.
- Be brief. A brain-save note should be 3-15 lines of body content typically.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

