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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add Social Media account linking in the Alexa App for all skills to use

    Allow users to link their social media accounts (Facebook, Twitter, Instagram, etc) in the Alexa App itself. Then allow skills to query which accounts are linked and request permission to use those links, without requiring each skill to perform account linking separately (and perhaps not even exposing the account details to the skill, for greater privacy!).

    This would allow a skill to request permission to post to Facebook, for example, to share their new high score. The skill would request this permission at the time of the interaction, and the approval would be delegated to Amazon's built-in handling (to make…

    15 votes
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow developers to choose just-in-time permissions

    Today, there are two ways that a user may be asked to grant permissions to a skill: At the time they enable the skill, and when the skill returns a Permission card with its response. For a developer of a skill that uses permissions, the second of these approaches is optional, and entirely controlled by the skill. The first is mandatory, and completely out of our control.

    As a developer, I would like the ability to configure whether any individual permission is prompted for upon skill enablement (and concordantly, whether a permission upsell is triggered when voice enablement is used).

    8 votes
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  3 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  3. Respond only to Administrator / Account Holder and/or delagated learnt voices

    Some people seem to enjoy annoying Alexa during parties, sometimes adverts on TV activate Alexa, and sometimes friends discussing their Alexa accidently get overheard.
    A simple, switchable security measure regulating who would be recognised would be nice to have, and even more if this would be part of the „Voice learning process“
    A switchable Administrator/Account Holder only, Household Members, and everyone would probably suffice.

    5 votes
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  2 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Option to eliminate 8-second time-out constraint

    Currently (10.2018) there is an 8 second timeout for Custom Skills that is standard across all interactions and isn't customizable.

    We are aiming to develop a skill that would allow users to opt-in to a skill that is not constrained by time. I.e. the skill will be designed to listen for an unlimited amount of time.

    The application for an unlimited amount of time is educational: for families with children with learning disabilities or language development issues there is an opportunity for specialists to be able to measure and analyze a family's "language environment" by using Alexa. Specialists would be…

    5 votes
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  1 comment  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add Additional Permission Scopes To Alexa Response

    Currently an Alexa response includes permission scopes for "payments:autopay_consent" and "alexa::devices:all:geolocation:read" if the Skill manifest requests those permissions. The status will either be "GRANTED" or "DENIED". If "DENIED" the Skill can request the user enable the permission. However, for all other permissions such as "alexa:devices:all:address:country_and_postal_code:read" or "read::alexa:device:all:address", there is no permission scope provided and the only way to check for the permission is to actually attempt an operation that requires the permission and see if it fails. I would like to request that all permissions requested by a Skill be included in the permission scopes as either "GRANTED" or "DENIED"…

    2 votes
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  6. Skill Access Controls within Alexa developer console

    I'd need more granular access control for different Alexa Skills published under the same Amazon developer account. This seems to be in place already for AVS according to this blog post https://developer.amazon.com/blogs/alexa/post/b82c72ff-0534-41ee-8c6f-b46c45771ad2/introducing-product-access-control-for-the-avs-developer-portal

    however for Alexa Skills Kit I cannot find a way to limit access for a single Skill, right now if I add a user to the developer account that individual can see analytics of all the Skills.

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  7. Get list of permission granted by user in the request json

    Firing an API just to know if required permissions are granted just adds to the latency and complexity of the whole process. Instead, we should get the list of permissions granted by the user in the request sent by ALEXA along with the other details.

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  8. Manage Music in Alexa for Business

    As a business, being able to turn off access or manage per device/room to playing Music when devices in open areas.

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  9. log out of unsatisfactory skills

    Many skills perform the same tasks, some better than others.
    Trying different skills is okay.
    When skills are disabled they are still used (linked).
    No way to stop old skills from interference. thanks

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  10. Give the ability to cache files on the user's device or account

    Give the ability to cache files on the user's device or account.

    I'm making a skill that involves playing a large sounds file for the user. The bandwidth charges for this can get pretty high and if a lot of people are using the skill response can get slow. It would be great to be able to cache the file so after they play it the first time it plays locally.

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make skill permissions configurable per locale

    Today, skill permissions (push notifications, device location, etc) are configured for a given skill on a global basis - if I turn on list management permissions to use with en-US, it will be enabled for every language model my skill implements. This doesn't mean that I have to use those permissions in every locale - it's still up to my skill to choose when to take advantage of them. But it does mean that users will be prompted for them.

    This is a problem for a couple reasons:
    1. As a developer, I may have legitimate reasons for not using…

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  12. Change "Permissions" nav menu button to "Your Users"

    Change "Permissions" nav menu button to "Your Users"

    In the Alexa Console, the "Permissions" button in the left menu makes me think I can provide permissions (e.g. beta testers and administrator access) to the particular Alexa Skill, not user's access to addresses and read/write lists. Might make sense to change the wording to "Your Users" that way the submenu can contain all info pertain to your uses using your Skill and "Permissions" is uses to give certain permissions access to the app on a tester, administrative, business user or marketing permissions to the Skill

    I'm assuming this feed back forum…

    1 vote
    Sign in Sign in with: Amazon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base