Gems are done. Google is retiring Gemini’s custom assistant feature and folding it into something called “skills,” with automatic migration starting November 17, 2026. Until then, your Gems keep working and you don’t have to touch anything.
I’ve built a fair number of Gems. Some for client work, some for internal tooling, one embarrassing one that just reformats my meeting notes. So my first reaction wasn’t panic about the migration. It was a groan at the invocation model.
The slash is the story
Skills don’t work the way Gems did. Instead of opening a dedicated assistant and chatting with it, you type a forward slash in a thread and pick the skill you want. That’s the whole interaction change, and it’s bigger than it sounds.
A Gem was a place you went. You opened it, you were in context, and everything you typed inherited that context. A skill is something you summon. You’re in a general thread, and you reach for a tool mid-conversation.
For builders, that second model is arguably better. It matches how we already think about tool calling. You have one agent loop, and it pulls in capabilities as needed. If you’ve wired up function calling in any SDK, skills will feel familiar — discrete units of behavior, invoked when relevant, composable inside a single session.
For normal humans, it’s worse. Nobody’s mom types a forward slash. The all-in-one chat agent won out on consumer surfaces for a reason: you just talk to it. Meta’s Muse leans hard into that, and next to it, a slash-command menu reads like a Discord bot from 2019.
Why I think Google went this way anyway
Skills arrived alongside Gemini Spark, which suggests this isn’t a Gems replacement so much as a consolidation. Google appears to be picking one primitive for “custom behavior attached to Gemini” and standardizing on it across products. Gems were the consumer-facing version of that idea. Skills look like the general version.
That’s a defensible engineering call. Two competing abstractions for the same concept is a maintenance tax and a documentation nightmare. Anyone who’s shipped a platform knows the pressure to collapse them.
The cost is that Google has done this often enough that it’s a pattern now. Features get renamed, merged, and re-scoped, and the product name you learned last year isn’t the one you use this year. If you write tutorials — which I do — you feel this acutely. Half of documenting Google AI tooling is documenting what things used to be called.
What this means if you build on Gemini
Practical read, based on what’s been announced:
- You have until November 17, 2026. Gems keep working until they migrate. No action required before then, per Google’s in-app notice.
- Migration is automatic. Google says it will move your Gems to the new format for you. That’s the good news and it’s genuinely good — nobody wants to rebuild thirty custom assistants by hand.
- Automatic doesn’t mean identical. Whenever a feature changes its invocation model, prompts tuned for the old surface behave differently on the new one. I’d plan to re-test anything load-bearing rather than assume it survives the move intact.
- Document your Gems now. Not because migration will fail, but because having your instructions in a file you control is just good practice. If you’re relying on a vendor UI as the only copy of your prompt, that’s a single point of failure regardless of what Google does.
There’s one open question worth flagging: what happens to free-tier users. Nothing in the announcement says free accounts lose access, so I’m not going to claim they will. But the shape of these transitions historically involves some capabilities landing on the paid side, and it’s the thing I’d watch for as November approaches.
My take
I’m mildly annoyed and mostly fine with it. The slash-command interface is a step backward for casual users and a step sideways for builders, which means the people most inconvenienced are the ones least equipped to adapt. That’s a bad trade, even if the underlying architecture is cleaner.
But the migration is automatic, the runway is long, and the new primitive is closer to how agent systems actually work under the hood. If Google uses this to make custom behavior more composable — skills that chain, skills that call other skills, skills that work across surfaces — the naming churn will have bought something real.
If it’s just Gems with extra keystrokes, that’s a different conversation. We’ll know more when people start building on it in volume.
For now: write your prompts down somewhere safe, mark the date, and keep shipping.
🕒 Published: