Google is retiring Gems in Gemini and moving users to Skills, a newer way to save reusable instructions for work across Gemini Chats and tasks. The change begins in November 2026 for people using personal Google Accounts. For businesses that have built repeatable Gemini workflows around Gems, the important issue is not whether a move is required. It is how to review existing instructions, files, and tool dependencies before the automatic transition.
According to Google's official Gemini transition guidance, Gems will automatically migrate to Skills when Gems are removed. Supported files will transfer too. However, Skills do not yet support every Gem capability, and Google sets a limit of 100 active Skills. That makes this a product transition worth planning for teams that rely on tailored Gemini instructions for recurring tasks.
What changes as Gemini moves from Gems to Skills
Gems were designed to tailor Gemini for a particular purpose through saved instructions. Skills serve a related role, but Google describes them as reusable instructions that can be used across Gemini Chats and tasks. Users can invoke a Skill with a slash command, while an @ trigger is planned for a future update.
The practical shift is toward making saved instructions easier to reuse in more places within Gemini. A business might maintain a Skill for drafting product descriptions in a defined voice, another for structuring customer-support responses, and another for summarizing internal material according to a set format. The usefulness of that approach still depends on clear instructions and supported source files.
| Area | Gems | Skills |
|---|---|---|
| Role in Gemini | Tailored instructions for specific tasks | Reusable instructions across Gemini Chats and tasks |
| How to invoke | Not specified in the supplied guidance | Slash command, with an @ trigger planned |
| Transition path | Retired as part of the move to Skills | Gems migrate automatically, including supported files |
| Known constraints | Some Gem tools are available today | Maximum 100 active Skills, with some tools not yet supported |
Migration timeline and related retirements
Google's published schedule separates personal and Workspace accounts:
- November 2026: Gems begin transitioning to Skills for personal Google Accounts.
- March 2027: The transition starts for Google Workspace business, enterprise, and non-profit accounts.
- June 2027: Google Workspace education accounts follow.
- November 2026: Opal and Gems by Google Labs will also retire alongside Gems.
The timeline gives Workspace users additional time, but it does not remove the need to assess important Gems. Teams should identify which saved instructions are actively used, who owns them, and whether each one depends on a capability that has not yet moved to Skills.
What will migrate, and what may need attention
Google says that the migration is automatic when Gems go away, and users can also manually recreate a Gem as a Skill before then. Supported files associated with Gems will transfer. Google also plans a bulk transition for knowledge files, while manual knowledge-file uploads can be made through SKILL.md where needed.
That distinction matters for workflows based on internal reference material. A Gem that relies only on instructions may be relatively simple to check after migration. A Gem that depends on files needs a more deliberate review: confirm that its files are supported, verify that the material transferred as expected, and use the documented manual upload route when required.
Businesses should also account for feature gaps. Google says some tools available with Gems are not yet supported in Skills, including video creation, Canvas, Deep Research, and Guided Learning. The supplied guidance does not say when, or whether, each of those tools will become available in Skills. A workflow built around one of them should not assume a like-for-like result after moving.
A practical transition checklist is:
- List the Gems people use for recurring work and identify the owner of each one.
- Separate instruction-only Gems from Gems that use knowledge files or unsupported tools.
- Recreate critical Gems as Skills early if you want to test them before the automatic move.
- Check that the total number of active Skills remains within Google's 100-Skill limit.
- Validate migrated Skills in the actual Chat or task context where employees use them.
The change is also an opportunity to simplify. Reusable instructions are most manageable when they describe one clear job, define expected output, and avoid overlapping responsibilities. That can make it easier for a team to find the right Skill and assess whether its output remains useful after the transition.
For businesses using Gemini instructions in everyday work, this transition is a chance to turn ad hoc prompts into dependable, repeatable processes. Scalevise can help assess which tasks are suitable for AI, map the dependencies around files and tools, and design a practical rollout that fits how your team already works. Our AI consultancy service helps translate changing AI product features into usable workflows, reducing avoidable rework before a platform migration. Request an AI consultation to plan your Gemini Skills transition.
Frequently Asked Questions
When will Google Gemini migrate Gems to Skills?
Google says the transition starts in November 2026 for personal Google Accounts, March 2027 for Workspace business, enterprise, and non-profit accounts, and June 2027 for Workspace education accounts.
Will existing Gemini Gems migrate automatically?
Yes. Google says Gems will automatically migrate to Skills when Gems go away. Users can also manually recreate Gems as Skills before the automatic transition.
Will files attached to Gemini Gems move to Skills?
Google says supported files will transfer automatically. Bulk knowledge-file transition is planned, and users can manually upload knowledge files through SKILL.md where necessary.
What Gemini Gem features are not yet supported in Skills?
Google says Skills do not yet support some Gem tools, including video creation, Canvas, Deep Research, and Guided Learning.
How many active Gemini Skills can a user have?
Google sets a limit of 100 active Skills.
Conclusion
Google's Gems-to-Skills transition is a confirmed product change with a clear staged timetable. Automatic migration should reduce basic setup work, but file support, the 100-Skill limit, and current tool gaps mean important workflows should be reviewed before their applicable migration date. For teams using Gemini to standardize recurring work, the move is best treated as a chance to test, consolidate, and improve their reusable instructions.
For businesses using Gemini instructions in everyday work, this transition is a chance to turn ad hoc prompts into dependable, repeatable processes. Scalevise can help assess which tasks are suitable for AI, map the dependencies around files and tools, and design a practical rollout that fits how your team already works. Our AI consultancy service helps translate changing AI product features into usable workflows, reducing avoidable rework before a platform migration.
Top comments (0)