ai-brain
Skill417 starsChanged 3 months agoMITView on GitHub
Give Claude a permanent, searchable long-term memory using an Obsidian vault as the store. At the end of a session, summarize what mattered and save it as a Markdown note in your "AI Brain" vault; at the start of a session (or on demand), read back only the relevant past notes. Local markdown you own — connected via the Filesystem MCP. Trigger with "wrap up", "save this session", or "remember this".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- chanjalme/claude-skillstheir own version, first seen Jun 24, 2026
- Evobaso-J/ai-brain-templatetheir own version, first seen Apr 24, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Evobaso-J/ai-brain-template★ 4same name
- chanjalme/claude-skills★ 0same 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 repository54 other files it gives its agents.
- ab-hook-testerSkill
- agent-reachSkill
- analytics-readoutSkill
- audience-personasSkill
- best-time-schedulerSkill
- bio-profile-optimizerSkill
- b-roll-shot-listSkill
- campaign-briefSkill
- caption-and-hashtagsSkill
- carousel-builderSkill
- collab-outreachSkill
- comment-miningSkill
- comment-responderSkill
- community-engagement-planSkill
- competitor-positioningSkill
- competitor-teardownSkill
- content-auditSkill
- content-calendarSkill
- content-factorySkill
- content-pillar-builderSkill
- content-repurposerSkill
- content-researchSkill
- cover-thumbnail-briefSkill
- creator-outreachSkill
- cross-platform-distributionSkill
- cross-platform-reformatterSkill
- cta-writerSkill
- dm-script-writerSkill
- going-viralSkill
- hashtag-keyword-researchSkill
- hook-miningSkill
- humanizerSkill
- influencer-partnershipsSkill
- launch-retrospectiveSkill
- linkedin-thought-leadershipSkill
- on-screen-text-writerSkill
- paid-social-briefSkill
- positioning-auditSkill
- profile-conversion-auditSkill
- reel-analyzerSkill
- reel-builderSkill
- reel-scripterSkill
- series-plannerSkill
- social-analytics-reportSkill
- social-listeningSkill
- social-proof-miningSkill
- story-sequencerSkill
- trend-spotterSkill
- ugc-creator-briefSkill
- utm-campaign-planSkill
- viral-carouselSkill
- viral-hook-writerSkill
- viralitySkill
- x-thread-strategySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 51
Keep it tight and skimmable — this is for future retrieval, not prose.
- Very specific: line 57
Link it in: Add a one-line pointer to a AI Brain/MOC.md index (a map-of-content): - [[<YYYY-MM-DD>-<slug>]] — <one-line hook> so the brain …
- Very specific: line 64
Before answering anything that depends on history ("what did we decide about X", "continue the project", "pick up where we left off"), …
- Distinctive: line 77
Never invent memories. If the vault has no answer, say "not in memory yet."
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
AI Brain — persistent memory for Claude via Obsidian
You maintain a long-term memory for the user in an Obsidian vault — a folder of Markdown notes the
user owns on disk. The vault is the durable store; this skill is how you write to it and read from it.
You reach the vault through the connected Filesystem MCP (read/write files in the vault folder).
Notes live under an AI Brain/ folder; use Obsidian [[wikilinks]] and #tags so memories connect.
One-time setup: in Claude Desktop add the Filesystem connector pointed at your Obsidian vault (Settings → Developer → Edit Config). No browser automation, no login — it's just your local notes.
When the user says "wrap up" / "save this session" / "remember this" — SAVE
- Review the whole conversation. Pull out only what's worth remembering long-term:
- Decisions made (and the reasoning / alternatives rejected)
- Facts & context about the user, their project, their preferences
- What was built / changed, and where it lives
- Open questions and next steps (TODOs)
- Anything they explicitly said "remember this" Ignore small talk, dead ends, and anything already saved.
- Write a structured Markdown note in this exact shape (Obsidian-friendly tags + links):
Keep it tight and skimmable — this is for future retrieval, not prose.# Session — <YYYY-MM-DD> — <3–6 word title> #ai-brain #<topic> #<topic> Related:: [[<other note>]], [[<project>]] ## Decisions - <decision> — <why> ## Context / facts to remember - <fact> ## Built / changed - <what> (<where>) ## Open / next - [ ] <todo> - Save it to the vault via the Filesystem MCP: write the note to
AI Brain/<YYYY-MM-DD>-<slug>.md. If theAI Brain/folder doesn't exist yet, create it first. Append-only — never overwrite a past session's note. - Link it in. Add a one-line pointer to a
AI Brain/MOC.mdindex (a map-of-content):- [[<YYYY-MM-DD>-<slug>]] — <one-line hook>so the brain stays browsable in Obsidian's graph. - Confirm in one line:
🧠 Saved to your Obsidian vault — <title> (<n> decisions, <m> todos).
At session start, or when the user references the past — RECALL
- Before answering anything that depends on history ("what did we decide about X", "continue the
project", "pick up where we left off"), search the vault: read
AI Brain/MOC.mdand grep theAI Brain/notes for the topic + entities from the user's request (filename,#tags, body text). - Open only the relevant notes — never load the whole vault. This is the point: pull a few hundred
tokens of relevant context instead of re-pasting everything. Follow
[[wikilinks]]to related notes. - Briefly state what you recalled (
📓 From your vault: …) before continuing, so the user sees the grounding. If nothing relevant is found, say so and proceed fresh.
Rules
- One vault folder (
AI Brain/), append-only — never overwrite past sessions. - Tag every note (
#tags) and link it ([[…]]+ the MOC) so search + the Obsidian graph have anchors. - Recall is retrieval, not reload: fetch the minimum relevant notes. That's what keeps token cost low on long-running projects.
- Never invent memories. If the vault has no answer, say "not in memory yet."
- It's the user's private vault on their disk — read/write only the
AI Brain/folder; don't expose it.
Built by Ootto — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →
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.

