agentleFS
weininghuiweininghui/skills/brainrepo/SKILL.md

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.

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
  1. Very specific:

    Check if ~/Documents/brainrepo/ exists with expected structure (Inbox/, Projects/, Areas/)

    line 20
  2. Distinctive:

    If NOT found → Run onboarding automatically

    line 21
  3. Distinctive:

    If found → Proceed with user request

    line 22
  4. Very specific:

    Create brain at ~/Documents/brainrepo/

    line 28
  5. Distinctive:

    Create the folder structure:

    line 29
  6. Very specific:

    Create initial files from templates in assets/templates/:

    line 35
  7. Distinctive:

    Every note uses minimal frontmatter:

    line 95
  8. Very specific:

    Use templates from assets/templates/ when creating new notes.

    line 109
  9. Distinctive:

    Don't organize — just capture

    line 115
  10. Very specific:

    Update Journal/YYYY-MM-DD.md with summary

    line 120
  11. Distinctive:

    Check Areas/ — anything neglected?

    line 126
  12. Very specific:

    Use [[wiki-links]] to connect notes:

    line 146

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Check if ~/Documents/brainrepo/ exists with expected structure (Inbox/, Projects/, Areas/)
  2. If NOT found → Run onboarding automatically
  3. If found → Proceed with user request

Onboarding

Triggers automatically on first interaction, or when user says "set up brainrepo":

  1. Create brain at ~/Documents/brainrepo/
  2. Create the folder structure:
mkdir -p <path>/{Inbox,Projects,Areas/personal-growth,Areas/family,Notes,Resources,Journal,People,Tasks,Archive}
  1. Create initial files from templates in assets/templates/:
    • Tasks/index.md — task hub
    • Areas/personal-growth/index.md — personal growth area
    • Areas/family/index.md — family area
  2. Initialize git (optional):
cd <path> && git init && git add -A && git commit -m "init: brainrepo"
  1. Confirm setup and show quick start commands

Core Concept

DUMP → PROCESS → RETRIEVE

  1. Dump — Capture everything to Inbox/ (don't organize yet)
  2. Process — Evening review: Inbox → permanent home
  3. 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 projects

See references/structure.md for detailed breakdown.

Capture Rules

What to Capture (Immediately)

TypeDestinationExample
Quick thoughtInbox/"Maybe we should..."
Decision madeInbox/ or Notes/"Decided to use Next.js"
Person infoPeople/New contact or update
Project updateProjects/<name>/Meeting notes, progress
Task/TodoTasks/index.md"Need to finish X"
Link/ArticleResources/ or Inbox/URL with context
Personal growthAreas/personal-growth/Health, habits, learning
Family infoAreas/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/:

  1. Each item → permanent home or delete
  2. Update Journal/YYYY-MM-DD.md with summary
  3. git commit -am "daily processing"

Weekly Review (Sunday, 15 min)

  1. Review all Projects/ — still active?
  2. Check Areas/ — anything neglected?
  3. Move completed projects to Archive/
  4. Update Tasks/index.md

See references/workflows.md for detailed workflows.

Commands

User saysAction
"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

ProjectsAreas
Have deadlinesNo end date
Can be "done"Maintained forever
Specific outcomeStandard 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.