I wonder if there is or could be a good standard way of providing decoupled tools and their coupled interface. Last year I wrote a friendly script to search co

I wonder if there is or could be a good standard way of providing decoupled tools and their coupled interface. Last year I wrote a friendly script to search content on YouTube, which prints human-readable content if plugged to a terminal and URLs otherwise, and another one which applies a pattern to turn such YouTube URLs to the underlying video or audio streams using youtube-dl. (I don't think this plays along nicely with YouTube's ToS but whatever I'm the only user.) The obvious use case is to look at the output of the first command, and then pipe it to the second after choosing what to watch, and find a way to feed that to mplayer. So you'd want to provide a shortcut script, maybe make it interactive… but when does it go from an alias to a new program altogether? This interaction is very intuitive in the browser and I find trying to reproduce it with a CLI tool is quite challenging. Btw I love ripgrep, it made me look very hip in front of colleagues a couple of times.