I would like to be able to test new skills on a local server which is only accessible via a public ipv6 address. The domain/subdomain has an appropriate dns entry (AAAA record) and ssl certificate.
As of now, neither the developer console nor a live test with an Echo is able to resolve the domain name.

I originally asked this as a question to the developer support and they suggested to raise the topic here.

CanFulfillIntentRequest should provide some basic context for the user such as (general) location information. My skill is only useful to people in a particular geographic region (the 5 boroughs of New York City). It'd make sense to allow it to fulfill intent requests originating from New York, but not from Chicago. I don't think think there's any way to distinguish at this time.

Similarly to the AcceptGrant Directive. https://developer.amazon.com/docs/device-apis/alexa-authorization.html#acceptgrant

Would be nice to receive an event (DeleteGrant?) whenever the user tap on the disable skill button.

In this way we can clean/free resources on our side too.
Currently the only way to detect that a user had disabled the skill is with the error response from the alexa event gateway.

There are few error types available when replying to an alexa event: https://developer.amazon.com/docs/device-apis/alexa-errorresponse.html#error-type-values

Seems that the error type does not influence the response of alexa to the user..
See: https://forums.developer.amazon.com/questions/176777/smart-home-skill-error-response.html

Please document how alexa will react to each error.

hello when the support of Amazon.Litteral will be done for French Skills ?

The documentation the the customer contact API says to use the following end points "/v2/accounts/~current/settings/Profile.name". A follow up note says: "~current" represents the userId of the current user (account that invoked your skill).

I read that and assume I need to replace "~current" with the userID... which isn't the case (after 2 days of off/on testing).

Additional detail here: https://forums.developer.amazon.com/questions/179334/how-do-you-request-user-contact-information.html?childToView=180317#answer-180317

Lots of us are developing skills behind a corporate firewall. The ask-cli is a great tool that we can't use since most corporate firewall's require the use of a proxy server which is not supported in the cli

I believe there needs to be an equivalent serviceClientFactory call for the customer profile (e.g. - 'serviceClientFactory.getDeviceAddressServiceClient()' is used for device address; I assume 'serviceClientFactory.getCustomerProfileServiceClient()' would be the equivalent for Customer Profile info)

incorporate voice info (ID) into alexa request context.

Currently I wasn't able to find an option to create a smart home device in NodeJS ASK SDK. It only allows to create event handlers. For instance Insteon skill for Alexa allows to create devices that alexa can communicate directly with (i.e. you can ask alexa to turn on light switch derectly without saying: "tell skillname to turn on the lights").

Allow access to Alexa contacts from the skill development environment. so that one can develope a skill around contact search

In order for Echo Show to play videos the Skill needs both the Video Interface and the Display Interface enabled.

It is not explained in the documentation that the Display Interface needs to be enabled for a skill to play a video.

This issue caused a large amount of wasted development time. Please consider changing the Interface descriptions and/or documentation to reflect this.

Thank you,

https://developer.amazon.com/docs/smapi/skill-manifest.html#customInterface-enumeration

This API says "AUDIO" as an option, when it is actually "AUDIO_PLAYER"

Keeping the voice first spirit user's should be allowed to link there Alexa with a skill using just voice. We for example just need an email and name to create account in our system. If Amazon provides an api to send this on fly when user says "yes go ahead link" then we can create an account on the fly and return an accessToken