Gemini Gems are becoming Skills on November 17. Audit yours now.

Google is killing Gems. The custom instruction sets that have lived in the Gemini sidebar since August 2024 become Skills on November 17, and Google will migrate them automatically. If your team relies on Gems for recurring workflows, you have about six weeks to find out what will not survive the move.

Skills are reusable instructions that run inside Gemini chat instead of a separate manager. Type a forward slash and the skill's name in the prompt bar and it applies to the current conversation. Gemini can also detect when a skill is relevant and apply it on its own, and multiple skills can stack in one chat, which Gems never allowed. Google announced the feature September 30 through Gemini App product manager Deven Tokuno; it debuted in the Gemini Spark agent and is now rolling out to Gemini chat globally, free, on every subscription tier. Users under 18 are excluded for now.

The timeline is staggered. Personal Google Accounts start losing Gems in November, with automatic migration beginning November 17. Google Workspace business, enterprise, and non-profit accounts follow in March 2027. Education accounts get until June 2027. Creating or editing Gems stops even earlier: October 13. Opal and the Google Labs Gems retire alongside.

Here is the part to read before you relax about "automatic." Feature parity is promised, not delivered. Google says skill sharing via links, Google Drive files, and notebook context are coming "in the coming weeks." Right now they are not here. Neither are several Gem capabilities: GitHub files as knowledge sources, and the Canvas, Deep Research, Guided Learning, video, and music creation tools, do not work with skills yet. If a Gem you depend on uses any of those, the migration will produce a skill that quietly does less than the Gem did. There is also a new requirement: skills need Keep Activity turned on, which means your chats are retained and human reviewers may read some of them, kept for up to three years. If you disabled Keep Activity for privacy reasons, your converted skills may not work at all.

The practical move is an audit, not a wait. List every Gem your team uses, who owns it, which knowledge files it carries, and which tools it depends on. Download the knowledge files for anything important; Google's own help page advises it. Anything leaning on Drive files, GitHub sources, or the unsupported creation tools should be rebuilt or replaced before November 17, not discovered broken after. Then decide whether to adopt skills early for the new workflows, the stacking and auto-apply behavior is genuinely better than Gems, while keeping critical production prompts on whatever still works until parity lands.

What remains unknown: whether the migration tooling handles edge cases cleanly, and whether the promised parity features arrive before the November deadline or after it. Google's own rollout notice reportedly surfaced before all the supporting documentation was ready. Plan for the gap, not the promise. Six weeks is enough time to audit. It is not enough time to rebuild everything the week your Gems stop working.