Turn your AI agent into an obsessive Obsidian archivist

What it does

obsidian-wiki is a collection of markdown skill files that AI coding agents read and execute. You point the agent at an Obsidian vault, feed it raw material—PDFs, chat logs, images, meeting transcripts—and it extracts concepts, merges them into existing notes, and keeps cross-references and frontmatter summaries current. Obsidian acts as the viewer; the agent acts as the maintainer.

The interesting bit

The work happens in a four-stage ingest pipeline: the agent reads sources directly, pulls signal from noise, merges new knowledge against existing pages while flagging contradictions, and lets the vault schema emerge organically rather than forcing a rigid structure upfront. A .manifest.json tracks everything that has been ingested, so subsequent runs only process what is new or changed.

Key highlights

• Supports a wide roster of agents: Claude Code, Cursor, Windsurf, Codex, Gemini CLI, Kiro, Hermes, Pi, and others.
• Sources are tracked in page frontmatter, so claims remain attributable.
• Each page gets a one- to two-sentence summary: in frontmatter for quick previewing during later queries.
• Handles diverse inputs: markdown, PDFs, JSONL exports, images (with vision models), and plain text.
• Skills are symlinked from a central package, so upgrading the framework propagates to every agent.

Caveats

• The README is truncated mid-sentence during the color-coding explanation, so some visualization details remain incomplete.
• Because the entire workflow is agent-driven, the quality of your wiki depends entirely on the agent correctly interpreting the skill files and consistently separating signal from noise.
• There is no separate preprocessing pipeline or validation layer; if the agent drifts, the vault drifts with it.

Verdict

Worth exploring if you already live in Obsidian and want your AI agent to curate a persistent, queryable memory instead of treating every prompt as a cold start. Give it a pass if you need a rigid, predefined taxonomy or a backend service that operates without an agent in the loop.