Desktop softwareCLI tools playbook
Developers adopt terminal tools from a README GIF, a Show HN thread or a package manager. Outpost prepares the packaging entries, curated-list entries and launch drafts for you to submit, with a receipt for each.
01 · DISCOVERY
Developers find CLI tools on GitHub, Hacker News (Show HN), curated awesome-lists, devtools newsletters such as Console and Changelog News, terminal and language-specific communities, and by searching their package manager. The README is the landing page. An install one-liner and a short terminal recording decide whether someone tries the tool in the next 30 seconds.
See it, install with brew, winget, cargo, npm or pip, and run one command. Adoption spreads when the tool lands in someone's dotfiles, CI scripts or team docs. If there's a business, it's usually a hosted or team tier around an open-source core.
02 · CHANNELS
Ranked 5 (essential) to 1 (optional) by the research for this industry.
Developers expect one-line installs. Your own Homebrew tap (a repo named homebrew-<name>) works on day one. homebrew-core needs a stable tagged release and notability: self-submissions need at least 90 forks, 90 watchers or 225 stars, and repos under 30 days old usually aren't eligible. On Windows, winget and Scoop cover most terminal users.
The highest-signal launch for developer tools. It must be something people can try now (no landing pages or sign-ups), you must be there to discuss it, and HN's guidelines say no vote solicitation and no AI-generated or AI-edited text.
The README converts. A reproducible terminal recording, such as a VHS .tape script rendered to a GIF, shows the tool working and can be regenerated on every release.
Awesome-lists still send steady discovery traffic, but check they're alive: awesome-cli-apps is archived and read-only, while awesome-tuis is maintained and takes PRs for maintained TUI apps.
Console reviews a few devtools each week in a free newsletter. Changelog News takes submissions but excludes commercial products, which go through sponsorship.
Command-line communities and language communities (Rust, Go and others) share tools built in their stack. Lead with what problem it solves and how it compares with the classic Unix tool.
03 · YOUR FIRST MONTH
A sample month. Your own plan is built from your audit, stage and goal, and paid options only ever appear as optional boosts.
Week 1 · days 1–7
Week 2 · days 8–14
Week 3 · days 15–21
Week 4 · days 22–30
04 · WHERE TO BE LISTED
Costs are as published by each destination when the research was reviewed; check before you pay for anything.
news.ycombinator.com
The developer launch venue. The tool must be usable now, and the maker must be present.
docs.brew.sh
Your own tap works immediately. homebrew-core comes later, once you have a stable release and meet notability.
github.com
One-line installs on Windows. Needs an official installer URL and a silent install.
github.com
Popular with Windows developers. Main is for CLI tools and has a higher bar; open an issue first.
devhunt.org
A launch site for developer tools only, with a free permanent listing.
Free listing; $19 paid launch optional
github.com
A maintained, community-run list of terminal UI apps that takes PRs.
console.dev
A free weekly devtools newsletter that reviews a few tools per issue.
Free to read (selection editorial)
changelog.com
Accepts news submissions about interesting developer projects, but not commercial products.
05 · SEARCH DEMAND
Primary search
how to promote cli tool
Below the provider’s reporting threshold: real demand, too small to report.
DataForSEO Google Ads, US/en, Oct 2026. Primary keyword below reporting threshold; related 'homebrew cask' 390/mo, 'homebrew tap' 140/mo.
Comparing: show why you
Looking for a place: be listed there
Learning: answer with guides
Ready to act: make it easy
06 · AVOID
Homebrew requires a stable, tagged release and notability, and repos under 30 days old usually aren't eligible. Ship a tap first and submit to core when you qualify.
HN treats landing pages and sign-up pages as off-topic for Show HN. Link the repo or something people can run right now.
HN's guidelines ask for no generated or AI-edited text, and no automated posting. Outpost drafts notes, but the post must be written and submitted by you.
Some famous lists, including awesome-cli-apps, are archived and read-only. Check activity before spending time on a PR.
If people have to scroll to learn how to install it, or can't see it working, most leave. Put install commands and a GIF at the top.
07 · WHAT OUTPOST DOES
Runs a packaging checklist (tagged release, checksums, tap, winget and Scoop manifests) and tracks each PR you open with a receipt.
Audits your docs site and suggests a demo script for the main use case.
Prepares Show HN talking points and a launch-day checklist. You write and post it yourself, as HN's guidelines require.
Finds the curated lists for your category and drafts each entry for you to open as a PR.
Prepares DevHunt, Console and Changelog News listings where they fit, for you to submit, and tracks the clicks they send.
Every action Outpost takes gets a receipt: the live URL, a timestamp and what it drove, or “nothing yet”.See how receipts work
08 · QUESTIONS
Both, in that order. A tap (a repo named homebrew-<name>) lets people run 'brew install you/tool/tool' today. homebrew-core needs a stable release and notability; self-submissions need at least 90 forks, 90 watchers or 225 stars. Move once you qualify.
No, and that's on purpose. HN's guidelines say not to automate posting or use AI-generated text, and they want the maker in the thread. Outpost prepares notes, timing and a checklist, and you post and reply in your own words.
They're a signal, not the goal, but they matter in practice: Homebrew uses them as one notability measure, and many developers glance at them. Earn them with a better README and real launches, never by trading or buying stars.
Publish to winget (official installer URL, silent install) and Scoop (open an issue first; Main is for CLI tools). Put both one-liners in the README next to Homebrew.
Console reviews a few devtools each week, and Changelog News accepts submissions for open-source projects, not commercial products. Language-specific newsletters for your stack are often the best fit.
A good Show HN can bring a burst in a day. Steady adoption comes from package-manager search, curated lists and word of mouth over many releases. Plan on months of consistent releases.
10 · EVIDENCE
Every fact on this page comes from one of these sources.
Tap repos named homebrew-<name>; install with user/repo/formula; taps run code with user privileges.
Stable release with immutable tag or release required for homebrew-core.
Notability thresholds (30/30/75; 90/90/225 for self-submissions) and the 30-day repo age rule.
Must be tryable now; landing and sign-up pages off-topic; maker must be around; no vote solicitation.
Don't automate posting; no generated or AI-edited text.
Terminal recorder that renders scripted .tape files to GIFs.
Repository is archived and read-only.
Maintained community list of TUI apps that accepts PRs.
Free weekly devtools newsletter reviewing 2-3 tools per issue.
News submissions accepted; commercial products excluded.
Official installer URL and silent install required.
Open an issue first; manifest conventions.
Last reviewed . Search volume: DataForSEO Google Ads, US/en, Oct 2026. Primary keyword below reporting threshold; related 'homebrew cask' 390/mo, 'homebrew tap' 140/mo.
FREE WEBSITE AUDIT
Paste your website. Outpost reads it, scores your visibility, finds your competitors and shows the first fixes, free. Then the playbook above becomes your own campaign, measured in installs.
See plans and pricing