Alexa Skills - Developer Voice And Vote
Welcome to the Alexa Skills Feature Request site! This site enables Alexa Skills Developers to request and vote on features you’d like to see in the developer toolset and services for Alexa.
To keep this site purpose-driven and actionable, we moderate requests. Here’s some guidance on how to create great feature requests that can be evaluated by our development teams. For conversation, dialogue or help, you should visit our Alexa forums. We appreciate your input.
-Alexa Skills team
-
Enhanced console analytics
Add an all time button to the time interval, the interface is a bit awkward to be able access the data.
As an aid to tracking promotions a since first release stats a first 30 day from release would also be good.
Finally and api to access the analytics would good2 votes -
Customize Dashboard
Custom Dashboard and Status Filter
2 votes -
Intent filter for to skip the match
It is nice to have, inside the Intent editor, a filter that allow the Intent Match to match the intent only if the previous intent was into a list of intents
2 votes -
Post alerts when there are issues affecting large number of users
Post an alert here when you have outage or other issues affecting a large number of users.
2 votes -
deleting an intent should remove required slots from dialogModel
deleted intent with required slots still has required slots in dialogModel
2 votes -
Fix translation
Don't use machine translation to translate the dev interface to other languages. The page on Intent History in the Alexa Console is awful in German and does not make much sense. For example the level of confidence in an utterance (High, Medium, Low) becomes "Vertraulich" in German which happens to mean confidential …
2 votes -
Endpoints per intent
It would be VERY helpful if each intent within a skill can have its own endpoint.
If you have a company that wants several intents under the one skill, but each intent is really quite seperate functionality, you want to be able to call a different endpoint for each intent so that you can have some sanity over your code organisation.
Either an web hook per intent, or a lambda per intent.
Currently you have to but a stack of unrelated code (different intents) into the same lambda.2 votes -
Test 'no response' from user.
It would be very helpful to have a way to mimic 'no response' from the user. If you can do that, it's not obvious how.
2 votes -
German spelling in Alexa Simulator
Alexa Simulator (Test environment) does not recognize correct German spelling and punctuation.
2 votes -
Add Tagging, Grouping and Filtering to ASK Developer Console Skills List
We have over 100 skills in the skills list in the Developer Console. These include public skills that we are publishing for ourselves as well as hosting on behalf of our clients and well as private demo skills for our sales team. This number will easily exceed 200 this year.
The feature request is the ability to assign one or more tags to a skill for use in the Developer Console. These tags would be used for grouping, sorting, and filtering the list of skills in a manageable way. All our own skills would be together, each client would be…
2 votes -
Printing Skill code within JSON editor
Which I'm in the JSON editor (or any part of ASK) can I print the code associated with my skill?
Thanks,
Frank M2 votes -
Missing UI flow in the new beta Alexa Console
If you select 'Measure' for a live skill from the skill list, then go to the Launch tab, you can't edit anything unless you go back to the Measure tab, switch to Development stage and go to Launch again. A stage selection drop-down in the Launch tab would be more intuitive.
2 votes -
Uploading from a GitHub repo in the alexa developer console is tedious
You would think it would be far easier to grab a project from GitHub in the alexa developer console like one button that opens to enter the git url.
Currently these are the steps
Open alexa developer console
Name the skill
There is Create Skill Button top right.
Then again there are other options
Choose a model with seven boxes
Choose a method with three boxes
Ignore all those choices
Press [ Create Skill ]
Next page
Choose a template and 10 more boxes to ignore if you want to import from GitHub
On this page are two boxes top…
1 vote -
Choosing which endpoint to hit in dev console test
As everyone knows, it is possible to assign regional endpoints in dev console for skill, but testing them is really time consuming, because routing is very inconsistent. Even if I am from UK sometimes requests go to US.
Another issue is making sure that all endpoints work. Only way I found to test them consistently is by switching default endpoint, with other regional endpoints to get consistent results, which takes a lot of time.
My suggestion would be, that at least in the dev console, it would be possible to not only pick locale, when testing the skill, but also…
1 vote -
Ability to create sub-accounts within a developer account
For large organizations I would like the ability as a developer to create sub- developer accounts within my developer account so that I can give each of my business units/divisions/affiliates a developer account to work in without them having access to ALL dev and production skills in the account. They should only be able to see the skills they are working on, whereas anybody at the top level account can see everything. This is especially important when a developer account receives a particular agreement/protection (in this case our developer account is protected by a HIPAA Business Associate Agreement (BAA) so…
1 vote -
Provide means for testing headless responses in Dev Console
Currently one can only simulate a device with a display in the dev console. It would be nice if Dev Console provided a means to test a headless response, given that those make up the most significant share of user requests.
1 vote -
Enable change logs for Alexa ASK console and CLI
Access Logs and Change history are needed to effectively monitor the changes done by various users in ASK developer console and ASK CLI. In the absence of the access logs and change history, large organizations with multiple ASK users have no way to track changes to Alexa skill in production. If the administrator of the Alexa account has the ability to view change logs, it will give the ability to effectively monitor user changes.
1 vote -
Enhancements to ASK developer console and CLI/SMAPI User Roles
The current permissions for various roles in ASK developer console and CLI/SMAPI are very broad. Large organizations need more control over roles to effectively manage Enterprise level skills. This feature request is to give organizations the ability to configure granular level access based on the roles as shown below.
Description Administrator Marketer Developer Analyst
Create Skill Yes No No No
Delete Skill Yes No No No
Creating a new
Intent Yes No Yes No
Deleting Intents Yes No Yes No
Modify Existing
intents Yes Yes Yes Yes
Updating
distribution detailsYes Yes Yes No
Skill Submission/Publishing/Hide/
Remove the skill Yes No…1 vote -
Account Linking cannot be removed once enabled in a skill
As the title suggests, we were recently made aware that Account Linking cannot be removed from a skill once enabled. Not even if the skill is removed. As we do not own the login system we were supposed to implement a page which described the 3rd party login system. When we submitted the skill again we were rejected with the following reason: "Please update the account linking URI to include “nosignup=true” as a parameter for suppressing the signup portions of the Spotify page and resubmit your skill." Where is the documentation regarding the nosignup parameter? How is it supposed to…
1 vote -
1 vote
- Don't see your idea?