brainrepo

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.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "brainrepo" with this command: npx skills add codezz/brainrepo

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

Acmesh

A pure Unix shell script ACME client for SSL / TLS certificate automation acmesh, shell, acme, acme-challenge, acme-protocol, acme-v2, ash. Use when you need...

Registry SourceRecently Updated
1050ckchzh
Coding

Webhook Tester

Webhook testing and debugging tool. Send test webhook payloads to any URL, simulate various webhook events (GitHub, Stripe, Slack), inspect responses, and lo...

Registry SourceRecently Updated
Coding

Uptime

Website and service uptime checker. Monitor URLs for availability, measure response times, check HTTP status codes, verify SSL certificates, and track uptime...

Registry SourceRecently Updated
Coding

Sslgen

Self-signed SSL certificate generator. Create SSL certificates for development, generate CA certificates, create certificate signing requests, and manage dev...

Registry SourceRecently Updated