My list of Alexa Skills is growing unwieldy, with some removed, some in development, some live... would be great to have a "filter" option on the Alexa Skills Kit Developer Console to show only live, etc.

With a push of a button allow people to copy all product information to all English enabled regions. This would cut down on developers having to cut copy and paste saving on average about a half hour of work.
V/R
Nick

The error message "Skill I/O is available only for speech requests to skills you have created". keeps appearing when I am testing a skill that I in fact have created. The most frustrating part is if I was able to see the Skil I/O for the skill I created, I would much better be able to figure out what is wrong with it.

Would be great if you could provide collected information about all my skills in my console, for example how many sessions all my skills together had to handle last month, how many new users activated my skills etc.. I usually just want a quick overview over how my skills are doing and don't want to click through all my skills.

Increase the session time at-least for the developers account. We need to give quality of code right? Some times we may need to debug the code .

"The requested skill took too long to respond"

There is a bug in the new Console. I cannot include both SSML and a question mark because validation says: "You can only have a '?' at the end of a prompt" but for SSML you need to have the closing </speak> tag.

Have a configuration for the REDIRECT_URI to NOT be passed as part of the URL parameters from Alexa Skill linking. Since we know the possible URIs to redirect to, we would keep these URIs in our app configuration to use when sending back instead of getting the URI as a parameter attribute.

The simulator only offers display-based devices to simulate, meaning that multimodal skills that behave differently for display vs non-display devices can't be tested. The "Device Display" menu should have an option for "No display".

Please allow exporting of analytics to pdf file as per the time range (weekly, monthly). We need this to share with clients to showcase how their Alexa skills are doing and they are getting ROI on investment. without this report not many clients would like to spend more time or money on it. Generating this report for every client manually is not possible when we have hundreds of skills. Also it would be great if this report can be emailed to given email id periodically.

For some reason I cannot specify a Lambda endpoint which has an alias qualifier at the end. For example, I want to have two aliases: TEST and PROD that point to different versions of the lambda function.

When I am trying to save the endpoint, it shows a "manifest error" message.

It worked fine before. My other skills that were created using the old developer portal UI still have their endpoint

I have a certified skill, so now have a development copy hanging off it. I messed up the development version hanging off it. Is there a quick way to reset the development version back to the same as the live version to undo all my development changes?

I think it would be great to make a button to do this. Otherwise, I will try to just delete the Interaction Model JSON.

When skill events were originally released last summer, they were only configurable from the SMAPI/CLI. The implicit reason at the time was "there's a new developer console coming, it's not worth it to implement new features on the old one".

The new skill console is out now, and it still doesn't appear that there's a way to set my skill to use skill events.

The ability to export folders/files from Alexa hosted skill

Hello, Alexa can't pronounce the word '&'. It's very frustrating

In alexa-hosted, we can use S3 as persistent adapter although Iin self hosting, DynamoDB seems most popular. but S3 free tier such as 2000 PUTs per month per account is too small as persistent storage and it is totally difficult to use S3 as DB instead of DynamoDB.

In the test simulator, it would be great if "8" would be understood as a spoken word "eight" so I don't have to type a number every time. This took me about 3 hours to figure out / debug a bug in my code that wasn't there.