obsidian wiki A digital brain you grow with your AI agent. It remembers what you figure out, connects it to what you already know, and answers when you ask. English 繁體中文 You solve a hard problem on a Tuesday. Three months later, in a different repo, you solve it again from scratch — because the answer lived in a chat log you'll never find. This fixes that. Point it at a folder, tell your agent what to remember, and it compiles what you learn into interconnected markdown you own. The pattern comes from Andrej Karpathy's LLM Wiki gist: compile knowledge once and keep it current, instead of asking an LLM the same questions forever or re running RAG every time. Your second brain. Your AI agent is how you grow it. Every skill here is a markdown file that any agent — Claude Code, Cursor, Codex, Windsurf, Gemini CLI, and a dozen more — reads and runs. No runtime, no API keys, no vendor. 60 seconds [安装/使用命令见下方] Then open any project in your agent and say "set up my wiki" . Prefer not to touch a terminal? Give your agent this and it'll do the whole thing: [安装/使用命令见下方] Other paths — git clone , Skills CLI, multiple vaults → Installation What you actually do Feed it. Anything text shaped: docs, PDFs, chat exports, meeting transcripts, screenshots, URLs. [安装/使用命令见下方] Ask it. Answers come back with [[wikilink]] citations, not vibes. [安装/使用命令见下方] Find that session you can't name. [安装/使用命令见下方] Keep it honest. The vault gets messy on its own; these clean it. [安装/使用命令见下方] All 39 skills → Skills Reference See it Open the vault in Obsidian and hit the graph view (Cmd/Ctrl+P → "Open graph view"). Say "color my graph" and it tints nodes by tag, category, or visibility. Or export the whole graph to graph.json , GraphML (Gephi/yEd), Neo4j Cypher, or a self contained interactive graph.html . Why this and not a notes folder It compiles, it doesn't accumulate. New knowledge merges into existing pages. Contradictions get flagged. Nothing gets duplicated. It only reads what changed. A manifest