If you built a Gem you actually use — the one that formats your meeting notes, edits in your voice, quizzes you before an exam — Google has a date circled for it. A conversion date.
On September 30, Google announced that skills are rolling out directly into Gemini chat globally, and that skills “will soon replace Gems as the tool for tailoring instructions for specific tasks.” Gems are being folded into something Google clearly thinks is better. Decide whether you agree before the folding happens to you.
A Gem was a place. A skill is a thing you carry.
A Gem lived in its own corner. You opened it, started a fresh chat inside it, and got that one personality, that one instruction set. One Gem per conversation. That was the deal.
Skills work differently, and Google’s own help page lays out the three differences that matter: easy access, automatic use, and stacking. You type `/` followed by a skill’s name — soon `@` instead — right inside any chat. Gemini can also spot when a skill fits your prompt and apply it without being asked. And you can stack several skills in one conversation.
Google’s example: combine a writing-style skill with a brand-guidelines skill and get on-brand drafts in your own voice. Under Gems, that meant picking which one mattered more and pasting the other in by hand. Under skills, they run together.
You can also build skills out of chats you have already had, and a skill can carry reference files — plain text documents, PDFs, or images, Google says.
None of that is a reason to panic. It is a reason to pay attention, because the switch is not one date. It is three.
Whose clock are you on?
Google’s transition page splits the timeline by account type, and the split is wide:
- November 2026: personal Google accounts lose Gems.
- March 2027: Workspace business, enterprise, and non-profit accounts.
- June 2027: Workspace education accounts.
Personal accounts go first, and they go soon. If your favourite Gem sits on a personal login, you have weeks, not seasons. Work and school accounts get a long runway.
Two smaller casualties ride along: Opal, Google’s experiment for building mini apps, turns down in November, and so do Gems by Google Labs. Skills in the Gemini app are currently for people over 18 signed in to a personal account, with work and school access still to come.
What does not survive the trip — yet
Google promises skills will get the features people liked in Gems, including sharing them and pulling files from Google Drive and Gemini Notebook. Read that again. Will get. Promised for the coming weeks, not shipped today.
The gaps right now are specific. Google’s help page says most default tools available in Gems do not work with skills yet, and names them: Create video, Create music, Canvas, Deep research, and Guided learning. GitHub files are not supported in skills either. And a skill has no page listing the chats where you used it — those chats just land in your normal side panel.
So a Gem built around Canvas or Deep Research will not behave the same way on the other side of this move. It will arrive, but it will arrive diminished. If that Gem does real work for you, keep using it as a Gem for as long as your account allows, and check Google’s page again before your deadline.
Automatic migration softens the landing, but do not mistake it for a finished job. Google will recreate your Gems as skills when Gems go away, supported files included. A detailed migration guide working from Google’s admin help pages adds the catch: migrated skills show up as inactive drafts. You have to review and switch on each one before it runs.
Move your best one by hand this week
The manual route is short. Open the Gem, download any knowledge files it holds — one at a time, annoyingly. In a new tab, go to Settings, then Skills, then Create manually. Paste in the Gem’s name, description, and instructions; the name gets reformatted automatically. If the Gem had files, download the new skill, drop its SKILL.md file into a folder with those files, and upload the folder using Replace skill.
Twenty minutes, maybe. But do not just copy. A Gem’s description could be vague because you were the one choosing it. A skill gets chosen by Gemini, sometimes automatically, so its description has a job to do. Google’s best-practice advice is blunt: describe the specific situations when the skill should be used, keep the instructions focused on what is unique to the task, and include concrete examples of the output you expect.
“Newsletter helper” tells Gemini almost nothing. “Edits weekly newsletter drafts for clarity and length, and suggests three subject lines — use when reviewing a draft before sending” tells it exactly when to step in. That one rewrite is the whole upgrade, hiding in plain sight.
Back up the rest, even the Gems you barely touch. Copy each one’s instructions into a document of your own. Instructions are text. Text is portable.
Your Gems are not disappearing tomorrow. They are being translated — into a format that is more flexible, less finished, and chosen by the machine as often as by you. Translate your best one yourself, while the original is still sitting there to check against.
Sources
- Google Blog (September 30, 2026) — Automate repetitive tasks with Skills
- Google Gemini Help — About the transition from Gems to skills
- DEV Community, Cryptea Sensei (October 20, 2026) — Gemini Gems to Skills: What Changes in November 2026 and How to Move Your Gems Now


