Gemini Gems Become Skills on November 17: What Users Need to Know
2026-09-29
On November 17, 2026, Gemini Gems automatically become skills. Here's how the migration works, what changes, and what happens to your custom instructions.
Google is retiring Gems, the custom assistant feature it introduced in 2024, and replacing them with something called skills. The Gemini Gems skills switch happens automatically on November 17, 2026, and if you've built a handful of Gems for work or hobbies, you won't have to rebuild anything. Google says it'll migrate each one for you.
That's the reassuring part. The less reassuring part is what changes about how you actually use these assistants once they become skills. Here's the full picture, starting with what's happening and ending with what you should do before the deadline.
What Google Gemini Skills Means for Your Gems
Gems were Google's answer to the problem of repeating yourself. Instead of re-explaining how you want your AI to respond every time, you'd spin up a custom version of Gemini tuned for a specific task. Google shipped premade ones, including a learning coach, a brainstorming assistant, a career guide, a coding partner, and an editor. Users made their own too, everything from a running coach to a nutritionist to a vacation planner, and could share them with others.
Once November 17 rolls around, those Gems become skills, and the work you put into them carries over. The Gemini app is already showing a banner at the top of the Gems manager: "Gems will become skills starting Nov 17, 2026." You don't need to export, rebuild, or re-tune anything.
The Gems themselves stay usable right up until the switch, so there's no reason to abandon them early. Keep using them as normal until the transition.
How the Gems to Skills Migration Works
The migration is automatic, and that's the whole point. Google is folding Gems into the broader skills framework rather than asking users to start from scratch. Your existing custom instructions survive the move.
What changes is the category. Gems were a standalone feature with their own manager screen and their own identity in the app. Skills are a wider concept, meant to be things Gemini can reach for across different tasks rather than a separate destination you visit. In practice, your old Gem stops being a place you go and becomes a capability Gemini can apply.
That shift explains why Google bothered to rebrand at all. A shared framework is easier to extend than a stack of separate features, and skills can be combined in ways single Gems couldn't. For a user, the payoff is supposed to be more flexible automation. For Google, it's a tidier product with fewer names to maintain.
Google hasn't hidden the reason for the shift. The company is consolidating features as all-in-one AI agents from rival labs gain traction, and Gems-as-a-brand was one of several naming experiments Google ran in the AI era. Folding Gems into skills trims the app's navigation and reduces the number of distinct product names users have to learn.
What Changes About Using Your Custom Assistants
Here's the adjustment that'll annoy some users. Skills aren't invoked the way Gems were. Instead of tapping into a Gem from a manager, you select a skill by typing a forward slash, "/", in a task thread. That's a keyboard-driven interface, and it's more at home in a developer tool than in a consumer chat app.
If you liked the tap-and-go simplicity of Gems, the slash command will feel like a step backward. If you're comfortable with shortcuts, it's faster once you're used to it. Either way, it's the single biggest day-to-day change, and it's worth practicing before November 17 so the switch isn't jarring.
A second change is flexibility. Skills are designed to be used and called across different tasks, and multiple skills can be active at once. Where a Gem was one assistant for one job, skills are meant to combine, which opens up workflows a single Gem couldn't handle.
Gemini Custom Instructions and What Carries Over
Your Gemini custom instructions are the backbone here, because that's what actually defines how each assistant behaves. The migration preserves them. When your Gems become skills, the instructions you wrote are what make each one do its job, so the quality of your custom instructions determines how useful the skill stays.
That's worth saying plainly: if your Gems worked well, they'll keep working well, because the underlying instructions haven't changed. If a Gem was vague, it'll stay vague as a skill. The transition doesn't fix or break your setup. It just moves it.
If you've been meaning to clean up your Gems, this is a natural moment. Review your custom instructions, retire the ones you never use, and sharpen the ones you rely on. Doing that now means you enter the skills era with a tidier set of tools.
Google Gemini is a productivity and creativity app that supports live conversations and multimodal creation.
What to Do Before November 17
Three things, and none of them take long.
1. Open the Gems manager and read the migration notice, so you know the date and what's changing.
2. Review your Gems and their custom instructions, retiring any you've outgrown.
3. Practice selecting a skill with the "/" command in a test thread, so the new flow feels familiar before it goes live.
There's no deadline pressure to export or back anything up, since Google handles the migration. The only thing you can't postpone is muscle memory, and a few minutes with the slash command now saves confusion later.
One caution worth taking seriously: if any of your Gems handle sensitive material, review what you've stored in them before the migration. Skills are meant to be more widely callable across tasks than Gems were, so if your custom instructions contain private context or credentials you'd rather not spread, this is the moment to strip them out. Treat the move as a chance to audit, not just migrate.
Privacy and Where Your Data Goes
Custom assistants live and die by the instructions and data you feed them. Gemini stores your Gem content and custom instructions on Google's servers, which is how the migration can happen without your involvement, and the same applies once they become skills. If you use Gemini's app on Android, the standard Google privacy settings apply, and you can review and delete your activity from your Google account at any time.
Two practical habits help here. Don't put passwords, API keys, or anything you'd hate to leak into a custom instruction, because the assistant doesn't need them to do its job and they widen your exposure. And check the Gemini app's data controls so you know how your conversations are retained and whether they feed model improvement. Installation-wise, Gemini on Android from a trusted store keeps you on the official build, and keeping Google Play Protect on adds a layer of protection against tampered apps.
What the Change Means for Gemini Users
Google is killing off Gems in favor of skills, and for most users the practical result is a wash. Your assistants survive, your custom instructions carry over, and you gain the ability to stack skills rather than run one Gem at a time. The cost is a clunkier invocation method and a feature name that no longer has its own home in the app.
This is the pattern with AI tools right now. Features get renamed, merged, and repositioned as the platforms consolidate around agents that do everything in one place. Google's messaging app history shows it has always shuffled product names, and Gems are the latest casualty of that habit. The useful question isn't what the feature is called. It's whether your setup still works, and on November 17 the answer is yes.
Download the Gemini app on Android from APKPure to stay on top of the transition. If you want your automation to survive the switch intact, spend a few minutes reviewing your Gemini custom instructions before the deadline, since that's the one piece you actually control.
Google Gemini is a productivity and creativity app that supports live conversations and multimodal creation.
NEWS
REVIEWS
HOWTO
