CLI Tools

Command-line tools are the most concentrated form of the developer-software category: one person, one irritation, one small binary that does exactly one thing correctly. They are also the most likely launches on this site to still be in use three years later, because a good CLI tool has almost no maintenance surface and almost no migration cost.

What makes one good is fairly consistent. It does one job. It reads from standard input and writes to standard output so it composes with everything else. Its output is parseable when piped and pretty when it is not. It has a genuinely useful help output rather than a link to a website. It installs as a single binary with no runtime to manage. Tools that get those five right tend to get adopted regardless of what they do.

The categories that show up most often are file and text manipulation, git ergonomics, HTTP and JSON handling, system inspection, and the growing set of terminal interfaces to services that already have a web dashboard. That last group is more valuable than it sounds, because the CLI version is scriptable and the dashboard is not.

Distribution is worth a thought when you are choosing. A tool available through your existing package manager will be updated; a tool installed by piping a script from a website will not be, and you will not notice until it breaks. Prefer the former where you can, and be honest that the convenience of the latter is why it persists.

The other thing to check is what happens on error. Terminal tools are frequently run inside scripts and pipelines, so exit codes and stderr behaviour matter more than they do in an interactive app. A tool that exits zero on failure will eventually cause a silent bad outcome in someone's automation.

For makers, this is the friendliest subcategory to launch into and the hardest to monetise, which is worth knowing before you decide what you are building. The audience is enthusiastic, technically able to evaluate your work properly, and largely unwilling to pay for a small utility. The successful commercial ones almost always sell the service the CLI talks to rather than the CLI itself.