Google Gemini Gems become Skills on 17 November 2026, and the interface changes from a menu to a slash command
TechCrunch reports that Google will turn every Gemini Gem into a Skill on 17 November 2026, migrate the two automatically, and switch the way users pick one from a dedicated menu to a forward slash typed into the task thread.
Image: TechCrunch
Why it mattersAny team that built a Gem for a repeatable workflow has seven weeks to plan the interface change, test that the migrated Skill still behaves the same, and update whatever instructions or training material tells staff how to reach it.
Any team that built a Gemini Gem for a repeatable workflow has seven weeks before the way staff reach it changes. Google will turn every Gem into a Skill on 17 November 2026, migrate each one automatically, and swap the interface at the same time, TechCrunch's Sarah Perez reported on 28 September, citing a warning message now shown inside the Gemini app.
A Gem, launched in 2024, is a saved instruction set with its own screen inside the Gemini app that a user picks before a conversation starts. A Skill, in Google's newer format, sits behind a forward slash typed into the task thread itself. On the day of the switch, every Gem becomes a Skill under the same name and instructions, according to the TechCrunch report, and no user action is needed to keep one.
Three things a Gem user does today that a Skill user will do differently
The prompt and the name travel with the account, and Perez quotes Google's own line that "it will migrate the Gems to the new format, so users won't have to do anything to make the transition." Three things do not travel automatically, and each one costs a small amount of setup on 17 November or shortly after.
The path to the Skill. A Gem lives on a screen a user picks first; a Skill is reached by typing a slash into the ordinary task thread and choosing from the list. Any staff document, training video or team wiki that describes how to open the Gem needs a rewrite before the switch.
The Skill's behaviour on the same prompt. A prompt written for a Gem screen may treat the surrounding conversation differently than the same prompt reached through a slash. TechCrunch's report describes the migration in terms of the prompt and the format alone, so a working team should paste the same test prompt into the migrated Skill on 17 November and read the answer against the previous one.
The default assumption when the interface changes. TechCrunch's own framing calls the slash interface "less consumer-friendly" than the all-in-one Meta Muse or Instinct agents where a user just types text. A colleague who used the Gem menu without thinking will now have to know the Skill's name and remember to type the slash first.
The change lines up with Meta Muse and Instinct, and copies their single entry point
Perez frames the change against Meta's Muse and Instinct, which she describes as all-in-one agents taking off in the same period. Skills give Google one entry point that already covers other things a Gemini user might do, and merges a purpose-built prompt into that entry point rather than keeping it on a separate screen. She reports the change was first noticed by 9to5Google over the weekend of 27 to 28 September, from the notification message inside the app rather than a public Google blog post.
The pattern is a familiar one for teams that already run Gemini in a workflow. The interface change lands on 17 November, the prompt travels with it, and the only real work is on the muscle memory and the instructions written for people who never saw the change coming. Seven weeks is a long enough window to plan it, and short enough to start today rather than in November.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
