Why You Need a Brain

The skills you unlock in SkillTree are only as good as the context they read from. The Brain is that context. This is the case for building one before you build anything on top of it.

Every SkillTree skill reads from one place: your brain.

The map gives you 78 AI employees. The dashboards give you command centers. But a skill that writes your client recap, updates your pipeline, or researches a prospect is useless if it doesn't know your business. It needs to know who your clients are, what you've built, how you talk, what you decided last month. That's the brain · your company's second brain, the knowledge base every skill pulls from automatically.

Build it once. Every skill gets smarter for free.

The problem: context amnesia

Most people open Claude and just start typing. It works for one-off tasks. It falls apart the moment you're running a real business through it.

Without a memory system, every session starts from zero. Your architecture, your conventions, the client detail you explained yesterday · gone when the window closes. You burn 30 to 40 minutes per session re-explaining what the model already should know. That's a full workday a week, every week, just re-explaining.

The symptoms are predictable:

• It re-asks questions you've already answered
• It proposes patterns you've explicitly rejected
• It forgets decisions made three sessions ago
• It treats your business like it's seeing it for the first time
• It loses the reasoning behind decisions, not just the decisions

When people say AI can't do real work, what they're actually saying is they gave it bad context. The fix isn't a smarter model. It's a memory system the model can operate from.

Why this compounds

Picture two operators who both start running their business on AI today.

• Operator A just types prompts. Cold start every session.
• Operator B spends a few hours building a brain · clients, processes, decisions, meeting notes · and feeds it as they go.

After a month, the outputs are noticeably different. After six months, the gap is wide. After two years, Operator B is running a system that knows their business cold: every client, every process, every decision, the full history. Operator A is still re-explaining themselves to a blank window.

Context compounds. That's the entire bet.

"All returns in life, whether in wealth, relationships, or knowledge, come from compound interest."

Naval Ravikant

The Brain is how you put your business knowledge on a compounding curve. Every meeting logged, every decision captured, every process written down makes every future session better · not just the next one.

What the Brain actually is

Two surfaces, one job: be the memory every skill reads from.

• Notion · structured, collaborative, AI-native. Best for clients, projects, pipeline, and anything a team or client touches.
• Obsidian · local, private, graph-based. Best for deep personal knowledge and thinking, with a knowledge graph Claude can query at runtime.

Many operators run both: Obsidian for personal knowledge and thinking, Notion for clients and projects. That's a valid setup, and the rest of this module shows you how to build each.

What you'll build in this module

• Your Brain in Notion · the structured company brain
• Your Brain in Obsidian · the local knowledge graph
• The capture workflow · how new knowledge gets captured automatically
• How to prompt your brain so the context actually lands

The technical CLAUDE.md and MCP setup lives in Claude Code Foundations. This module is about building the knowledge layer those tools read from. Don't skip it · a skill with no brain is just an expensive guess.