I don't know how hard this is to do differently but I was doing: ``` charmcraft command bad args ``` And then to figure out how to make it better I added: ``` charmcraft command bad args --help charmcraft command --help bad args charmcraft help command bad args ``` But all of them come back with: ``` $ charmcraft upload-resource --help jam-k8s-api-sidecar-test ubuntu ubuntu:latest Usage: charmcraft [options] command [args]... Try 'charmcraft help -h' for help. Error: unrecognized arguments: jam-k8s-api-sidecar-test ubuntu ubuntu:latest ``` I can, certainly run just ``` charmcraft help upload-resource ``` But my natural instinct is to go up one and then add --help to try and figure out what I did wrong. Especially unhelpful is that if I have a correctly formatted command and add --help: ``` $ charmcraft upload-resource jam-k8s-api-sidecar-test ubuntu --help Usage: charmcraft [options] command [args]... Try 'charmcraft help -h' for help. Error: unrecognized arguments: jam-k8s-api-sidecar-test ubuntu ``` It seems the parser looks for help/--help/-h and then switches to the 'help' command, but that doesn't allow you to pass any extra arguments. It might be cleaner if we just change the help command to take any arguments (but ignore them), and then you can actually get the help on a command that you've started writing.