Gemini Gems Become Skills on Nov 17: Migration Guide

If you built a custom assistant inside Gemini — a writing coach, a meeting-notes formatter, a study helper — Google is about to move it. On 17 November 2026, Gems on personal Google accounts become read-only, and a new system called Skills takes their place. The good news is that the replacement speaks a language many AI users already have on their computers: the SKILL.md file format shared with Claude.

This is not a story about losing your work. It is a story about a deadline, a draft folder you need to check, and a handful of things that quietly break in the move. Get those three right and the switch is mostly painless.

What is actually changing, and when

Gems, launched in August 2024, were custom versions of Gemini with saved instructions and attached reference files. You opened a Gem and chatted inside it, separate from your normal chats. Skills work differently: they are reusable instruction packs you call inside any ordinary chat, either by typing / (Google says this trigger is moving to @) followed by the skill's name, or by letting Gemini pick the right skill automatically when your prompt matches its description.

Google's own help page gives the timeline plainly, and it is worth quoting exactly because the two November/December dates are easy to confuse:

Two details in that table deserve emphasis. First, "read-only" does not mean "deleted": between 17 November and 17 December you can still see your Gems and download their knowledge files, but you cannot use or edit them. That one-month window is your safety net — use it. Second, the Workspace dates are floors ("no sooner than"), not promises that everything keeps working untouched until then.

What migrates automatically — and what you still have to do

Google says it will automatically turn your remaining Gems into skills, along with supported files. That sentence is reassuring until you read the next one: each migrated skill arrives as an inactive draft. You must review it and activate it before you can use or share it.

Put a reminder in your calendar for the week after 17 November: open Settings (or Customize) → Skills, and work through your drafts one by one. A draft you never activate is, for practical purposes, a Gem you lost.

Migrated skills keep the Gem's name, description, instructions and supported knowledge files, according to Google's transition guide. Three limits apply:

• A skill can hold at most 100 MB of files in total. If a Gem's attachments exceed that, Google drops the largest files first, so a heavy Gem needs manual attention before the deadline.
• Only 100 skills can be active at once. You can create more than that, but you will have to deactivate one to activate another.
• Some file types supported in Gems are not supported in skills yet, and GitHub files are not supported in skills. If a Gem depends on an unsupported file type, the automatic migration will not carry it over.

The Claude connection: why your SKILL.md file already works

Here is the part of the change most coverage misses, and the reason this migration is more interesting than a routine product shutdown. Skills are built on the open, markdown-based SKILL.md format — the same format Anthropic's Claude Code uses for its skills. In practice, a skill is a folder containing a SKILL.md file with a name, a description, and instructions, plus any reference files it needs.

That shared format is what makes cross-platform reuse real rather than theoretical. A hands-on test published by XDA Developers on 1 November 2026 found that Claude Code skills upload directly into Gemini: you can paste the name, description and instructions into Gemini's manual creation boxes, or upload a single SKILL.md file, a whole skill folder, or a zip archive with SKILL.md in its main folder. The skill name must be lowercase with hyphens between words — which is already how Claude skills are named.

One caution from that same test is essential: the difference between "uploads" and "works". Many Claude Code skills are built around Claude working through files on your own computer. That behaviour is mostly useless in a browser chat, and Gemini does not support scripts that need internet access. The XDA tester solved this by asking Claude to copy the skills into a new folder and rewrite those copies for chat-based research, leaving the originals untouched. That is the right pattern: migrate a copy, rewritten for chat, not the original coding skill verbatim.

There is a second lesson in the test. When Gemini picks skills automatically, the description field does most of the work — a skill whose description mentioned sketching a user-interface layout was triggered simply by asking for a UI layout. So when you review your migrated drafts, rewrite the description as a plain-language statement of when the skill should fire: what task, what input, what output. A vague description is a skill that never gets called.

One naming note: "skills" here is a Gemini product feature, related to but not the same as the open Agent Skills standard Anthropic donated to the Linux Foundation's Agentic AI Foundation in October 2026. The shared SKILL.md file is the bridge between them.

What breaks: the honest list

No migration guide is honest without the breakages, and this one has several that could genuinely surprise you:

• Five tools do not work with skills yet. According to XDA Developers and Google's own help pages, skills do not currently work with Deep Research, Guided Learning, Canvas, Create video, or Create music. A Gem built around one of these will not behave the same way after migration. If that Gem matters to you, do not wait for the automatic conversion — rebuild its workflow by hand now, or accept that its core trick is paused until Google adds support.
• Google Labs pre-made Gems will not migrate. Only your own Gems convert. If you relied on a Labs Gem, you will need to recreate its instructions yourself as a skill.
• Sharing and Drive files are coming, not here. Google's help page says that "in the coming weeks, skills will have the features you loved in Gems, including the ability to share them with others and add files from Google Drive and notebooks." Until then, a shared Gem workflow has no direct equivalent.
• Skills do not sync between the Gemini app and Workspace. If you use both, you must recreate the skill in each environment separately. The same applies to Gems used in Workspace Studio flows: the "Ask a Gem" step stops working in March 2027 and should be replaced with an "Ask Gemini" step.
• Opal goes away too. Google's help page notes that Opal, its experiment for building mini apps, retires at the same time as Gems in November.

None of this is a reason to panic — only a reason not to assume the automatic migration reproduces your setup exactly.

How to move a Gem yourself, step by step

If you would rather not wait — and for your most important Gem, you should not — Google's manual route is straightforward:

1. Save the knowledge files first. Open the Gem, click Edit, and download each attached file individually. Do this before 17 December 2026, while the read-only Gem is still accessible.
2. Create the skill. In the Gemini app, open Customize → Skills (or Settings → Skills, depending on what your account shows) and choose Create manually.
3. Copy the three essentials. Paste in the Gem's name, description and instructions, rewriting the description as a trigger statement: the task, the input, the output.
4. Reattach the files. Download the skill to get a .zip containing the new SKILL.md, move that file into your folder alongside the reference files, and upload the whole folder. Keep the total under 100 MB.
5. Test it on real input. Run the skill on last week's actual task and compare the result with what the Gem produced. A skill never tested on your real work is a guess, not a migration.

For a Claude skill, the steps are the same in reverse: copy the folder, rewrite file-manipulating or internet-dependent instructions for chat, then upload it to Gemini. Keep the original where it is; you are adding a Gemini version, not moving house.

Do you need to pay? The commercial question, answered honestly

This is the commercial slot, so let us be direct about money: you do not need to pay for skills. They work on Gemini's free plan in the Gemini app. Anyone telling you a subscription is required to keep your Gems alive is wrong, and that matters because the migration deadline is exactly the kind of moment where unnecessary upgrades get sold.

What a paid plan does buy is a stronger model and more headroom around the skill. As listed in the US in October 2026, Google AI Plus costs $4.99 a month and Google AI Pro costs $19.99 a month, before tax. The difference that matters most is the model: Plus runs on Flash and Flash-Lite, while Pro includes the frontier Gemini 4 Argon model and the Pro models — and from 13 November 2026, according to emails Google sent Plus subscribers, Pro model selection leaves Plus entirely. Pro also brings higher usage limits and more storage (5 TB against Plus's 400 GB).

So the honest buying guide is simple:

Prices are US list prices and can change, and they vary by country — always check Google's own subscriptions page before paying. Claude's own skills also work on its free plan, so the cross-platform trick here does not require two subscriptions either.

A final safety note before you import anything you did not write: read every file in a skill folder before uploading it, not just SKILL.md. A borrowed skill can contain instructions to fetch other files or send data somewhere. Gemini's sandbox does not give scripts internet access, which limits the damage, but reading the files first costs a minute and is still the right habit.

The checklist, in order

1. This week: list your Gems and rank them — which one would actually hurt to lose?
2. Before 17 November: download the knowledge files of your top Gems, and manually recreate the most important one as a skill to learn the process.
3. Week of 17 November: check your skills list for migrated drafts, and activate each one you still want.
4. Before 17 December: download anything left in a read-only Gem. After that date, personal-account Gems are gone from the app.
5. If you have Claude skills: copy, rewrite for chat, and upload — and rewrite the description so Gemini knows when to fire the skill.

Google is retiring a feature, but replacing it with something more portable than what it removes. A Gem lived inside Gemini. A skill, written as a SKILL.md file, can live in Gemini today and in Claude tomorrow. That portability is the real story of 17 November — provided you do the small amount of checking the automatic migration does not do for you.

Recommended Reading

If this migration has you thinking about working with AI as a collaborator rather than a search box, Ethan Mollick's Co-Intelligence is a practical guide to exactly that — where these tools shine, where they mislead, and how to check their work. Read more on Co-Intelligence at BookNest.

As an Amazon Associate, AI Trends Daily earns from qualifying purchases.

The featured image is an original AI-generated illustration, not a photograph. Sources: Google Gemini Apps Help, "About the transition from Gems to skills"; XDA Developers, "Gemini is replacing Gems with Skills, so I moved my Claude Code skills over to test them" (1 November 2026); Google's 30 September 2026 Skills announcement, as summarised in the XDA and BlazeTrends coverage. Prices are US list prices as reported in October 2026; check Google's subscriptions page before purchasing. This article is not investment advice.

Related reading on this blog: Gemini 4 Argon explained, ChatGPT vs Gemini vs Claude in 2026, how to write better AI prompts, and Google's Gemini small business hub review.