For 1, I do agree that the term is overused, but in this case it's not really about the beauty of the code itself: it's about the fact that the final generated

For 1, I do agree that the term is overused, but in this case it's not really about the beauty of the code itself: it's about the fact that the final generated script acts in a predictable way and prints information and help messages in a format that people are already familiar with. You don't have to write your own usage message: it does it for you, and it looks the way I would expect a usage message to look. I also see argument 2 a lot, and I've already addressed this in other comments, but sometimes you really just need to call a couple of commands while prepping some env vars or config files for convenience. In those cases, reaching for Python or Go ends up being a lot of boilerplate for very little advantage, especially when you want to pass control over to other applications once you're done setting things up.