What Gemini skills mean for your Gems and Opal tools

Gemini skills are replacing Gems inside Google's AI assistant, with firm shutdown dates attached this time. Personal Gemini accounts lose Gems in November 2026. Workspace business, enterprise, and nonprofit plans lose them in March 2027, and education plans in June 2027. Every existing Gem migrates automatically. Opal, Google's separate tool for building mini apps, shuts down in November too, and nothing you built there carries over.

Plenty of small operators built a Gem or two this year: a customer-reply assistant trained on an FAQ, a quoting Gem fed a price sheet, a tone-of-voice Gem for social captions. Those still work today. The question is what happens to them, and to anything built in Opal, once the clocks above run out.

What a Gemini skill actually is

A skill is a saved instruction set you call up by typing a slash and its name in the Gemini prompt bar, instead of retyping the same setup every time. Gemini can also watch your chats, notice a pattern, and offer to save it as a skill on its own. You can stack more than one skill in a single conversation, and a skill can now carry reference files: a PDF price sheet, a brand style guide, a product spec, so Gemini answers against your actual documents instead of a prompt you keep rewriting from memory.

Why Gemini skills beat the old Gems setup

Gems were static personas: a block of instructions you set once and reused. Gemini skills do more. They attach files, they combine with each other, and in Workspace they get a real build process. Someone drafts a skill in a Google Doc with the skill builder, the team comments and edits it like any shared doc, then it gets turned on in Workspace Studio for everyone. That beats a personal Gem one person set up that nobody else on the team can see or improve.

The Opal problem: nothing migrates

Opal, Google's Labs tool for building small apps from a prompt, shuts down in November 2026, the same month personal Gems disappear. Gems get carried into skills automatically. Opal apps do not. If anyone on your team used Opal this year to spin up an internal tool, a quick intake form, a simple calculator, a lookup app, it needs to be exported, documented, or rebuilt as a skill or a real app before the shutdown. After that, it is gone for good.

1. 1

   Audit your Gems

   List every Gem your business uses and who built it. Note what each one is for, since the auto-migration keeps the instructions, but you should confirm the result still behaves the way you expect.

2. 2

   Export anything built in Opal

   Opal apps do not migrate. Save the prompt, logic, and output format for anything built there so it can be rebuilt as a skill or a standalone tool.

3. 3

   Test the migrated skill before you rely on it, with the real documents attached

   Once a Gem flips over to a skill, run it on a real task before your team trusts it again, and attach the actual price sheet or style guide rather than a prompt that just describes one. A skill built from the real file answers differently than one built from a description of it.

If your team has a Gem, an Opal app, or a Workspace Studio flow doing real work right now, this is a reasonable moment to have someone walk through what breaks, what migrates cleanly, and what is worth rebuilding properly instead of just carrying forward. Happy to look at yours.