Atlas

Atlas

A Claude Code skill that turns scattered research material into a structured, interconnected wiki maintained by an LLM. Based on [Andrej Karpathy's LLM Knowledge Bases workflow](https://x.com/karpathy/status/2039805659525644595) (April 2, 2026), which describes the ingest → compile → query → lint loop that Atlas implements as a skill.

You collect raw sources. Atlas organizes them into concept pages with summaries, cross-links, and a two-tier hierarchical index. You query it, and the LLM researches answers from the wiki and writes them as files that feed back into the knowledge base. The knowledge compounds over time.

**What Atlas adds beyond the original workflow.** Karpathy describes the shape of the loop (ingest → compile → query → lint). Atlas is the implementation that handles the engineering problems a real knowledge base hits as it grows: two-tier hierarchical indexing that prevents context rot past ~150 concepts, an alias registry that stops duplicate pages, a Source Verifier that audits wiki claims against their raw sources, scale-adaptive query routing, git-backed auto-commits on every operation, and a clean split with the companion Mentor skill so external curation (what belongs) and internal organization (where it goes) are separate concerns.

Quick Start

/atlas init "my research topic"     # Create KB structure
/atlas ingest          # Add a source
/atlas compile                       # Build the wiki
/atlas query "your question"         # Research against the wiki
/atlas lint                          # Health check with fix suggestions

Your wiki lives in `wiki/`. Entry point: `wiki/INDEX.md`. Concept pages: `wiki/concepts/`. The LLM maintains everything — you rarely edit directly. Git auto-commits on every operation, so rollback is cheap.

The Mental Model (read this once, confusion ends)

Atlas manages two kinds of pages, and only one of them ever asks anything of you.

**Concept pages** (`wiki/concepts/`, on