After a skill has gone live and gets removed, the changes to the skill cannot be made for invocation name. Everything else can be changed except the invocation name. There is document to deal with the error.

If this page is viewed on a small enough resolution, it will cut off the Alexa Client Secret string without any indication to the end user that they need (or even can?) scroll to the right for the complete string.

Suggestion is to either make it explicit that the string is being visually truncated and you need to expand the window, or add a "copy to clipboard" function to eliminate any issues.

add enter button on page when typing msg for alexa on test page.

[vishjain@amazon.com] When you navigate to Certification Tab after making a change in Code or Distribution tab
Expected:
It should launch validation automatically and display only remaining errors after validation checks with new changes.
Observed:
I was been displayed all errors and need to press run to run the validation.

How about creating a way to send certification e-mail to more than one person. This would come in handy when being contracted to do Skill work.

Add the ability to train the Alexa Developer console (currently having issues where it is taking "two" as "nooo")

My desire: An API to upload a CSV to Edit or Upload Sample Utterances in Bulk

My reason: We have a daily update set of ~ 15000 slot values and it would be very helpful if there was an API to automatically update the slot values using a CSV instead of manually updating them.

When on the dev console it is hard to tell if the project you have open is the dev or live version of a skill without going to specific pages and seeing if the save button is disabled or not.

This could be solved by putting this status somewhere on the page. I think this could be done by putting this info (dev vs live) on the dev console's top bar (so you can see it everywhere), and maybe even color-coding the info to draw the eye.

A way to gather Alexa Reporting KPI's like Sessions, Utterances and Visitors without having to log into the Developer Console. Something I could access from an API would be ideal. I'm managing 15 skills and flash briefings and don't want to pull each number manually when it could be easily automated.

The editor should keep the position of where each tab is being edit, so that when we move from one tab to another and then come back to the initial tab, we go to the same place.

I'd like to propose that the name of the skill is shown in a different style, as it's very confusing visually at the moment -- it looks as if it's one of the menu items ('build', 'code', etc.).

If you just changed the colour of the font to, say, blue (matching the Alexa blue), it'd be much, much better.

I've seen that someone posted that they want to see the skill name when editing ("show the skill name when editing"), and that just confirms that the current style is not a good one.

If you can get Audible to slow to 75% why can't you do the same with Alexa?

The analytics tab in the ADC needs to show slot value analytics. If my slot is 'Color' and the slot values are 'red', 'blue', and 'green', I should not have to go to a 3rd party site to see which of those values is accessed the most. It is unreal to me that this is not already in place out of the gate considering Slots has been around.

Switching from one tab to another changes the code collapse.

When use Alexa hosted lambda as backend, it'd be awesome to have log integrate with cloudwatch log, I want see console log and do debug.

I would love to be able keep list of all sentences entered in the "Alex Simulator" so we can select from them.

Right now you always need to copy
/ paste or type the text over and over again.

Thank you
and Warm Regards

It would be cool when a beta test is in progress, that there is an API or similar to give the developer the opportunity to automatically invite beta testers to the test.
Like a user is registering to the beta test and further he will also be added to the beta test for the skill.

make it possible to easily see console output. output of console.log() should be visible somewhere within the UI for debugging purposes on the test screen. Doesn't seem checking device log does that, I don't see anything there even though there is a console.log call in my launchrequest handler.

The alexa developer console would be more helpful if it had the ability to test on a batch of pre-recorded audio files. Since its cumbersome to wait for the Alexa to respond for each query. Instead results could be reviewed at a later time to speed up the process. Also, pre recorded audio files can be modified with artifical noise to see how intents are extracted under various background conditions.