Google plans to migrate Gemini Gems to skills on November 17

Google plans to convert Gemini's custom Gems into reusable skills starting November 17, 2026, according to Sarah Perez's TechCrunch report. The report describes a message inside the Gemini app announcing the change. Google says it will handle the migration, and existing Gems will remain usable until the transition begins.

For people who have written instructions for a recurring task, the important detail is preservation: Google says their work will carry over into the new format. The announcement changes how that work is organized and selected inside Gemini. It does not require users to rebuild their custom assistants before the stated migration date.

The migration has a date, but has not happened yet

The November 17 date is the start of the conversion described in the app message. As of the September 28 report, Google was informing users about a future change. Existing Gems were still available, with an automatic transfer planned for the later date.

That distinction prevents two misleading readings of the announcement. Google has not said that users must delete their Gems, and the report does not say the migration has already finished. A team relying on one for a repeated task can continue using it in the meantime while preparing to check the replacement after it appears.

Perez reports that users will not need to take action to make the transfer happen. That commitment concerns the migration itself. It should not be expanded into a guarantee that every interaction, shared link or saved configuration will behave identically after the change. The report does not supply a detailed compatibility checklist for those cases.

Skills reuse instructions across different tasks

Google launched Gems in 2024 as a way to give Gemini task-specific instructions without repeating them for each conversation. Its examples included a learning coach and a coding partner. Users could also create their own assistants, such as a vacation planner, and share them with other people.

The proposed skills format keeps the reusable-instruction idea while allowing those skills to be used across different AI tasks. That is the concrete change described in the report. The name alone does not establish compatibility with skill formats from other vendors, nor does this account describe a downloadable file specification or a developer API.

For a user with a writing Gem, for example, the practical question is whether the migrated instructions still guide the intended task. The sensible check is to run a familiar request and inspect the result once the skill becomes available. That is a suggested verification step, not a claim that Franklin AI has tested the migration or that Google has documented an exact testing procedure.

Selecting a skill introduces a different interface

The report says users will select a skill by entering a forward slash in a task thread. This makes the invocation method part of the change: people will need to recognize the new label and know how to choose the instructions they want to apply.

Perez questions whether that interface will be as approachable for consumers as typing a normal request into a chatbot. That is her assessment of the design, rather than a measured usability result. The captured report includes no user study establishing how long the new interaction takes to learn or whether it improves task completion.

Google's assurance that existing work will be migrated addresses a real concern for users who invested time in custom instructions. The remaining uncertainty concerns the resulting experience. The available report leaves sharing behavior, migration exceptions and any new limits unspecified. Until Google exposes the transferred skills, users should treat the announcement as a dated transition plan and retain their own expectations about the tasks their Gems were created to perform.