Most people with a folder full of Gemini Gems are planning to do nothing about the switch to Skills. Google says it will convert every Gem automatically from 17 November 2026, so why bother? Because a converted Gem keeps working, but it does not get any of the things that make Skills better. It will not trigger on its own, it will not stack cleanly with other skills, and if it relied on knowledge files, some of them may not make the trip.
This guide explains what actually changes, why a one-to-one conversion wastes the upgrade, and a four-part rewrite that turns your best Gems into small, stackable skills in about 20 minutes each. You will also get a copy-paste prompt that does most of the rewriting for you.
What happens to Gemini Gems on 17 November 2026?
From 17 November 2026, Google starts converting Gems in personal Gemini accounts into Skills, including custom, premade and shared Gems. Gems keep working until they migrate. Workspace business, enterprise and nonprofit accounts follow from March 2027, and education accounts from June 2027. Skills are opened by typing a slash in the chat.
The timeline comes from the in-app banner and Google's help pages, as reported by Notebookcheck on 29 September and Android Central on 30 September. Skills reached Workspace on 5 October and the Gemini app on 13 October.
Four practical differences matter more than the name change:
--- Invocation: instead of opening a Gem from the side panel, you type / and pick a skill.
--- Stacking: you can use several skills in one conversation, for example a newsletter skill plus a brand-voice skill.
--- Auto-selection: Google says Gemini can recognise when a skill applies to your prompt, so you do not always have to call it.
--- Portability: skills use the open SKILL.md format, a plain Markdown file, so a well-written skill can move to other tools that support the same format.
Why should you rebuild a Gem instead of letting Google convert it?
A Gem was written to be one assistant you open on purpose. A skill works best as one narrow job that Gemini can pick up on its own and combine with others. An auto-converted Gem keeps its old shape: one long block of instructions, no clear trigger, and overlap with your other skills. Rebuilding fixes all three.
Think about a typical Gem called "Marketing Writer". Its instructions probably mix brand tone, banned words, three content formats, a target audience and a reminder to use British spelling. As a Gem, that was fine, because you chose when to open it.
As a skill, the same block causes problems. Gemini cannot tell from a vague description when it should apply, so either it never triggers or it triggers on everything. If you stack it with a separate "LinkedIn Post" skill, the two sets of tone rules can contradict each other. And because the format rules are buried halfway down, they are easy for the model to underweight.
The fix is to split by job, write a clear trigger, and add a self-check. The result is shorter skills that do one thing well and combine predictably.
How do you rewrite a Gem as a skill? The four-part method
Rewrite each Gem into four parts: a lowercase hyphenated NAME, a WHEN description that says exactly which requests should trigger it, numbered STEPS for the job itself, and a CHECK the model runs before replying. One job per skill. Anything shared across jobs, like brand voice, becomes its own skill you stack.
1. NAME. Google's upload rules require the skill name inside SKILL.md to be lowercase with hyphens, such as weekly-status-report. Name the job, not the persona. "client-email-reply" is better than "my-assistant".
2. WHEN. In the open SKILL.md format, the description field tells the model when to use the skill. Write it like a routing rule: what the request looks like, what inputs arrive, and what it should not handle. "Use when the user pastes meeting notes and asks for a status update for management. Do not use for client-facing emails." This one sentence decides whether auto-selection works.
3. STEPS. Turn your Gem's paragraph of instructions into a numbered procedure with the output format spelled out. Put hard rules (word limits, required sections, spelling) near the top, not buried at the end.
4. CHECK. End with two or three things the model must verify before answering, such as "every figure appears in the source" or "no section is longer than 80 words". This is the cheapest reliability upgrade you can make.
Here is a prompt that does the first draft for you. Paste your Gem's instructions where shown. It works in Gemini, ChatGPT or Claude.
Try this prompt:
I am migrating a Gemini Gem into one or more SKILL.md files. Here are the Gem's full instructions:
[PASTE GEM INSTRUCTIONS]
1. List every distinct job these instructions cover. If there is more than one job, propose one skill per job, plus one shared skill for rules that apply to all of them (tone, spelling, banned words).
2. For each skill, write a complete SKILL.md with a frontmatter block containing name (lowercase, hyphens only) and description (one or two sentences: when to use it, what input it expects, and what it must NOT be used for).
3. In the body, write numbered steps, the exact output format, and a final CHECK section with 2 or 3 tests the output must pass before replying.
4. Keep each skill under 300 words. Do not invent rules that are not in my original instructions. If something is ambiguous, list it under QUESTIONS FOR ME instead of guessing.
Read the QUESTIONS FOR ME list carefully. Those are the places where your old Gem was quietly relying on you to fill gaps.
What does a rebuilt skill look like in practice?
A single "Marketing Writer" Gem typically becomes three skills: a shared brand-voice skill, a LinkedIn-post skill and a product-update-email skill. Each has its own trigger and format, and you stack brand voice with whichever format the task needs. The writing gets more consistent because each rule lives in one place.
Here is the LinkedIn-post skill from that split, written in plain SKILL.md:
Example SKILL.md:
---
name: linkedin-post-draft
description: Use when the user shares a product update, event or result and asks for a LinkedIn post. Input is rough notes or a link summary. Do not use for emails, ads or replies to comments.
---
STEPS
1. Identify the single most useful fact for a professional reader.
2. Write a hook line of no more than 15 words that states that fact.
3. Write 3 short paragraphs: context, what changed, what the reader can do.
4. End with one question that invites a comment. No hashtags beyond 3.
FORMAT
Under 180 words. No emojis. Plain line breaks between paragraphs.
CHECK
- Every number and date appears in the user's notes.
- The hook would make sense without the rest of the post.
- If brand-voice rules are active, follow them over these steps.
Notice the last check line. When you stack skills, decide in advance which one wins on conflicts. Writing that rule into the format skill saves you from mixed results.
Upload is simple. In the Gemini app, go to Settings, then Skills, then Upload, and choose the SKILL.md file, or a .zip with SKILL.md in the main folder. Google's help page says files must be plain text, the total upload is capped at 100 MB, and hidden files such as .DS_Store can make an upload fail.
What can go wrong when you move from Gems to Skills?
The main risks are access and data, not prompting. Creating skills is reported to need a Google AI Pro or Ultra plan, skills require the Keep Activity setting, and skills built in the Gemini app do not sync with Workspace. Download any Gem knowledge files before November, because Google has not said which file types convert.
--- The paywall. AI Weekly, citing 9to5Google, reports that creating skills is limited to AI Pro and AI Ultra subscribers, while migrated Gems keep running. If you are on the free tier, rebuild and test your important Gems as SKILL.md files now, so you have portable copies whatever Google decides.
--- Keep Activity. Google's skills help page lists Keep Activity as a requirement and limits skills to users over 18. If you switched Keep Activity off for privacy, Notebookcheck notes you may not be able to use converted skills at all. With it on, some chats can be reviewed by people at Google and kept for up to three years.
--- Knowledge files. Google advises downloading Gem knowledge files first. Uploaded skills also accept only plain-text files, so PDFs and Word documents will need converting to Markdown or text.
--- Two separate libraries. A skill made in the Gemini app is not available in Gmail or Docs, and the reverse. Keep your SKILL.md files in one folder as the master copy.
--- No web calls. Scripts inside uploaded skills cannot reach the internet, so a Gem that "checks the website" needs a different approach.
--- Early bugs. In late September, testers reported the "Create skills" button doing nothing on some accounts. Check again before 17 November rather than assuming.
Try it now: migrate your most-used Gem in 20 minutes
Pick the one Gem you open most, copy its instructions, run the conversion prompt, fix the questions it raises, upload the result and test it with three real requests. Twenty minutes gives you a working skill, a portable backup and a clear view of whether your other Gems are worth rebuilding.
--- Minutes 0 to 5: open your Gem, copy the full instructions and download any knowledge files.
--- Minutes 5 to 10: run the conversion prompt and answer every item under QUESTIONS FOR ME.
--- Minutes 10 to 15: save each skill as SKILL.md, then upload through Settings, then Skills.
--- Minutes 15 to 20: test with three requests: one that should trigger the skill without a slash, one you call with /, and one that should NOT trigger it. Tighten the description if any test fails.
That third test is the one most people skip, and it is the one that tells you whether auto-selection will help or annoy you. If you want ready-made examples to compare against, our walkthrough of free AI employee skills shows what working SKILL.md files contain. Tools keep changing names; a well-scoped instruction keeps paying off. We understand AI. We understand you better. With UD by your side, AI doesn't feel cold.
Reviewed by the UD AI team. Dates and requirements reflect Google's in-app notice and help pages as reported by Notebookcheck, Android Central and AI Weekly between 28 and 30 September 2026. Plan access and migration details may change before 17 November.
How sharp are your AI skills really?
Writing tight skills is a test of how well you understand what AI needs from you. Check where you stand with UD's free AI IQ Test, and when you are ready to turn your prompts and skills into a workflow your whole team can rely on, we'll walk you through every step, from tool setup to workflow design and deployment.
