On 28 September 2026 Google confirmed, via in-app Gemini messages, that the feature known as Gems will end as such on 17 November 2026. Per TechCrunch and The Verge, users’ invested work will not be destroyed: Gems will be automatically migrated into “skills” reusable across different AI tasks.
Launched in 2024, Gems let users teach the assistant to perform specific tasks without repeating instructions—learning coach, coding partner, career guide, editor, or custom builds such as a running coach or vacation planner. They could also be shared, part of Google’s bid to virally grow Gemini against ChatGPT and Claude.
The new skills format keeps custom instructions but changes the interaction model. Google says users will type a forward slash “/” in a task thread to select the desired skill—an interface TechCrunch describes as closer to engineers than to consumers who only type natural language.
The contrast with Meta is explicit in coverage. Muse and Instinct are sold as agents that take free-form text and act; Gems, even as skills, remain modules the user must invoke. Google stresses that prior work is preserved and that Gems remain usable until the cut-over date.
9to5Google had previewed the wind-down over the weekend; The Verge confirmed it on 28 September with screenshots of the in-app notice. No successor product branded “Gems” has been announced—only unification under skills inside Gemini’s broader agentic strategy.
For enterprises and educators who distributed shared Gems, automatic migration lowers friction but forces habit change: document the “/” command, update onboarding materials and verify that permissions and connectors still apply after the format shift.
Timing matters. September 2026 is defined by autonomous-agent incidents, model cancellations and a race of “super app” interfaces. Google is betting on modular composition—invocable skills—against the single assistant that imitates the user, the pattern Meta’s Muse has taken into marketplace flows and privacy controversy.
Product questions remain. Will migrated skills retain memory and few-shot examples with the same fidelity? Will they still be shareable via link? Will Workspace admins get analytics to measure adoption after 17 November?
Competitively, killing Gems as a brand can be read as an admission that the “named assistants” metaphor did not scale against continuous chat. At the same time, skills align Gemini with developer-agent patterns (slash-commands) already familiar in Cursor, Claude Code and Copilot.
Power users may gain if skills integrate better with multi-step flows and tools. Casual users—the segment Google hoped to win with prebuilt Gems—may feel a step backward if they must remember syntax instead of picking an avatar or a name.
Neural Pulse advises writers and teams that depend on Gems to export instructions today, test the migrated skill in a trial thread and note differences in tone, allowed tools and context limits before 17 November, when the switch ceases to be optional.
The close is pragmatic: Google is not abandoning personalisation; it is repackaging it under an engineering metaphor. Success will be measured in post-migration retention and in whether Gemini makes “/skill” feel as natural as typing “help me with this” to an all-in-one agent.
