Google to replace Gemini Gems with a new skills system by 2026

The transition to skills

Google is fundamentally changing how users interact with custom AI personas within the Gemini ecosystem. Currently, users create 'Gems,' which are specific AI configurations that require users to navigate to a dedicated tab to use them. The company is moving toward a 'skills' model, which allows these custom instructions to be invoked dynamically during any conversation.

As reported by androidpolice.com, this shift is intended to make the AI more accessible. Instead of switching contexts, users will be able to call up a specific skill in the middle of an ongoing chat. This can be done by typing a slash (/) followed by the skill name, though Google plans to transition this command to an at sign (@) in the future.

One of the most significant technical upgrades is the ability to stack skills. This means a user could theoretically activate an editorial assistant and a research skill simultaneously in one thread. This allows the AI to apply multiple layers of context, such as specific writing styles and deep research parameters, at the same time.

Timeline for account types

The rollout of these changes follows a specific schedule based on the type of Google account a user holds. For individuals with personal Google accounts who are 18 and older, the transition to skills begins on November 17, 2026. On this date, original Gems will remain accessible for reference only, but users will no longer be able to create, edit, or use them.

The final removal of Gems for personal accounts is set for December 17, 2026. Users under the age of 18 do not have a confirmed transition date yet. Google Workspace users have a longer runway, with their transition not beginning until next year. For these users, the final removal dates are not yet set in stone.

Education users have the most time, with a confirmed removal date of June 1, 2027. However, Google has not yet announced a specific date for when skills will be integrated into Workspace applications like Docs, Sheets, and Slides. This delay means that while the core Gemini experience is changing, the integration into productivity suites remains pending.

Technical limitations and files

While the skills system offers more flexibility, it currently comes with several functional limitations compared to the original Gems. For instance, many of Gemini's advanced tools—such as Canvas, Deep Research, and music or video creation—do not currently support skills. Additionally, users cannot currently share skills with other people or sync them between the Gemini app and Workspace apps.

There are also specific constraints regarding data and storage. While there is no limit on the total number of skills a user can create, only 100 can be active at any one time. Furthermore, any files added to a skill are subject to a 100MB size limit. If a file exceeds this size, Google will delete the largest files to bring the skill under the limit.

Users must also be aware of unsupported file formats. Legacy Microsoft Office files like .doc and .xls, as well as compressed archives and GitHub files, are not supported. Because Google will delete these files on the December 17, 2026 deadline, users need to manually download and save any data they wish to keep before the transition is complete.

How to migrate your data

Google has stated that it will automatically migrate existing Gems, but the company suggests that proactive migration is the safest way to ensure your workflows remain intact. Simple, text-based Gems should transition smoothly, but complex Gems with supporting files require more manual attention. Users are encouraged to audit their current Gems and recreate their most important ones as skills before the 2026 deadline.

To perform a manual migration, users can download the files from the Knowledge heading of an existing Gem. These files should be placed in a folder named in all lowercase with hyphens. Then, users can create a new skill manually and paste the name, description, and instructions from the original Gem into the new skill setup.

For the most complex migrations involving knowledge files, users can download the skill as a zip file and extract the SKILL.md file. This file must be placed in the same folder as the knowledge files before being uploaded back to the skills page. This process ensures that the AI maintains the correct context and instructions even as the underlying platform architecture changes.

The open standard move

A major underlying change in this transition is the move toward an open standard. Skills are being built on the SKILL.md standard, which is designed to be transferable across different AI platforms. This means that the instructions and data you use to build a skill today could potentially be used with other major AI models in the future.

This move signals a shift toward interoperability in the AI space. By adopting a standard format, Google is making it easier for users to move their custom configurations between different services. While the current focus is on the Gemini ecosystem, the underlying architecture is being built to be more portable than the previous Gem format.

Despite the growing pains of a new system, the move to skills is intended to create a more integrated experience. By moving away from isolated tabs and toward a system that can be triggered anywhere, Google aims to make custom AI behavior more seamless. As the system matures, the goal is to provide a more spacious and functional way to interact with specialized AI tools.