I'd like to up-vote this request. I do understand the reasons why changing the name is discouraged for live skills. But it would be helpful for some cases. Let's say, for example, that you have published a skill with a certain invocation name and discover later that name is problematic...perhaps it is commonly misheard by Alexa (my situation) or potentially conflicts with another live skill. You come up with a new, better, and less problematic invocation name. But the only option currently is to abandon the previously deployed skill and redeploy with a new invocation name. It would be helpful if you could change it to remedy the issue. Maybe limit it to one name change per live skill so devs don't abuse this option and maybe force it through certification again.

Since invocation name is editable the Automated ASK-CLI errors being thrown which say "you cannot change the invocation name of a live skill" were unexpected and problematic for our design process

Our Preprod live skill is used for testing live features across our large audience. This includes collisions and VUX design which includes the invocation name. Our inability to change the live invocation name of our User Acceptance Testing skill is a major hindrance.

This behavior should be default. Perhaps the idea was consistency for live skills helps users but that's not the case. It's even more confusing to our users when we cannot change the invocation name to account for collisions with other Alexa features.

I do not understand how this is not the default behavior. Is such a simple thing and they still manage to ***** it.

Also the field for the invocation name is modifiable, so it causes a lot of confusion about the possibilities of changing the invocation name.