It's interesting seeing the de-emphasis on download links coming from the site's existing DBs, almost a shock
I wonder what the user engagement of command-based vs tool-based site would be, as I kind of feel (particularly for CLI programs) the recipe idea might be a more popular approach given many searches for CLI-based programs center around usage (with all their disparate argument naming conventions, less familiarity with the command-line etc).Still think there may be an outcome where some recipes would essentially make it a docs page for a particular program. Eg: downloading a video considerably narrows limits which viable programs to use, with youtube-dl being the foremost and most likely for recipe creation, and with all of ytdl's features it wouldn't be surprising to see dozens of recipes that would be essentially straight out of its readme---yet no doubt useful.
That said, the above isn't the worst thing that could happen so I'm still open minded about it and I like the idea of introducing people to practical examples of CLI usage.
Something to consider may be caveats to CLI usage somewhere: like such-and-such a program lacks Unicode support, or whatnot. For CMD itself for example there are numerous gotchas with path name parsing and also a hard limit on the max string/variable length that can be passed to/handled by it (relevant more for batch scripting).
