If you've spent time building custom AI assistants inside Google's Gemini, you're about to see a significant shift. This November, Google is retiring Gems and rolling out a new system called Skills. It's not just a rebrand. The underlying architecture is changing, and that has real consequences for anyone who relies on these tools for work, research, or creative projects.
I've been using Gems since they launched, building everything from a meal-planning assistant to a code-review helper that saves me hours each week. When I heard about the switch, I dug into what Google has shared so far and talked to other users who are already testing the new Skills framework. Here's what I found, and what you need to know before November arrives.
What exactly are Gemini Gems?
For those who haven't used them, Gems are custom versions of Gemini that you configure for specific tasks. You give a Gem a name, write a detailed instruction prompt, and optionally upload reference files. After that, the Gem behaves like a specialized assistant. Instead of re-explaining your needs every time you open a chat, you just select the Gem and start working.
The appeal is obvious. A marketing manager might build a Gem that always writes in her brand voice. A developer might create one that reviews Python code for security flaws. A student could set up a Gem that summarizes academic papers in plain language. The possibilities are broad, and that's precisely why the transition to Skills matters.
Why Google is making the change
Google hasn't published a lengthy manifesto, but the signals are clear. Gems, as they exist today, are essentially saved prompts with a few bells and whistles. They're useful, but they're also static. Skills, by contrast, appear to be designed as more dynamic, composable units of capability. Think of the difference between a saved search and a full application. Google is moving toward the latter.
There's also the competitive angle. OpenAI's GPTs, Anthropic's Projects, and a growing ecosystem of third-party agent platforms have pushed the idea of customizable AI further. Google needs Gems to evolve into something that feels less like a prompt library and more like a genuine productivity layer. Skills seems to be that answer.
What changes with Skills
Based on early documentation and user reports, here are the key differences you can expect.
- Skills are modular. Instead of one monolithic instruction block, you can define discrete abilities that stack together. A single Skill might handle tone adjustment, while another manages data formatting.
- Better integration with Workspace. Skills are expected to plug more deeply into Docs, Sheets, and Gmail, letting your custom assistant act on real files rather than just chat about them.
- Improved memory and context. Gems often forget details between sessions. Skills are built with persistent context in mind, so your assistant remembers your preferences over time.
- Sharing and discovery. Google is reportedly working on a marketplace-like experience where users can publish and import Skills, similar to how GPTs can be shared.
That last point is potentially the most transformative. If Skills become shareable, we could see a thriving ecosystem of community-built assistants for everything from tax preparation to language learning. It also raises questions about quality control and privacy, which Google will need to address.
What happens to your existing Gems
Google has indicated that existing Gems will be migrated to the Skills framework, though the process may not be seamless. Complex Gems with lengthy instructions or multiple uploaded files might require manual adjustment. If you've built a Gem that you depend on daily, now is the time to export its instructions and test it under the new system as soon as you get access.
One user I spoke with, a freelance editor who built a Gem for proofreading client manuscripts, said her initial migration attempt lost some of the nuance in her original prompt. She had to rewrite about 20 percent of it to get comparable output. Your mileage may vary, but the lesson is clear: don't assume a one-click transition will preserve everything.
Why this matters beyond the Gemini app
Google's move is part of a larger trend. AI assistants are shifting from general-purpose chatbots to specialized, configurable agents. Microsoft is doing something similar with Copilot extensions. Amazon is pushing Alexa Skills into new territory. The companies that win this next phase will be the ones that make customization both powerful and easy.
For everyday users, the practical impact is straightforward. If Skills work as promised, you'll spend less time re-prompting and more time getting useful output. You'll also be able to borrow proven setups from other users instead of building everything from scratch. That lowers the barrier to entry significantly.
For businesses, the stakes are higher. Companies that have invested in custom Gems for customer support, content generation, or data analysis will need to audit their setups. A Skill that behaves differently than expected could introduce errors into workflows. The smart move is to treat the November transition as a project, not an afterthought.
How to prepare now
You don't have to wait until the rollout to get ready. Here are steps you can take today.
- Document your Gems. Copy every instruction prompt, note any uploaded files, and record example outputs that you consider correct. This gives you a baseline for comparison.
- Identify critical Gems. Which ones do you use daily? Those deserve the most attention during migration.
- Test early. If you have access to the Skills beta, start experimenting. Try recreating your most important Gem as a Skill and compare results.
- Simplify where possible. Overly complex prompts may not translate well. Break them into smaller, more modular instructions if the new system supports it.
- Stay informed. Google will likely publish migration guides and FAQs. Keep an eye on official channels as November approaches.
It's also worth considering what new capabilities Skills might unlock. If you've been hesitant to build custom assistants because Gems felt too limited, the new framework could change your mind. The ability to chain Skills together, for example, might let you create a research assistant that searches the web, summarizes findings, and drafts a report, all within a single session.
The bigger picture: customization as the new battleground
Google's decision to replace Gems with Skills isn't happening in a vacuum. It reflects a broader recognition that the value of AI isn't just in the base model. It's in how well that model adapts to your specific needs. The companies that make adaptation frictionless will earn loyalty. Those that don't will see users drift to competitors.
There's also a philosophical shift here. Gems were about saving prompts. Skills are about building capabilities. That's a meaningful distinction. It suggests Google wants users to think of Gemini not as a chatbot you talk to, but as a platform you build on. Whether that vision resonates will depend on execution.
Early reactions from developers have been cautiously optimistic. Some worry that Skills could become overly complex, turning a simple task into a configuration nightmare. Others see the potential for a vibrant ecosystem. The truth likely lies somewhere in between, and the November rollout will be the first real test.
Frequently asked questions
Will my existing Gems stop working immediately in November?
Google has not announced a hard cutoff date, but the transition is expected to begin in November. Existing Gems should continue to function during the migration period, though some features may be limited. It's best to prepare your most important Gems for the switch as soon as possible.
Can I export my Gems before they become Skills?
There is no official export tool yet, but you can manually copy your Gem instructions and save any uploaded files. Google may add an export option closer to the transition. In the meantime, documenting your setups is a prudent step.
Will Skills be available to free users or only paid subscribers?
Google has not confirmed the exact availability tiers. Gems are currently available to both free and paid users with some limitations. It's likely Skills will follow a similar model, but premium features may be reserved for Google One AI Premium subscribers.
How are Skills different from just writing a good prompt?
A good prompt is a one-time instruction. A Skill is a reusable, configurable component that can be shared, combined, and improved over time. Skills are designed to be more like apps than prompts, with persistent settings and deeper integration into Google's ecosystem.
What should I do if my migrated Skill doesn't work as expected?
Start by comparing the output to your original Gem's output. Check for missing context or instructions. If the issue persists, try simplifying your Skill or breaking it into smaller parts. Google will likely provide troubleshooting resources, and community forums can be helpful as well.
The move from Gems to Skills is more than a name change. It's a signal that Google is serious about making Gemini a customizable platform. For users, that means both opportunity and adjustment. The opportunity is a more powerful, flexible assistant. The adjustment is the work of migrating and relearning. If you start preparing now, you'll be ahead of the curve when November arrives.