Skip to content

Alexa Skills - Developer Voice And Vote

Welcome to the Alexa Skills UserVoice site!

This site enables Alexa Skill Developers to request and vote on features you'd like to see in the developer toolset and services for Alexa.

Please bear in mind that this site is for Alexa skill builders, not Alexa users. Additionally, we cannot guarantee each feature request will be implemented but our team reviews each request and sends to the appropriate product teams.
For more information about using UserVoice, please see our blog post here: [Vote on developer features you would like to see at Alexa Skills Kit User Voice]

-Alexa Skills team

Alexa Skills - Developer Voice And Vote

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

132 results found

  1. An issue for larger organizations is the lack of governance around access to the developer console and specific features of the console. For example, I'd like to be able to allow a developer to contribute to a skill or do their own POCs, but prevent them from submitting for certification.

    It would also be useful if SAML auth were supported to allowed for federated access to the console.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Post an alert here when you have outage or other issues affecting a large number of users.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. deleted intent with required slots still has required slots in dialogModel

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Alexa Simulator (Test environment) does not recognize correct German spelling and punctuation.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Which I'm in the JSON editor (or any part of ASK) can I print the code associated with my skill?
    Thanks,
    Frank M

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Very annoying personalization menu during skill testing.
    Therefore, the skill confirmation screen is as narrow as the pocket-handkerchief garden.
    Remove personalization menu from the test screen.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. While the Interaction Path in the dev console is very handy it does not include APL interactions. More than half my users use the Show and I'd like to see what buttons they press.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. I am a totally blind software developer and I want to learn how to develop Alexa skills. On the developer console when I go to create a new skill and enter the initial information about it, there is a visual only CAPTCHA to resolve before I can create the skill. I can't see the images so can't complete this CAPTCHA. Other CAPTCHAs I've found on Amazon have an audio option which is very good.

    Can we have an audio alternative on the CAPTCHA please when creating a new skill. Better still, maybe no CAPTCHA at all. After all, whoever is…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Is it possible for you to create a counter for tracking sobriety dates or when you quit smoking?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Be able to put in breaklines in ISP JSON file for long descriptions. It works when you edit the skill.json file when you write content in the Description box on your skill so the same should be applied for description boxes of an ISP product.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    1. Open alexa developer console

    2. Name the skill

    3. There is Create Skill Button top right.

    Then again there are other options

    1. Choose a model with seven boxes

    2. Choose a method with three boxes

    3. Ignore all those choices

    4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?