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
-
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…
16 votes -
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…
11 votes -
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 -
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.
6 votes -
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.6 votes -
Add Additional Permission Scopes To Alexa Response
Currently an Alexa response includes permission scopes for "payments:autopayconsent" 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:countryandpostalcode: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…
5 votes -
Turn off microphone during specific hours, and create command which would turn off mics on all of my Echos
I would like the ability for some of my echos to turn off microphones during certain hours - I do not wish for amazon to listen to me. Or perhaps make an option for saying "privacy mode" and all echos mics are turned off. I have a number of echos and I am thinking of getting more to improve Alexa's reception and improve the sound in the room. However, occasionally I need privacy and I have to go around turning off echos' mics. So that is stopping me from getting more of them.
4 votes -
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.
3 votes -
Allow all members of Amazon Household to cast to Echo
Currently, the Echos have to be linked to an account (which is fine), however, only devices logged into that account are able to cast to an Echo from Amazon Music on iOS/Android.
I have 5 Echo Devices, all linked to my own account, though, I have an Amazon Music Family Subscription and my account is also the Primary Account of Amazon Household.
My suggestion is that any other accounts linked by Amazon Household to the account used on the Echos should be able to cast to those devices too... in fact, my suggestion is that the other Adult Account in…
2 votes -
alexa ring light modification with code
If we can handle alexa ring light color with code modification. blinking light with sound etc.
2 votes -
Allow scheduled sleep of Alexa and timed reenable
Allow a command to put Alexa to sleep for spoken time or schedule her as well.
Example, Alexa Sleep for 30 minutes, alexa will no longer respond to commands for 30 minutes. I would still want her to be accessible from the app.
Also, Alexa go to sleep at 1:00 p.m. for 30 minutes.
So same thing but at 1:00 p.m. she goes to sleep.
This may be alarming to some users, if they do not know it is asleep so also allow it to be unplugged and turned back on without this enabled.
The reasons I am suggesting this,…
2 votes -
Provide an API to get alexa user id using Alexa skill client
Our service needs account linking to work. Implementing OAuth2 is a lot of work. Using LWA is awkward since the user has already signed in Amazon and also requires the user to LWA in our app again. Using user's email is another way to do it, with the same down side that the user has to LWA in our app. All these force users to give up information that's is not really necessary.
I propose to let apps use Alexa user id to authenticate the user. This way users don't need to do anything on Alexa side besides enabling our…
1 vote -
Allow non-kids skills to be whitelisted by parents
whitelist skills on kids edition echo dot
1 vote -
Add Required/Optional Labelling to Requested Skill Permissions
Two of the permissions our skill requests are not strictly required to use the skill. We request either Location Services or Device Address permissions, depending on a user's device, to improve the experience of searching nearby.
It would be nice if we could add an indicator under the "Manage Permissions" section of the skill settings to let a user know which permissions are optional and which permissions are required to use our skill.
1 vote -
Change Order of Requested Skill Permissions
It would be nice to control the order in which permissions appear under the "Manage Permissions" link for an Alexa skill. More important permissions that a user must grant for a better skill experience should be listed first.
Currently, the order of requested permissions is fixed as:
- Device Address
- Customer Name
- Customer Email Address
- Customer Phone Number
- Lists Read
- Lists Write
- Amazon Pay
- Reminders
- Location Services
1 vote -
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 -
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. thanks1 vote -
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 -
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 -
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
- Don't see your idea?