November 17, 2026. That’s the date Google has quietly stamped on the death certificate for Gems, the custom assistant feature it spent the better part of its Gemini marketing push teaching people to care about. On that day, Google begins automatically migrating every Gem into something called a “skill.” You don’t have to do anything. You also don’t get a vote.
The notice is showing up inside the Gemini app itself, warning users that Gems become skills starting on that date, and that you can keep using your Gems right up until they migrate. As breakups go, it’s polite. As product strategy goes, it’s the same move Google has made so many times that regular users have stopped bothering to learn the current vocabulary.
What actually changes
The mechanics matter more than the branding here, and this is where I’d push back on anyone calling this a lateral move.
- Gems were standalone custom assistants. You made one, you opened it, you talked to it.
- Skills live inside a chat thread. You type a forward slash, pick the one you want, and go.
Skills arrived alongside Gemini Spark, so this isn’t a feature invented purely to replace Gems. It’s an existing format that Gems are being folded into. Consolidation, not creation.
That forward slash is doing a lot of quiet work. It’s a power-user convention borrowed from Slack, Discord, and every dev tool built in the last decade. If you already live in those apps, it’s muscle memory. If you’re the kind of person who opened Gemini because a coworker said it would help write emails, a slash menu is a wall. You have to know the thing exists, know it’s hiding behind a keystroke, and know what it’s called. Nothing about typing punctuation to summon a hidden menu says “just talk to me.”
The direction of travel is backwards
Compare this to where the rest of the space is heading. Meta’s Muse sells the opposite pitch, one agent, one conversation, no menus, no modes, no syntax to memorize. The bet there is that people don’t want to manage a toolbox. They want to describe a problem and have the software figure out which tool applies.
Google is betting the other way, that users will happily curate and invoke their own capabilities. On paper that’s more powerful. In practice, discoverability is the entire game for consumer AI, and a slash command is the least discoverable interface pattern available short of a config file. People who would have used a Gem because it was sitting there in a list may simply never find its replacement.
I want to be fair about what’s unconfirmed: Google hasn’t detailed what skills can do that Gems couldn’t, and there may be real capability gains hiding behind the rename. If skills can chain, share context across a thread, or combine with each other mid-conversation, that’s a genuine upgrade and worth the friction. Nobody has shown that yet. Right now all anyone can point to is a migration date and a new noun.
The rename treadmill
This is the part that should bother you most, and it has nothing to do with slash menus.
Google has a long-running habit of rebranding and merging features instead of letting a product name sit still long enough to mean something. Gems were introduced, promoted, explained in help docs, written about in tutorials, and built into people’s workflows. Now they’re skills. Every blog post, internal wiki page, onboarding doc, and YouTube walkthrough that mentions Gems is now subtly wrong, and the people who wrote them get to do the work again for free.
There’s a real cost to this that Google’s internal metrics probably don’t capture. Trust in a feature is built on the assumption it’ll still exist under the same name next year. Teams that standardized on Gems learn the lesson that investing in a Google AI feature is a temporary arrangement. Do it enough times and users stop customizing anything, because why bother configuring a thing that gets renamed out from under you.
What to do before November
Practical advice, since that’s what you came for:
- Keep using your Gems. They work until they migrate.
- Write down what each one does and what prompt or instructions it contains, somewhere outside Gemini. If migration mangles anything, you’ll want the source.
- Learn the slash flow now if you’re on a version that already has skills, so you’re not relearning your own setup on migration day.
- If you’re a free user, watch this one closely. Google hasn’t spelled out how the migration treats free versus paid tiers, and that’s a gap worth getting an answer on before the date rather than after.
Gems weren’t beloved. Most people never made one. But the way this is being handled tells you something about how much weight to put on the next feature Google announces with a capital letter and a friendly name. Learn the slash, keep your prompts in a text file, and hold your product loyalty loosely.
🕒 Published: