Who it is forA person with many documents in mixed formats who needs answers from them and does not want to read everything again.
The problemScattered documents are hard to search and answers are hard to trace back to a source.
The outcomeA folder of Markdown notes that answers questions and cites the notes it used.
What you need first
- Python 3.11 or later, or uv to install it
- An API key for OpenRouter, OpenAI, Gemini or another OpenAI-compatible server, or Ollama installed for free local use
- Documents as text, Markdown, PDF, Word, PowerPoint, Excel or OpenDocument files
Steps
- Install it with
pip install llmwiki2(Python 3.11 or later). - Start it with
llmwiki2; your browser opens. - Pick a provider, paste its key, press Test connection, then Save and start.
- Drop text, Markdown, PDF, Word, PowerPoint, Excel or OpenDocument files anywhere on the page.
- Type a question and click a cited note to read it.
Prompt for your agent
Using the llm-wiki-v2 repo (package llmwiki2), file the documents in <documents folder> into the wiki, then ask it <question>. Expected output: the answer plus the note paths it cites. Verify that each cited note exists as a Markdown file in ~/llm-wiki.
Caveat. A scanned PDF with no text layer adds nothing until you run OCR on it first.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page