Gemini Gems become skills Nov 17 — Pro-only, not in the EU

Google is killing Gemini Gems and moving everyone to "skills" on November 17, 2026. Google says the migration is automatic and you do not have to do anything. That is true and it is not the point. Skills require a paid Google AI Pro or Ultra subscription, and they are not available in the European Economic Area, Switzerland, the UK or Nigeria. If you built your team's prompts as Gems on a free account, or you run in the EU, the migration is not a migration — it is a removal.

What actually happened to Gemini Gems

Users started seeing an in-app notice this weekend. 9to5Google reported the exact wording: "Gems will become skills starting Nov 17, 2026. Starting November 17, 2026, we'll automatically begin migrating your Gems to skills. You will be able to use your Gems until they migrate." TechCrunch picked it up on Monday.

Gems launched in 2024 as saved custom instructions you opened from a side panel. Skills, introduced with Gemini Spark, do the same job but live in the main chat — you invoke one by typing /, and you can stack several in a single prompt. Mechanically it is better.

The access terms are where it changes. Google's own help page states you must have a Google AI Pro or Ultra subscription to use skills in Gemini Apps, and that skills are unavailable in the EEA, Nigeria, Switzerland and the UK. Gems, by contrast, are free to every Gemini user today. Google's notice does not say what free-tier accounts get on November 18, and we are not going to guess.

Why your prompt library is a business asset you do not control

The work in a Gem is not the model. It is the instructions — your tone, your escalation rules, the six edge cases your intake process has, the format your bookkeeper actually wants. That is institutional knowledge. It took someone on your team real hours to write, and it currently lives in a text box on a vendor's server, with no export, on a feature the vendor just scheduled for deletion.

This is the ordinary lifecycle of a free platform feature, not a scandal. Google is allowed to do this. The lesson is about where you keep the asset, and the fix is boring: prompts belong in your repo, in plain text, versioned, with the vendor as the thing that reads them.

Three moves before November 17:

Copy every Gem's instructions into a file today. Not a screenshot — text, in a folder your team controls, one file per task. Do it now, while the Gems still open and the instructions are still readable.

Check who on your team is on a free account. If your customer-service Gem runs on someone's personal free login, that workflow stops working in seven weeks and nobody will file a ticket about it until a customer does.

If you operate in the EU or UK, plan for no replacement. Skills are not available there. A saved-prompt library you host yourself — even a shared text file and a paste step — does not have a regional availability page.

We build automations where prompts are files in your repository and the model vendor is swappable, because a feature you do not host is a feature on a countdown.

Sources: 9to5Google, Google Gemini Apps Help, TechCrunch.