Introducing SkillDevs.io: A Community-Driven Initiative for Alexa Skills

Why we built a public issue tracker for Alexa Skills, how it works, and how you can participate in making the Alexa developer experience better for everyone.

SkillDevs.io is a community initiative of Alexa developers and businesses, including participants directly affected by the ecosystem issues discussed here. It is not affiliated with or endorsed by Amazon.

SkillDevs.io is a community-maintained issue tracker for Alexa Skills in Alexa+, run by Alexa developers and businesses with direct exposure to the conditions it tracks. The GitHub issue tracker is where they report what they observe, upvote what affects them most, and follow progress alongside Amazon.

It exists because the ecosystem that took a decade to build has, over the last year, tightened across nearly every surface independent Skills depend on, in ways that affect Alexa+ customers as much as the developers who serve them. Until SkillDevs.io, no shared, public place to surface and track those conditions existed. The goal is constructive: make these conditions legible enough that Amazon and the developer community can work through them together.

What's Happening on Alexa+#

The last twelve months on Alexa have looked different from the decade before them. The pivot to Alexa+ has been accompanied by a measurable tightening across nearly every surface independent Alexa Skills depend on to reach customers.

Discovery has narrowed. Skill listings have been deranked across multiple surfaces in the Alexa+ mobile app and on Echo Show widgets, with first-party experiences in the same categories continuing to enjoy prominent placement. Developers report that natural-language phrases that previously reached ambient and audio Skills increasingly route to Amazon first-party offerings instead. The current invocation grammar remains undocumented, with questions pending for over four months.

Retention paths have eroded. The discontinuation of the Alexa Routines Kit (ARK) on May 13, 2026 removed the most documented mechanism for embedding Skills into customer routines, with no announced successor. Skill Quality Coach and Utterance Profiler, the developer tools that supported quality and engagement, have been wound down in the same window.

Monetization has dropped sharply. The In-Skill Purchase checkout now takes three confirmation steps where it once took one, with conversion falling to between 2% and 5%. Comparable first-party purchase flows on Alexa+ appear materially less friction-heavy.

The migration story has not been published. Alexa+'s next-generation capabilities, surfaced as "add-ons", remain restricted to invite-only partners selected by Amazon. The 100,000+ Skills built under the legacy framework continue to operate under the tightening conditions above, without a clear path to the upgrade.

What This Means for Customers#

Customers experience these changes without an explanation attached. The phrases they used for years route to different offerings than they used to. The Skills they enabled and built habits around no longer answer the same way. Customer journeys increasingly appear to favor first-party experiences by default, yet their depth and range do not always match what they replaced. The cumulative effect is a quieter narrowing of choice, harder to see in any single moment but visible in aggregate.

Our post Counting the Days: What Alexa+ Customers Experience While Alexa Skill Issues Remain Unresolved documents this customer-side impact in detail, in customers' own words, with live counters tracking how long each open issue has remained unresolved.

Where Customers Can Find Help#

The tracker answers a question Alexa developers ask: what has changed across the ecosystem, and how long has it been open. Alexa+ customers arrive with a narrower one. Their Alexa Skill stopped working the way it used to, and they want to know what to say instead, tonight.

SkillUsers.io is the customer-facing half of the same initiative, run by the same people, under the same disclosures. Its help pages carry no developer vocabulary and no ecosystem analysis. A customer types what they say to Alexa, for example “open sleep sounds”, and gets a page about that Alexa Skill: why the request may be going somewhere else, what phrasing tends to work today, and when the answer is honestly that nothing on the customer's side changes it. Alexa developers can send that link to their own customers instead of writing the explanation themselves.

The two sites share this blog, so a post reads the same on either one. They do not share their purpose. SkillDevs.io documents conditions and tracks them over time. SkillUsers.io helps one customer with one Alexa Skill, today. Neither replaces Amazon's own support channels, and both point customers to them for anything involving an account, a device, or a charge.

What This Means for Alexa Developers#

For the developers who built that catalog, the conditions to keep serving customers have tightened in parallel. Unresolved Skill bugs persist across multiple monthly reporting cycles. Tools that supported quality, engagement, and routine integration have been deprecated without replacement. With reduced discoverability, eroded retention mechanisms, and monetization at a fraction of its prior viability, the operating environment for long-standing third parties has visibly shifted. Without trusted ecosystem conditions, fewer developers invest, fewer differentiated experiences survive, and customer choice tightens in turn.

How to Participate#

The community issue tracker is where Alexa developers can report issues, request clarification, suggest improvements, and upvote the items that affect them most. This is not a replacement for Amazon's official support channels; it is a complement to them, a shared public view of what is happening, prioritized by the people experiencing it.

A first set of nine structured questions about Skills in Alexa+ has been shared with Amazon and remains open. Monthly progress updates capture what has moved and what has not, posted publicly and sent to Amazon leadership at the same cadence.

If you build Alexa Skills, your observations help complete the picture. Reporting, upvoting, and sharing the tracker with your network all add to the visibility this initiative is here to support.

Alexa developers can start at the issue tracker or on the SkillDevs.io homepage to see the latest open issues. Alexa+ customers looking for something to try can start at SkillUsers.io.