Hardcoded `gpg` command in "keybase/cURL/bash" scripts is problematic

I am not sure how much of a "bug" it is, but it did cause me some head scratching, so maybe it should be at least somewhat documented.
I keep my subkeys on Yubikey NEO, which is not well supported by gpg 1.4. So I have both `gpg` and `gpg2` installed, and `gpg2` _must_ be used to operate my private keys. When I first tried to copy-paste the "keybase/cURL/bash" scripts, I got some errors to the effect of "private key not found", because gpg 1.4 does not have access to the keys on the card. I had to save the commands into a file and change the command name. After that the script worked.
I do not see a "proper" way to fix it, but maybe a hint on the web page that produces the script could help.

Start with the webpage that produces the "keybase/cURL/bash" scripts and locate where the hardcoded `gpg` command is assembled. Review the generated commands and the reported gpg1/gpg2 compatibility problem; done means the page clearly warns users or otherwise addresses systems where `gpg2` is required.

Written by the indexing model from the issue text.