brainrepo
Skill1 starsChanged 13 days agoMITView on GitHub
Your personal knowledge repository — capture, organize, and retrieve everything using PARA + Zettelkasten. Triggers on: \"save this\", \"remember\", \"note\", \"capture\", \"brain dump\", daily/weekly reviews, searching stored knowledge, managing projects/areas/people. Works with any AI agent that reads markdown. Stores everything as .md files in a Git repo for Obsidian, VS Code, or any editor.
In this repository199 other files it gives its agents.
- activecampaignSkill
- adcp-advertisingSkill
- admapixSkill
- aegis-auditSkill
- afrexai-compliance-auditSkill
- afrexai-seo-content-engineSkill
- agent-browserSkill
- agentic-codingSkill
- agent-overflowSkill
- agent-skills-toolsSkill
- ai-ppt-generatorSkill
- airdrop-hunterSkill
- ai-web-automationSkill
- alicloud-ai-video-wan-r2vSkill
- alpha-finderSkill
- amap-trafficSkill
- amazon-product-apiSkill
- apertureSkill
- api-developmentSkill
- api-gatewaySkill
- asterSkill
- auto-replySkill
- auto-updaterSkill
- aviation-weatherSkill
- awwwards-designSkill
- base-8004Skill
- bioskillsSkill
- browserless-agentSkill
- browser-secureSkill
- btc15-autonomous-marketSkill
- buy-anythingSkill
- byteroverSkill
- cal-com-automationSkill
- capability-evolverSkill
- catalogSkill
- chargebeeSkill
- clawcostSkill
- clawdbot-documentation-expertSkill
- clawdbot-for-vcsSkill
- clawddocsSkill
- claw-syncSkill
- claw-trader-liteSkill
- clean-codeSkill
- cloudphoneSkill
- cls-certifySkill
- codebergSkill
- code-mentorSkill
- commit-analyzerSkill
- competitor-analysis-reportSkill
- content-ideas-generatorSkill
- content-ideasSkill
- contract-generatorSkill
- conventional-commitsSkill
- copywritingSkill
- crypto-payments-ecommerceSkill
- custom-smtp-senderSkill
- dashboard-manager2Skill
- data-analystSkill
- docker-sandboxSkill
- elite-longterm-memorySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Check if ~/Documents/brainrepo/ exists with expected structure (Inbox/, Projects/, Areas/)
- Distinctive: line 21
If NOT found → Run onboarding automatically
- Distinctive: line 22
If found → Proceed with user request
- Very specific: line 28
Create brain at ~/Documents/brainrepo/
- Distinctive: line 29
Create the folder structure:
- Very specific: line 35
Create initial files from templates in assets/templates/:
- Distinctive: line 95
Every note uses minimal frontmatter:
- Very specific: line 109
Use templates from assets/templates/ when creating new notes.
- Distinctive: line 115
Don't organize — just capture
- Very specific: line 120
Update Journal/YYYY-MM-DD.md with summary
- Distinctive: line 126
Check Areas/ — anything neglected?
- Very specific: line 146
Use [[wiki-links]] to connect notes:
≈ “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
BrainRepo
Your personal knowledge repository. Capture fast, organize automatically, retrieve instantly.
Brain Location
Fixed path: ~/Documents/brainrepo/
This is not configurable. All brain data lives here.
First Run Check
Before any action, check if brainrepo is initialized:
- Check if
~/Documents/brainrepo/exists with expected structure (Inbox/, Projects/, Areas/) - If NOT found → Run onboarding automatically
- If found → Proceed with user request
Onboarding
Triggers automatically on first interaction, or when user says "set up brainrepo":
- Create brain at
~/Documents/brainrepo/ - Create the folder structure:
mkdir -p <path>/{Inbox,Projects,Areas/personal-growth,Areas/family,Notes,Resources,Journal,People,Tasks,Archive}- Create initial files from templates in
assets/templates/:Tasks/index.md— task hubAreas/personal-growth/index.md— personal growth areaAreas/family/index.md— family area
- Initialize git (optional):
cd <path> && git init && git add -A && git commit -m "init: brainrepo"- Confirm setup and show quick start commands
Core Concept
DUMP → PROCESS → RETRIEVE
- Dump — Capture everything to Inbox/ (don't organize yet)
- Process — Evening review: Inbox → permanent home
- Retrieve — Ask AI to find anything
Repository Structure
brainrepo/
├── Inbox/ # Quick capture (clear daily)
├── Projects/ # Active work with deadlines
├── Areas/ # Ongoing responsibilities (no deadline)
├── Notes/ # Permanent atomic knowledge
├── Resources/ # External links, articles, references
├── Journal/ # Daily notes (YYYY-MM-DD.md)
├── People/ # One note per person
├── Tasks/ # Centralized task tracking
└── Archive/ # Completed projectsSee references/structure.md for detailed breakdown.
Capture Rules
What to Capture (Immediately)
| Type | Destination | Example |
| Quick thought | Inbox/ | "Maybe we should..." |
| Decision made | Inbox/ or Notes/ | "Decided to use Next.js" |
| Person info | People/ | New contact or update |
| Project update | Projects/<name>/ | Meeting notes, progress |
| Task/Todo | Tasks/index.md | "Need to finish X" |
| Link/Article | Resources/ or Inbox/ | URL with context |
| Personal growth | Areas/personal-growth/ | Health, habits, learning |
| Family info | Areas/family/ | Important dates, notes |
What NOT to Capture
- Casual chat without information value
- Temporary queries ("what time is it")
- Information easily searchable online
Note Format
Every note uses minimal frontmatter:
---
created: YYYY-MM-DD
tags: [tag1, tag2]
related: ["[[Other Note]]"]
---
# Title
Content here. Link to [[Related Notes]] freely.Use templates from assets/templates/ when creating new notes.
Daily Workflow
During Day
- Dump everything to
Inbox/ - Don't organize — just capture
Evening (5-10 min)
Process Inbox/:
- Each item → permanent home or delete
- Update
Journal/YYYY-MM-DD.mdwith summary git commit -am "daily processing"
Weekly Review (Sunday, 15 min)
- Review all Projects/ — still active?
- Check Areas/ — anything neglected?
- Move completed projects to Archive/
- Update
Tasks/index.md
See references/workflows.md for detailed workflows.
Commands
| User says | Action |
| "Set up brainrepo" | Run onboarding, create structure |
| "Save this: [text]" | Capture to Inbox/ |
| "New project: [name]" | Create Projects/name/ with template |
| "Add person: [name]" | Create People/name.md with template |
| "What do I know about X?" | Search & retrieve |
| "Daily review" | Process Inbox/, update Journal/ |
| "Weekly review" | Full system review |
Linking
Use [[wiki-links]] to connect notes:
Met with [[People/john]] about [[Projects/acme/index|ACME Project]].
Relevant insight: [[Notes/negotiation-tactics]]Projects vs Areas
| Projects | Areas |
| Have deadlines | No end date |
| Can be "done" | Maintained forever |
| Specific outcome | Standard to uphold |
File Naming
- Folders:
kebab-case/ - Files:
kebab-case.md - Dates:
YYYY-MM-DD.md - People:
firstname-lastname.md
References
- Structure Guide — Detailed folder breakdown
- Workflows — Daily/weekly/monthly workflows
- Templates — Note templates
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.

