Google Replaces Gemini Gems with Skills: Only 100 Can Be Active at Once
Starting November 17, 2026, Google is replacing Gemini Gems, standalone chatbots with an assigned role, with Skills: instructions that Gemini connects in any chat, either on its own or via an @-mention. Only 100 skills can be enabled at the same time, while sharing and files up to 100 MB from Drive, Photos and Notebook are back. Teams should therefore check how migrated Gems behave in a regular chat before December 16. Old Gems will open until December 16, 2026, and Workspace business accounts until March 2027. Skills can only be shared in the web version for now, not in the mobile app. When sharing, users choose permissions: view only, or editing as well.
AI-processed from ZDNet AI; edited by Hamidun News
If you have built your own assistants in Gemini, such as a "house-style editor," an "onboarding bot" or a "contract checker," now is the time to look at your settings. Starting November 17, 2026, Google is shutting down Gemini Gems, standalone chatbots with an assigned role, and replacing them with a feature called Skills. A Skill is not a separate chat. It is a set of instructions that Gemini applies in any of your conversations. No more than 100 of these skills can be active at the same time, but you can keep as many created skills as you like. Old Gems will move over automatically, but you should check how they behave in the new format.
What changes: from a separate chat to a set of instructions
A Gem was, in effect, a standalone chatbot: you created it with a role description, opened it as its own dialogue, and talked to that bot specifically. A Skill works differently. It is a user instruction that lives inside Gemini and connects to any conversation.
It works like this. You describe the situations in which Gemini should apply the skill and explain what exactly it should do. Google advises giving concrete examples of the desired result, which helps the model hit the right format. After that, Gemini can decide on its own that the skill is relevant, or you can call it manually with an @-mention in the chat.
For example, you might have a skill called "write in our brand voice." Previously, using it meant going into a separate Gem and doing all the work there. Now you write a regular request in the main chat, mention the skill, and Gemini pulls in the relevant rules. Google cites as examples a marketing team with a brand-voice skill that draws on a guideline document in Drive, and a team lead with a skill for onboarding based on the team handbook.
You can create skills without limit, but only 100 can be active at the same time.
What was carried over from Gems, and the deadlines
To make the transition easier, Google has brought two Gem features back into Skills.
The first is sharing. You can send a skill to colleagues and choose whether they can only view it or also edit it. The settings are in the menu in the upper left corner: Customize, then Skills. Permissions can also be changed there later. There is one caveat: for now, skills can only be shared through the web version of Gemini, not the mobile app.
The second is files. When creating a skill, you can attach documents up to 100 MB from Drive, Photos and Notebook, as well as from a local device. According to Google, Gemini accesses these files every time the skill runs, and changes to the source files are picked up in real time. For team use this is convenient: updating a guideline or handbook in Drive is enough for the skill to start working from the new version, with no need to rewrite prompts.
The timeline is as follows. All existing Gems are automatically moved to Skills, and you can migrate them manually sooner if you prefer. The Gems section is now hidden in settings, and access to it will close on December 16, 2026. For Workspace business accounts, enterprise customers and non-profit organizations, the deadline is extended to March 2027, and for education accounts to June 2027.
What to do in practice
First, do not put off the check. Automatic migration is helpful, but a skill's behavior in a regular chat may differ from that of a standalone bot. Run your most important Gems through the new format and confirm that the results are still the same.
Second, revise the descriptions. Since Gemini now decides on its own when to enable a skill, vague wording of the conditions will cause it to trigger in the wrong situations or not trigger at all. Write specific situations and add examples of output.
Third, keep an eye on the limit of 100 active skills. For one person that is plenty, but in a company where everyone shares their own sets, the list can grow quickly. It makes sense to turn off skills you no longer use.
Fourth, factor in the platform restriction: if a team works mostly from phones, skills will have to be distributed through the web.
The news itself is modest. Google has not released a new model. It has repackaged an existing capability. But the direction is clear. Instead of many isolated bots, the company is building a single assistant with pluggable instructions. For product managers and team leads, the takeaway is this: shared AI work templates are better stored as skills linked to live documents than as a scattered collection of chats.
- Nov 21, 2026Apple Is Building an AI Agent and Making It Harder for Outsiders to Get Access: Permission Now Takes 14 Steps, Not 4
- Nov 21, 2026Gemini 4 Neon shrank the TS Rust binary from 47.44 to 7.97 MB in under 10 hours
- Nov 21, 2026A swimming team captain handed ChatGPT three scheduled tasks and cut her routine work by a multiple
- Nov 21, 2026MIRA Neural Network Renders Rocket League at 20 FPS, but Ping Hits 460 ms
Key Questions Answered
What changes: from a separate chat to a set of instructions?
A Gem was, in effect, a standalone chatbot: you created it with a role description, opened it as its own dialogue, and talked to that bot specifically. A Skill works differently. It is a user instruction that lives inside Gemini and connects to any conversation. It works like this. You describe the situations in which Gemini should apply the skill and explain what exactly it should do. Google advises giving concrete examples of the desired result, which helps the model hit the right format.
What was carried over from Gems, and the deadlines?
To make the transition easier, Google has brought two Gem features back into Skills. The first is sharing. You can send a skill to colleagues and choose whether they can only view it or also edit it. The settings are in the menu in the upper left corner: Customize, then Skills. Permissions can also be changed there later. There is one caveat: for now, skills can only be shared through the web version of Gemini, not the mobile app. The second is files.
What to do in practice?
First, do not put off the check. Automatic migration is helpful, but a skill's behavior in a regular chat may differ from that of a standalone bot. Run your most important Gems through the new format and confirm that the results are still the same. Second, revise the descriptions. Since Gemini now decides on its own when to enable a skill, vague wording of the conditions will cause it to trigger in the wrong situations or not trigger at all. Write specific situations and add examples of output.
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.