by balukosuri
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
# Add to your Claude Code skills
git clone https://github.com/balukosuri/llm-wiki-karpathyGuides for using ai agents skills like llm-wiki-karpathy.
No comments yet. Be the first to share your thoughts!
A self-maintaining personal knowledge base powered by LLMs, based on Andrej Karpathy's LLM Wiki pattern.
Instead of re-searching raw documents on every question (like RAG), the LLM reads your sources once and builds a persistent, interlinked wiki that compounds over time. The more sources you feed it, the richer and more connected it gets.
git clone https://github.com/balukosuri/llm-wiki-karpathy.git
cd llm-wiki-karpathy
Cursor reads CLAUDE.md automatically and understands the wiki's structure, page formats, and workflows.
If you use a different AI agent (Claude Code, Codex, etc.), paste the contents of CLAUDE.md into your agent's context.
Open the project directory as an Obsidian vault. You'll have two windows side by side — Cursor on the left where you talk to the AI, Obsidian on the right where you browse the wiki as pages appear.
raw/Any document works:
Type this in Cursor:
ingest raw/my-document.pdf
The AI will:
wiki/sources/wiki/log.mdA single source can touch 5-15 wiki pages. Watch them appear in Obsidian in real time.
What are the main risks identified across all my sources?
The AI reads the wiki, synthesizes an answer with citations, and asks: "Should I save this as a wiki page?" If you say yes, the answer becomes a permanent analysis page. Your questions make the knowledge base richer over time.
Every 10 ingests or so, run a health check:
lint the wiki
The AI checks for contradictions between pages, stale claims, orphan pages with no links, missing cross-references, and inconsistent terminology. It reports what it found and asks which fixes to apply.
llm-wiki-karpathy/
├── CLAUDE.md # Schema — the AI's operating manual
├── llm-wiki.md # Karpathy's original idea document
├── article.md # Walkthrough article explaining this project
│
├── raw/ # Your source documents (AI reads, never writes)
│ └── .gitkeep
│
├── wiki/ # AI-generated knowledge base (AI owns this layer)
│ ├── index.md # Master catalog — the AI reads this first on every query
│ ├── overview.md # Big-picture synthesis (evolves with each ingest)
│ ├── glossary.md # Terms, definitions, and style conventions
│ └── log.md # Chronological record of all activity
│
└── .obsidian/ # Pre-configured Obsidian vault settings
| Layer | Folder | Who owns it | Purpose |
|-------|--------|-------------|---------|
| Raw sources | raw/ | You | Immutable source documents. The AI reads from here but never modifies anything. |
| The wiki | wiki/ | The AI | Structured, interlinked markdown pages. The AI creates, updates, and maintains everything here. |
| The schema | CLAUDE.md | You + AI | Defines page types, workflows, and conventions. Edit this to customize the AI's behavior for your domain. |
The AI creates different page types depending on what it finds in your sources:
| Type | Location | What it captures |
|------|----------|-----------------|
| Source | wiki/sources/ | Summary of a raw document — key facts, quotes, metadata |
| Feature | wiki/features/ | A product feature — what it does, how it works |
| Product | wiki/products/ | A product or tool — overview, versions, related features |
| Persona | wiki/personas/ | A user type — goals, pain points, expertise level |
| Concept | wiki/concepts/ | A domain idea — definition, related terms, common misconceptions |
| Style Rule | wiki/style/ | A writing convention — when to apply, examples, exceptions |
| Analysis | wiki/analyses/ | A synthesized output — comparison table, gap analysis, outline |
The schema file CLAUDE.md is not set in stone. Edit it to fit your needs:
Ingest one source at a time. You can batch-ingest, but you lose the chance to guide the AI. Stay involved — read the summaries, tell it what to emphasize, ask follow-ups during ingestion.
Save your best questions. When you ask something and get a useful answer, tell the AI to save it as an analysis page. Your explorations compound in the wiki instead of disappearing into chat history.
Use graph view often. Press Cmd+G in Obsidian. The visual map shows which pages are hubs, which are orphans, and how everything connects.
Check the glossary before writing. Open wiki/glossary.md before you write anything. It has the right terms, the wrong terms, and the reasons behind each choice.
Don't write wiki pages yourself. Your job is to find good sources and ask good questions. The AI handles the summarizing, cross-referencing, filing, and bookkeeping.