brain
Skill1 starsChanged 32 days agoMITView on GitHub
Orient in the user's big-brain second brain and work brain-aware for the rest of the session. Use when the user types /brain, or asks "what am I working on", "what's on my plate", "catch me up", "what's overdue", or at the start of a session about ongoing work. Loads the vault overview, reports it in one screen, and keeps the vault updated as work happens.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- jonmagic/skillstheir own version, first seen Nov 8, 2026
- keli-wen/agy-stafftheir own version, first seen Nov 8, 2026
- Aiqbee/aiqbee-aitheir own version, first seen Nov 8, 2026
- SeanningTatum/brain-axitheir own version, first seen Nov 1, 2026
- sophonfinance-wq/finance-automation-portfoliotheir own version, first seen Nov 1, 2026
- aidemd-mcp/servertheir own version, first seen Oct 28, 2026
Used with
Projects with it also use research.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- keli-wen/agy-staff★ 828same name
- H-mmer/pentest-agents★ 815same name
- Anantys-oss/koan★ 48same name
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- henriquecaner/brain-agent★ 13same name
- Aiqbee/aiqbee-ai★ 7same name
- jonmagic/skills★ 6same name
- tonydzi/second-brain-starter-kit★ 6same name
- aidemd-mcp/server★ 4same name
- gufranco/claude-engineering-rules★ 3same name
15 more not listed
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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Run big-brain status (or call the brain_overview MCP tool).
- Very specific: line 20
If the vault hasn't been linted recently, run big-brain doctor and surface only warnings.
- Very specific: line 24
Treat it as a project or topic: big-brain show <arg> (falling back to big-brain search <arg>), then summarize where it stands (goal, …
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
brain
The big-brain vault is the user's external memory, shared by all their AI tools. This skill loads it and switches you into brain-aware mode. The vault is whichever one big-brain resolves using the BIG_BRAIN_VAULT env var, a --vault path, or the nearest brain.config.json. Use the big-brain CLI or the big-brain MCP tools; don't hardcode a vault path.
With no argument
- Run
big-brain status(or call thebrain_overviewMCP tool). - Report in one screen, BLUF: active projects with their next task, anything overdue or due this week, inbox count if it's piling up. No filler; skip empty sections.
- If the vault hasn't been linted recently, run
big-brain doctorand surface only warnings.
With an argument
Treat it as a project or topic: big-brain show <arg> (falling back to big-brain search <arg>), then summarize where it stands (goal, status, open tasks, last Log entries) and ask what to work on.
Brain-aware mode (rest of the session)
From here on, keep the vault current as a side effect of the work:
- Decisions, progress, and problems →
big-brain daily --log "..."and a Log line on the affected project. - New commitments → project notes; new action items →
big-brain task add. - Completed work →
big-brain task done <id>. - Facts worth keeping with no obvious home →
big-brain capture "...".
Do routine captures/logs without asking (mention them in one line); ask before rewriting or archiving existing notes. If the vault has git auto-commit enabled, these saves also commit and push on their own. At the end of a work session, make sure what happened is reflected in the vault. The next session (or another LLM) starts from there.
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.