pickfit

BrowseLocal AI tools

etiny

Offline tiny models that scan markdown notes for distilled book advice on goals, careers, and pitches.

Tested on Linux

Use it

Linux x86_64

  1. pipx install etiny

    pipx install etiny
  2. pull personal-goals bundle

    etiny pull personal-goals
Where the README and reality differ
  • README: etiny walk — scan every .md under a folder, recursively
    What worked: command 'walk' does not exist: etiny reports invalid choice walk (choose from pull, list, update, info, rm, prune, verify, scan, elevators, elevations, doctor)
  • README: etiny scan notes.md works with bare relative path
    What worked: bare 'notes.md' fails with 'document not found: notes.md'; requires ./notes.md or absolute path /home/sbx/work/notes.md
  • README: etiny elevations "fear of failure" search syntax
    What worked: outer CLI rejects positional phrase and --search; bundle elevations.py expects --search/--limit but outer parser does not forward them without extra separator
  • README: default model is personal-goals (table says yes)
    What worked: default MODEL is 'goals' which is not in registry; must pass --model personal-goals explicitly after pull

Check that it works

etiny --help

The output should contain “usage: etiny”.

First thing to try

etiny elevators --model personal-goals

Run etiny elevators --model personal-goals to list the source works in a downloaded model.

What it does

  • List source works with their counts
    How to use it
    1. Run etiny elevators --model personal-goals to list the books behind a model.
    2. Read each line for the work's ID, title, author and counts.
    Tested
  • Scan a document against advice models
    Not tested
  • Search the advice rules for a phrase
    Test failed
  • Scan all Markdown files in folders and subfolders
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • scan a markdown document against advice models
  • scan every markdown file in subfolders recursively
  • search the rule corpus for a word or phrase
  • list source works with their counts
  • fetch a model bundle for offline use

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 1 Nov 2026
  • Version 0.1.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.