pickfit

BrowseLocal AI tools

LLM Wiki v2

Turns documents into a Markdown wiki that files notes and answers questions with citations.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python 3.11 or later
  • Keys or accounts: LLM provider key
  1. Install llmwiki2 with uv tool

    uv tool install llmwiki2

Check that it works

llmwiki2 --help 2>&1

The output should contain “LLM wiki on the Open Knowledge Format”.

First thing to try

rm -rf ./wiki ~/llm-wiki-demo && llmwiki2 --bundle ./wiki init 2>&1 && echo "---INIT DONE---" && ls -R ./wiki 2>&1
llmwiki2 --bundle ./wiki check 2>&1

Run llmwiki2 --bundle <wiki folder> check to point the tool at a wiki folder and check it.

What it does

  • File documents into a Markdown wiki
    Not tested
  • Get answers to questions with citations
    Not tested
  • Import text, PDF and Office files
    Not tested
  • Use the wiki as long-term memory for MCP clients
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Good for

  • file dropped documents into a Markdown wiki
  • answer questions with citations to notes
  • browse folders and notes as a live map

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.7.0

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.