Google • Gemini • AI workflows
Google says in an in-app notice that Gemini Gems will begin moving to Skills on November 17, 2026. Migration is automatic and each Gem should remain usable until it moves, but Google's public Help pages do not yet promise that every file, sharing permission or workflow setting will transfer unchanged.
When will Gemini Gems become Skills?
The notice now appearing in Gemini's Gem manager says the transition starts on November 17, 2026. It says Google will automatically begin migrating Gems to Skills and that users can continue using each Gem until it migrates. 9to5Google first documented the notice, and TechCrunch and The Verge independently reported the same date and automatic-migration wording.
That date is a migration start, not a published completion deadline. Google has not said that every account will move on the same day, and its public Help Center does not yet provide a migration schedule by country, account type or subscription. Treat November 17 as the beginning of a transition window rather than a promise that all Gems will change at once.
Can I keep using a Gem until it migrates?
According to the reported in-app notice, yes: a Gem remains usable until Google migrates it. Google's current Gem Help still explains how to create, edit, use and delete Gems, add knowledge files and share a Gem with viewers or editors.
There is no reason to delete a working Gem merely because the transition has been announced. Keep using the original while it is available, and avoid making an irreversible cleanup decision before you have checked the migrated Skill. If a Gem is important to work, study or a shared process, keep a separate copy of its instructions and retain the original source files used as knowledge.
What is changing from Gems to Skills?
Both features preserve reusable instructions, but Google's current Skills model is designed to work across Gemini Spark tasks. A Skill can be selected with a slash command, automatically applied when Gemini judges it relevant, and combined with other Skills in one task. Google also lets users create a Skill from a template, build one manually, ask Gemini to create it, or upload a plain-text skill package.
Gems currently work more like named custom assistants in the Gemini sidebar. Google documents a name, instructions and optional knowledge files from a device, Google Drive or NotebookLM. Gems can also be shared with viewers or editors, and shared Gems are stored through Google Drive.
The migration announcement establishes that Gems are becoming Skills. It does not yet establish that every Gem feature has a one-to-one Skills equivalent. In particular, Google's public migration material does not explain how existing sharing links, access roles, Drive-backed knowledge, NotebookLM sources, default tools or work and school accounts will map after migration.
Who can create and use Gemini Skills today?
Google's current Skills Help is narrower than the current Gem Help. At the time of review, Skills are available only in Gemini Spark and require a personal Google Account, age 18 or older, a Google AI Pro or Ultra subscription, and Keep Activity turned on. Google says the feature is available where Gemini Apps are supported except the European Economic Area, Nigeria, Switzerland and the United Kingdom.
Google currently lists access through Gemini Spark in the Gemini mobile app, the Gemini app on Mac and the web app at gemini.google.com. Work and school accounts are not supported by the current Skills page. These are present-day launch limits, not proof of what eligibility will look like when migration starts in November.
This distinction matters for existing Gem users. A free-account, managed-account or excluded-region user should not assume that today's Skills creation screen will appear merely because the migration was announced. Check the Gemini interface and current Google Help for the account that actually owns the Gem.
What should I check before my Gems migrate?
- Save the instructions. Open each important Gem and keep a separate copy of its name, description and complete instruction text.
- Inventory knowledge sources. Note every uploaded file, Drive file and NotebookLM source. Keep the originals in their existing controlled locations rather than relying on the Gem as the only copy.
- Record sharing. For a shared Gem, note the owner, viewers, editors, general-access setting and any linked files. Do not assume those roles or links will transfer unchanged.
- Write down tool expectations. If the Gem depends on image creation, Canvas or another specific tool, record that behavior so you can verify it after migration.
- Note account and region. Check whether the owner is a personal, work or school account and whether current Skills access is available in that location.
- Test after migration. Compare the migrated Skill's instructions, knowledge, sharing and outputs against the original record before using it for important work.
This checklist is a continuity precaution, not a claim that Google will lose data. The point is to preserve the information needed to recognize a mismatch and rebuild a workflow if an undocumented edge case appears.
What can Gemini Skills do now?
Google says an enabled Skill can be used automatically when relevant or selected directly by entering / in a task thread. Multiple Skills can be combined in one task, and one Skill can reference another in its instructions. Users can disable automatic use without deleting the Skill, edit it directly or conversationally, download it as a ZIP file, and delete it from the Skills page.
Google also documents file-based Skill creation. A package needs a root SKILL.md file with a lowercase hyphenated name, can include supported text, code and configuration files, and can total up to 100 MB. Binary media and rich office files are not supported in the current upload flow, and scripts inside a Skill cannot make external website requests.
Those capabilities help explain Google's direction: reusable instructions become modular building blocks that can be selected, combined and carried across Spark tasks. They do not answer every migration question for an existing Gem, so the prudent approach is to preserve the original configuration and verify the result.
What remains unknown about the migration?
Google has not yet published a migration-specific Help page covering completion timing, rollout order, subscription changes, regional exceptions, work or school accounts, shared-Gem permissions, public links, Drive file access, NotebookLM sources or default-tool behavior. It has also not documented whether every migrated Gem will be immediately editable in the same interface for every owner.
Until those details are published, distinguish three layers: the reported in-app notice establishes the migration start and continued use until migration; current Gem Help establishes how Gems work now; current Skills Help establishes how Skills work now. None of those layers alone proves future one-to-one feature parity.