pickfit

BrowseDeveloper CLIs

wiki

CLI to read Wikipedia articles, search, query Wikidata, fetch metrics and stream dumps.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Go 1.26+
  • Needs the network
  1. Download linux_amd64 release tarball and install wiki to ~/.local/bin

    curl -sL -o /tmp/wiki.tar.gz https://github.com/tamnd/wikipedia-cli/releases/download/v0.4.9/wiki_0.4.9_linux_amd64.tar.gz && mkdir -p ~/.local/bin && tar -xzf /tmp/wiki.tar.gz -C /tmp && cp /tmp/wiki ~/.local/bin/wiki && chmod +x ~/.local/bin/wiki && ~/.local/bin/wiki --version

Check that it works

wiki --version

The output should contain “wiki version dev”.

First thing to try

cat > /tmp/sample.xml <<'XML'
<mediawiki version="0.11" xml:space="preserve" xmlns="http://www.mediawiki.org/xml/export-0.11/">
<siteinfo>
<sitename>Wikipedia</sitename>
<dbname>enwiki</dbname>
<base>https://en.wikipedia.org/wiki/Main_Page</base>
<generator>MediaWiki 1.44.0</generator>
<case>first-letter</case>
<namespaces>
<namespace key="0" case="first-letter" />
</namespaces>
</siteinfo>
<page>
<title>Alan Turing</title>
<ns>0</ns>
<id>12345</id>
<revision>
<id>1</id>
<timestamp>2024-01-01T00:00:00Z</timestamp>
<contributor><username>Test</username><id>1</id></contributor>
<comment>test</comment>
<model>wikitext</model>
<format>text/x-wiki</format>
<text bytes="27" xml:space="preserve">'''Alan Turing''' was great.</text>
<sha1>abc</sha1>
</revision>
</page>
<page>
<title>Quantum computing</title>
<ns>0</ns>
<id>12346</id>
<revision>
<id>2</id>
<timestamp>2024-01-02T00:00:00Z</timestamp>
<contributor><username>Test</username><id>1</id></contributor>
<model>wikitext</model>
<format>text/x-wiki</format>
<text bytes="20" xml:space="preserve">Quantum is cool.</text>
<sha1>def</sha1>
</revision>
</page>
</mediawiki>
XML
cat /tmp/sample.xml
wiki dump pages /tmp/sample.xml --quiet -o jsonl

Run wiki read "<article title>" to print a Wikipedia article in your terminal.

What it does

  • Read Wikipedia articles as text
    How to use it
    1. Run wiki read "<article title>" to print the article.
    Tested
  • Search the full text of Wikipedia
    How to use it
    1. Run wiki search "<your text>" to list matching articles with titles, descriptions, snippets and links.
    Tested
  • Query Wikidata with SPARQL
    How to use it
    1. Run wiki sparql '<your query>' --quiet -o jsonl to get one JSON result per line.
    Tested
  • Stream Wikipedia dump files
    How to use it
    1. Run wiki dump pages <file> --quiet -o jsonl on a pages-articles XML dump.
    2. Read one JSON line per page with its id, title, revision and timestamp.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • read an article as paged text or markdown
  • full-text search Wikipedia articles
  • query a Wikidata entity
  • fetch per-article pageview time series
  • stream-parse a pages-articles dump

How pickfit tested it

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

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version dev

Differences the test machine hit

  • README: go install github.com/tamnd/wikipedia-cli/cmd/wiki@latest (requires Go 1.26+)
    In the test: downloaded prebuilt linux_amd64 tarball from GitHub releases and copied wiki binary to ~/.local/bin
  • README: versioned release binary
    In the test: binary prints 'wiki version dev' with no release number

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.