In node.js if a user disables your skill, the framework should delete the persistent info record from the DynamoDB stream for the alexa skill automatically. Why leave dead data in my persistence store? The user has decided to disable the skill. It even gives you a warning that it will remove information but it's not deleting it from my dynamo db stream.

I had posted this previously but it seems to have disappeared?

With the SmartHome SDK there is a need to prevent users accessing interfaces that are not in specific regions. For example, an Australian customer accessing the US endpoint may or may not have access to the SceneController capability or the TemperatureSensor capability.

This is controlled at a level below the specific Alexa Gateway as some gateways only support some interfaces in some languages. We need a mechanism to identify which interfaces are supported.

Currently the ASK SDK for Python supports data persistence using DynamoDB and it is recommended to use it, however, to expand some capabilities that only S3 can provide is a great alternative. the SDK for NodeJS already includes support for this officially. Not sure if this can be useful, I have implemented it and the information can be found here https://github.com/frivas/alexa-s3-persistence-python

I hope you find it useful.
Thank you very much.

JSON is great, but YAML is way easier. Especially the configs for models can be quite long and the ability to add comments in YAML would really make it easier to read.

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.

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

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)

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

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