obsidian-wiki skill
A skill set that lets an agent run a personal Obsidian wiki: it compiles knowledge from documents and past sessions and answers with citations
- 3,633 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads agent conversation history and project files
- Writes pages to the local vault and runs Python scripts
Install
- Works in
Manual install
pip install obsidian-wiki
obsidian-wiki setup --vault ~/brainuv tool install obsidian-wiki and pipx install obsidian-wiki also work. Then ask the agent to set up the wiki.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads agent conversation history and project files
- Writes pages to the local vault and runs Python scripts
This is third-party code. Review the repository files before installing.
What it does
The project follows Andrej Karpathy's LLM Wiki pattern: instead of re-answering the same questions, the agent compiles what it learns into linked markdown pages in an Obsidian vault. Skills ingest folders, URLs, PDFs, the current repository and conversation history from Claude Code, Codex, Copilot and other agents. Queries return answers with wikilink citations, and maintenance skills find broken links, duplicates and contradictions and weave new pages into the graph. A manifest tracks what was ingested, so later runs process only the delta.
Who it is for. For developers and researchers who want to keep knowledge from agent sessions in their own base instead of losing it in chat logs.
Good fit when
- You want an Obsidian knowledge base the agent fills and maintains itself
- You want to mine useful knowledge from old Claude Code or Codex sessions
- You need to find a past session or solution by description
Not a fit when
- You need a team wiki with access control and shared editing
- You do not use markdown notes and do not want a vault on disk
Example request
Save this session to the wiki and link it to what I already know about rate limitingLimitations
Ingesting large chat archives costs many tokens; the author suggests pre-extracting JSONL with the bundled script. Page quality depends on the agent's model. Python is required for the CLI and helper scripts.
How to disable. Remove the package with pip uninstall obsidian-wiki and delete the .skills symlinks from your agents' skill directories. The vault stays a plain markdown folder.
FAQ
Are API keys or a server required?
No. Skills are markdown files the agent runs itself, and the wiki lives in a local folder.
Which agents are supported?
Claude Code, Cursor, Codex, Windsurf, Gemini CLI and others: the .skills folder is symlinked into each.
Discussion
No questions or reviews yet.
Related
SkillsFour skills for a personal Obsidian knowledge base: an agent compiles articles and notes into a linked wiki, answers from it and health-checks it
Obsidian skills
Obsidian Skills
Skills for agents working with Obsidian: Markdown with wikilinks, Bases, JSON Canvas, Obsidian CLI, Defuddle and Knap
A plugin and skill set that turns an Obsidian vault into a knowledge base with sources, links and grounded answers
A workflow for Claude Code, Codex and Gemini CLI where the agent files source documents into a persistent, linked wiki
Karpathy LLM Wiki
karpathy-llm-wiki
A skill for a personal knowledge base the model maintains: ingest sources, compile cited articles, lint integrity
Turns session history of Claude Code, Codex, Cursor and Gemini CLI into a searchable wiki on Karpathy's LLM Wiki pattern, locally
README in short
The README explains the idea: knowledge is compiled once and kept current rather than retrieved again through RAG. Install via pip, uv or pipx and run setup with a vault path, or ask the agent to do it. It lists commands for ingesting, querying, digests and wiki cleanup, plus a CLI for searching past sessions. The graph exports to GraphML, Neo4j, SQL or interactive HTML. MIT licensed.
README badge
Original SKILL.md
--- name: claude-history-ingest description: > Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs. --- # Claude History Ingest — Conversation Mining You are extracting knowledge from the user's past Claude Code conversations and distilling it into the Obsidian wiki. Conversations are rich but messy — your job is to find the signal and compile it. This skill can be invoked directly or via the `wiki-history-ingest` router (`/wiki-history-ingest claude`). ## Before You Start 1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (inline `@name` override → walk up CWD for `.env` → global config → prompt setup). This gives `OBSIDIAN_VAULT_PATH` and `CLAUDE_HISTORY_PATH` (defaults to `~/.claude`) 2. Read `.manifest.json` at the vault root to check what's already been ingested 3. Read `index.md` at the vault root to know what the wiki already contains ## Ingest Modes ### Append Mode (default) Check `.manifest.json` for each source file (conversation JSONL, memory file). Only process: - Files not in the manifest (new conversations, new memory files, new projects) - Files whose modification time is newer than their `ingested_at` in the manifest