provide an option to initiate alexa to alexa call/message from a skill itself

provide the original text as well, along with the intent

Have access as a developer to the full list enabled skills that a user has added to their Alexa device.

There might be use cases where a developer is dependent on another skill and wants to check if its active or not.

GET request /user_skills

\ TuneIn, Dominos, FitBit enabled

Currently I can quickly run tests of my code in development, but I'm now adding more <audio> tags in my SSML, and when I run the replay, all I see is <Short audio> What I'd like to see is <Short audio: door_opens.mp3>, etc. Just pull the last fragment of the URI and display it in the tag (e.g /([^/]+)$/ = everything in the uri after the last forward slash.)

Otherwise, I can't automate any tests that require verifying the audio files in my ssml are right for the current context.

Expose the same API in the ASK SDK that the Simon Says Skill has access to. Using AMAZON.SearchQuery does not cut it for messaging and social media type skills.

Thanks

The programmatic access to the device info data would open new opportunities for business that serve the customers through Alexa.
Also, it would allow to access the data about the environment in which the device is operated.

Many large companies have or utilize third party voice authentication mechanisms to provide voice auth across a number of channels (e.g.,IVR, mobile app). While voice profiles are available through Alexa, is it possible to have an option to reuse existing third party voice auth APIs companies have invested in already within Alexa Skills?

According to the docs, APL Text items support some HTML-like markup, with a custom escape method for special characters:

https://developer.amazon.com/docs/alexa-presentation-language/apl-text.html

There should be a function in the SDKs that we can use for escaping a plain text string, to display it as-is.

Also, the chart under "Markup characters in text must be replaced with character entity references" is a little confusing. E.g. what are we supposed to replace &, <, and > with?

To avoid having ask-cli installed globally which is not good when working with other developers together who might have version mismatches, it would be nice when you could trigger ask commands with npm scripts.

For example:
package.json:
"scripts": {
"validate": "ask validate"
}

Currently this throws errors like described here:
https://forums.developer.amazon.com/questions/211596/run-ask-commands-as-npm-script.html?childToView=212326#comment-212326

via some script we hit an api for a specific user that is in front of line and Alexa responds with example speech.

"Hi Jhon, welcome to Demo clinic"

or
"Hi Dave, welcome to Demo clinic"

I'd like to have a Lambda Layer for the ASK SDK Python available also in Europe region. Today it is available only in US.
See also here for reference: https://github.com/alexa/alexa-cookbook/blob/master/resources/lambda-layers/ask-sdk-lambda-layers.md

Can we have a command line version of the Test console? Right now, ask-cli only works with custom skills and not smart home skills.

It would be useful to permit the passing of Lambda Environment Variables as part of ask cli (and IDE plugins) configuration - OR - To bind the ask cli features as part of AWS SAM.

The JSON editor should have undo back to the last "no big red x" version in a single click. That way after I spend a bunch of time trying to figure out what it is unhappy about I can start again from a known good place with a single click.

Actually we can create and deploy javascript alexa skills, it would be great if we can do with typescript too.

I think it's not so hard to add typescript support (transpile before deploy)

Add the ability to download the code in one easy zip file, or provide some basic version control, so this https://forums.developer.amazon.com/questions/202617/alexa-hosted-skills-undo-commands.html doesn't happen

Enable the utterance profiler for speech. My experiences using the profiler is that it gets typed utterances correct. However the problems occur during speech. I would like to see the various intent considerations.

I want you to develop Alexa so that you can understand Chinese that is said to be more than 100 million native speakers.
I fully understand that Alexa can not sell in China. I think that it is not a good idea to remove Chinese speakers living in the world from business.