LLM Wiki Agent workflow
A workflow for Claude Code, Codex and Gemini CLI where the agent files source documents into a persistent, linked wiki
- 3,694 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Only works with local markdown files inside the repository
Install
- Works in
Manual install
git clone https://github.com/SamurAIGPT/llm-wiki-agent.git
cd llm-wiki-agentClone the repository locally
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Only works with local markdown files inside the repository
This is third-party code. Review the repository files before installing.
What it does
The repository defines a structure and instructions (CLAUDE.md, AGENTS.md) that the agent follows to maintain a wiki itself. The user drops documents into raw/ and asks the agent to ingest them; the agent reads the source, creates source, entity and concept pages under wiki/, and updates index.md and the append-only log.md. Separate local scripts under tools/ run structural checks without an LLM (health.py), LLM-based content quality checks (lint.py), and build a link graph (build_graph.py) into graph.json and graph.html. Non-markdown files (PDF, DOCX, PPTX, XLSX, HTML and others) are first converted via markitdown.
Who it is for. For researchers and analysts who want an agent to build a linked knowledge base out of documents they keep dropping in.
Good fit when
- You need to accumulate material from many sources into one linked wiki across sessions
- You want the agent to answer questions by synthesizing across already ingested sources
- You need to check the wiki for contradictions and orphan pages
Not a fit when
- You need a one-off translation or summary of a single document, not an accumulating base
- You need a multi-user wiki with accounts, not local markdown files
Example request
Ingest this paper into the wiki and show how it connects to sources already thereLimitations
No API key is needed for Claude Code since the agent maintains the wiki through its own file read and write tools. health.py and build_graph.py need a local Python install. lint.py makes LLM calls for semantic checks. The wiki is entirely local, with no sync between machines and no server.
How to disable. Delete the cloned repository folder or stop opening it in the agent.
FAQ
Do you need a separate API key?
Not for Claude Code and similar agents, they work through their own file access. A key is only needed for the lint.py script, which makes LLM calls for quality checks.
Which source formats are supported?
Markdown is ingested directly, while PDF, DOCX, PPTX, XLSX, HTML, TXT, CSV, JSON, XML, RST, EPUB and other formats are first converted to markdown via markitdown.
Discussion
No questions or reviews yet.
Related
WorkflowsLLM Wiki Manager keeps a personal Markdown wiki through an agent: it ingests sources, links pages and answers with citations
A Claude Code template that builds a knowledge base from articles and PDFs: five newsroom roles and contradiction checks.
A CLI that creates an Obsidian-ready Markdown vault and installs four skills so an agent maintains the knowledge base.
A plugin that turns PDFs, articles and notes into a shared markdown wiki that agents search, cite and keep growing
A personal wiki in a .wiki folder: the agent reads sources, writes cross-linked pages and health-checks the knowledge base
A markdown research wiki template: the agent ingests sources, updates pages and checks every quote word for word against the file.
README in short
The README calls the project a coding agent skill: drop sources into raw/, tell the agent to ingest them, and it extracts knowledge and builds a linked wiki with an index.md catalog, an append-only log.md, a synthesizing overview.md, and source, entity, concept and synthesis pages. Setup is a plain git clone opened in Claude Code, Codex, OpenCode or Gemini CLI, with no API key or separate Python setup required. Claude Code additionally exposes /wiki-ingest, /wiki-query, /wiki-lint, /wiki-graph slash commands. MIT licensed.