brain-search
Skill1 starsChanged 5 months agoMITView on GitHub
Search the second brain by keyword, tag, or natural language query. Returns summary cards with option to expand. Works from any project context.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- 0xSero/research-skillstheir own version, first seen Nov 15, 2026
- DentalEdge-Solutions/claude_codetheir own version, first seen Nov 1, 2026
- inite-ai/inite-brain-servicetheir own version, first seen Oct 18, 2026
- herreraspaintingba-hub/second-brain-starter-kittheir own version, first seen Oct 2, 2026
- hess0ul/brain-searchtheir own version, first seen Jun 9, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- inite-ai/inite-brain-service★ 43same name
- 0xSero/research-skills★ 4same name
- DentalEdge-Solutions/claude_code★ 1same name
- herreraspaintingba-hub/second-brain-starter-kit★ 0same name
- hess0ul/brain-search★ 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 repository14 other files it gives its agents.
- brain-addSkill
- brain-add-videoSkill
- brain-checkSkill
- brain-digestSkill
- brain-processSkill
- brain-saveSkill
- 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
16 rules. 0 are common, 11 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Search the brain and return relevant notes as summary cards.
- Very specific: line 23
Use the Grep tool on brain/index.md for query keywords (returns only matching lines, NOT the whole file)
- Distinctive: line 28
Run these Grep calls in parallel where possible
- Distinctive: line 30
Read ONLY those candidate notes in full to assess relevance
- Very specific: line 33
Read brain/index.md in full
- Very specific: line 35
Check mocs/ for relevant Maps of Content
- Distinctive: line 36
Read top candidate notes
- Distinctive: line 67
Read and display the full note content
- Distinctive: line 72
If the user is currently working on something specific (e.g., writing a newsletter), read each matching note and highlight only the parts …
- Distinctive: line 85
After presenting a rich, multi-note synthesis answer, offer to save it:
- Very specific: line 89
If the user confirms, create a synthesis note using the meta/templates/synthesis.md template:
- Distinctive: line 93
Update index.md and log.md
- Very specific: line 97
Grep-first: Use Grep on brain/index.md and note files before reading full files.
- Distinctive: line 99
If no results found, suggest related terms or check for typos in the query.
- Distinctive: line 100
Keep responses concise — the user wants to scan, not read paragraphs about their search.
- Distinctive: line 101
When called from outside brain/ (e.g., from ai-in-marketing/), adjust paths accordingly.
“Common” is measured: kept by at least 6 in 10 of the 4 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-search <query>
Search the brain and return relevant notes as summary cards.
Steps
- Parse the query from the argument. Identify:
- Keywords and phrases
- Tag filters (if query contains
#tagsyntax) - Category filters (if query mentions professional/personal/admin/creative)
- Natural language intent (what is the user looking for?)
- Grep-first search (primary strategy — avoids reading full index.md):
- Use the Grep tool on
brain/index.mdfor query keywords (returns only matching lines, NOT the whole file) - Also Grep across note files in
brain/(excluding inbox/, meta/, .carl/, .claude/) for: a. Frontmatter matches: tags, title, summary fields b. Body matches: query keywords in note content c. Wiki-link matches:[[query term]]references - Run these Grep calls in parallel where possible
- From the Grep results, identify the top 5-10 candidate note file paths
- Read ONLY those candidate notes in full to assess relevance
- Use the Grep tool on
- Fallback: full index read (only if Grep returns no/poor results for fuzzy/NLP queries):
- Read
brain/index.mdin full - Scan all entries for semantic matches against the query intent
- Check
mocs/for relevant Maps of Content - Read top candidate notes
- Read
- Rank results by relevance:
- Title match → highest
- Tag match → high
- Summary match → high
- Multiple keyword hits in body → medium
- Single keyword hit → lower
- Wiki-link reference → medium
- Deduplicate (same note matched by multiple strategies)
Present results as summary cards (top 10 max):
🔍 Found {count} results for "{query}" 1. **{title}** [{status}] 📂 {category}/{subcategory} | 🏷️ {tags} {summary from frontmatter} 📄 {file_path} 2. **{title}** [{status}] ...- Ask which to expand:
Enter a number to see the full note, or 'done' to finish. - When user selects a note:
- Read and display the full note content
- Show its
related:notes as additional leads - Offer to expand those too
- Context-aware excerpts (when called during a task):
- If the user is currently working on something specific (e.g., writing a newsletter), read each matching note and highlight only the parts relevant to their current task
- Prefix with: "Most relevant to your current work:"
Search shortcuts
#tag→ search by tag onlytype:article→ filter by note typestatus:evergreen→ filter by maturityin:admin→ search within a specific category- Plain text → full search across all fields
Synthesis filing
After presenting a rich, multi-note synthesis answer, offer to save it:
💾 This synthesis drew from {X} notes. Save it as a brain note? (type: synthesis)If the user confirms, create a synthesis note using the meta/templates/synthesis.md template:
type: synthesis,source: "brain-query"- Include the original query, the synthesized answer, and the list of source notes as [[wiki-links]]
- File in the most relevant category based on content
- Update index.md and log.md
Important
- Grep-first: Use Grep on
brain/index.mdand note files before reading full files. Only readindex.mdin full as a fallback for fuzzy/NLP queries. This saves significant tokens as the brain grows. - The brain root is at
brain/relative to the vault root. Use absolute paths when called from other projects. - If no results found, suggest related terms or check for typos in the query.
- Keep responses concise — the user wants to scan, not read paragraphs about their search.
- When called from outside brain/ (e.g., from ai-in-marketing/), adjust paths accordingly.
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.

