pickfit

BrowseProductivity & docs tools

Pandoc

A Haskell library and command-line tool that converts documents between many markup formats, such as Markdown, HTML, LaTeX, docx and EPUB.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: LaTeX (optional, for PDF output)
  1. download latest linux-amd64 release tarball and extract into ~/.local

    V=$(curl -fsSL https://api.github.com/repos/jgm/pandoc/releases/latest | python3 -c 'import sys,json;print(json.load(sys.stdin)["tag_name"])') && curl -fsSLo /tmp/pandoc.tgz https://github.com/jgm/pandoc/releases/download/$V/pandoc-$V-linux-amd64.tar.gz && mkdir -p $HOME/.local && tar xvzf /tmp/pandoc.tgz --strip-components 1 -C $HOME/.local

Check that it works

pandoc --version

The output should contain “Features: +server +lua”.

First thing to try

cat > in.md <<'EOF'
# Hello

Some *emphasis* and a [link](https://example.com).
EOF
cat > upper.lua <<'EOF'
function Str(el)
  return pandoc.Str(el.text:upper())
end
EOF
cat > myreader.lua <<'EOF'
function Reader(input)
  local blocks = {}
  for line in tostring(input):gmatch("[^\n]+") do
    table.insert(blocks, pandoc.Para{pandoc.Str(line)})
  end
  return pandoc.Pandoc(blocks)
end
EOF
cat > mywriter.lua <<'EOF'
function Writer(doc, opts)
  return "WORDS: " .. pandoc.utils.stringify(doc) .. "\n"
end
EOF
cat > lines.txt <<'EOF'
first line
second line
EOF
pandoc -f markdown -t html in.md

Run pandoc -f markdown -t html <file> to convert a Markdown file to HTML.

What it does

  • Convert documents between many markup formats
    How to use it
    1. Run pandoc -f markdown -t html <file> to convert a Markdown file to HTML.
    2. Change the -f (from) and -t (to) values to pick other formats.
    Tested
  • Change the document structure with custom filters
    How to use it
    1. Write a Lua filter file, for example one that returns pandoc.Str(el.text:upper()) from a Str function.
    2. Run pandoc --lua-filter <filter.lua> -t plain <file> to apply it during conversion.
    Tested
  • Use your own Lua readers and writers
    How to use it
    1. Write a Lua reader with a Reader(input) function and a Lua writer with a Writer(doc, opts) function.
    2. Run pandoc -f <reader.lua> -t <writer.lua> <file> to convert with them.
    Tested
  • Make PDFs through LaTeX, Groff ms or HTML
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • convert a Markdown file to PDF
  • convert Word docx documents to other markup formats
  • create slide shows such as reveal.js or beamer

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 15 Nov 2026
  • Version pandoc 3.14

Differences the test machine hit

  • README: sudo dpkg -i $DEB
    In the test: No root in this box; used the release tarball extracted into ~/.local instead
  • README: Pandoc can also produce PDF output via LaTeX, Groff ms, or HTML (LaTeX optional prerequisite)
    In the test: A separate PDF engine (LaTeX, groff, or weasyprint with system pango libs) must be installed; none was available without root

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.