Ai Second Brain Skills

AI Second Brain Skills

Your folder becomes your app. No database. No embeddings. Just markdown — and an AI that knows where to look.

Two Claude Code skills that turn any folder into a compounding, AI-maintained knowledge base. Based on Andrej Karpathy's [LLM wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f), with a research loop inspired by his [autoresearch](https://github.com/karpathy/autoresearch) project.

TL;DR

git clone https://github.com/NulightJens/ai-second-brain-skills.git ~/ai-second-brain-skills
ln -s ~/ai-second-brain-skills/llm-wiki-setup  ~/.claude/skills/llm-wiki-setup
ln -s ~/ai-second-brain-skills/wiki-self-heal  ~/.claude/skills/wiki-self-heal

Then in Claude Code:

1. "Set up an LLM wiki at ~/my-second-brain"
2. Drop a source into raw/
3. "Ingest the source I just added to raw/"
4. "Run wiki-self-heal" once a week

That's the whole loop.

Why this exists

Most people's AI workflow: paste context into a chat, get an answer, start a new chat, paste everything again. Knowledge evaporates between sessions. Nothing compounds.

The wiki pattern is different. The LLM reads every source **once**, extracts the knowledge, and writes it into an interlinked set of markdown files — a persistent wiki that sits between you and your raw sources. When you ask a question, it reads the wiki (not the sources). When you add a source, it integrates, flags contradictions, and strengthens the synthesis. Knowledge is compiled once and kept current.

No vector database. No embeddings. No chunking pipeline. The folder is the app.

How it works

A three-layer mental model:

1. The map — CLAUDE.md at the vault root. The AI reads this first, every time. It contains the folder structure, the routing table ("for task X, read these files"), naming conventions, workflows, and guardrails. Think of it as the floor plan posted at the entrance of a building.
2. The rooms — raw/ (immutable sources, read-onl