Google Gems Are Becoming Skills. Check Your Flows.

Google Gems are being replaced by skills, and the part of that change that can hurt you is not the part Google's headline covers. Your chat Gems will migrate on their own. The automations built on top of them will not. If anyone on your tea

Google Gems are being replaced by skills, and the part of that change that can hurt you is not the part Google's headline covers. Your chat Gems will migrate on their own. The automations built on top of them will not.

If anyone on your team set up a Workspace Studio flow with an "Ask a Gem" step, that flow stops working in March 2027. Nobody gets a pop-up when it does. The intake email just stops getting its draft reply.

The dates Google has actually published

We read Google's own posts, not the recaps. The September 30 Workspace Updates post lays out the transition for business accounts:

• October 13, 2026: skills start rolling out in the Gemini app, finishing by mid-November.
• November 17, 2026: Gems move into the Settings panel, but you can still create, edit and use them.
• No sooner than March 1, 2027: Gems can't be created, edited or used. Studio flows with an "Ask a Gem" step stop working.
• No sooner than June 1, 2027: the same cutoff for education accounts.

Personal Google accounts move earlier. Google's Gemini Apps Help page says Gems transition to skills starting in November 2026 for personal accounts, and in 2027 for work and school accounts.

One wrinkle changed after the post went up. Google's October 13 update says skills in the Gemini app did start rolling out that day. Skills in Workspace, the version that works inside Docs, Gmail and Studio, are delayed "until further notice."

"No sooner than" is Google's phrase, not ours. Treat March 1 as the earliest date and plan like it's the real one.

Auto-migration covers the chat Gems and skips the flows

Here is what Google says will happen on its own: remaining Gems in the Gemini app "auto-migrate to draft skills in the Gemini app." Here is what it says will not: skills "won't automatically appear in Workspace," so anything you want there has to be recreated by hand.

That split is where the trouble sits. A Gem you open in the Gemini app and chat with is a low-stakes thing. A Gem called by an automated flow is a different animal.

Google's Workspace Studio guidance is blunt about it. You can already no longer add an "Ask a Gem" step to flows. Existing steps keep working until the cutoff.

Flows with an "Ask a Gem" step will stop working. To keep your flows running, replace the "Ask a Gem" step with an "Ask Gemini" step before this date.

— Google Workspace Studio Help, Gems transition

Note what the fix is. You swap in a plain "Ask Gemini" step, paste in the prompt, and point it at a skill if you have access. Then you update every later step that used the old step's output. In a short flow that is a quick job. In a flow somebody built eight months ago and nobody documented, it's an archaeology project.

Sort your Gems into four piles

Start by listing every Gem and every Studio flow. Then sort.

Pile one: chat-only Gems. Instructions plus a few reference files, used by one person in the Gemini app. Let these auto-migrate, or rebuild the two you care about. Google's help page walks through copying the name, description and instructions into a new skill, and uploading knowledge files in a folder named after the skill.

Pile two: Gems wired into a Studio flow. These are the priority. Replace the "Ask a Gem" step with "Ask Gemini," and rebuild the Gem as a Workspace Studio skill once skills reach your domain. The Studio guide says you can also wait for skills to arrive before touching the step.

Pile three: Gems that lean on Gemini's other tools. Google's help page says that for now, most default tools available in Gems do not work with skills, including Canvas, Deep Research, Create video and Guided learning. It also says Opal and Gems by Google Labs go away in November. If your best Gem is really a Deep Research routine with a prompt attached, you will have a gap until Google closes it.

Pile four: shared Gems. Skills in the Gemini app don't have sharing yet. Google's October 13 post lists the ability to share them, and a Drive integration, as coming "in the coming weeks." If five people use one Gem you built, the day it converts is the day you have to work out who gets the new version.

A skill is an SOP, so write it like one

Google describes skills as "built entirely on the open, Markdown-native SKILL.md standard," and says you can copy skills you created on other platforms into the Gemini app. Its help page confirms you can upload a SKILL.md file to create one.

That matters more than the rename. A Gem was a text box inside Google. A skill is a file. Files can live in your own Drive, in a folder, in a repo, wherever you decide.

We have a view on this, and it comes from using the format every working day. The blog process behind this post is a SKILL.md file. So is our design-rule enforcement, which we wrote up in the taste-skill.md post. The lesson from running a business on them: the file is the asset, and the tool that reads it is replaceable.

So write each skill the way you would write a standard operating procedure for a new hire. State when it applies. Keep it short. Include two or three examples of output you'd accept. Google's own best-practice list for skills says the same thing: define when to use it, keep it concise, provide examples.

Then keep the master copy outside the tool. This is the second time in a month a major vendor has retired its custom-instruction bundle and told owners to migrate. We covered the first in the custom GPT retirement post, where OpenAI's migration carried instructions across but not the custom actions. Different vendor, same lesson. The instructions move easily. The wiring around them does not.

What to do this month and what can wait

Do now, because it costs an hour:

1. Open the Gems list in the Gemini app and write down every Gem, its owner, and who uses it.
2. Open Workspace Studio and list every flow with an "Ask a Gem" step. Note what each flow's output feeds.
3. Copy each important Gem's instructions into a document you own.
4. Ask your Workspace admin whether skills are on for your domain. Google's October 13 post says admins can manage skills in Workspace through admin controls, and that there are no admin controls for skills in the Gemini app.

Do later, once skills reach Workspace:

1. Rebuild the Studio skills and swap the flow steps.
2. Test each flow end to end with a real input, not a dummy one.
3. Re-share skills with the people who used the old Gems.

If you're on the cheaper Workspace tiers, remember the plan-gate pattern we described in the Gemini in Chat post: features get announced for "Workspace" and then land unevenly across plans. Skills in Workspace are listed for Business Starter, Standard and Plus, but check your own admin console instead of trusting the availability table.

When the Gem was holding a business process together

Most small businesses have three Gems and no flows. For them this is a short afternoon. Do it yourself and move on.

The picture changes if a Gem drafts your quote replies, scores inbound leads, or writes the first response to a customer email inside a Studio flow. That is a workflow, and the Gem is one step in it. When the step breaks, the output stops, and the people on the receiving end usually find out before you do.

That is the work we take on. Our workflow automation service audits the Gems and flows you rely on, rebuilds the ones that matter with a human approval step where a wrong output would reach a customer, and stores the master instructions in a place you own. We are a vendor, so weigh that. If your whole setup is two chat Gems, you don't need us.

If the setup is bigger, the same logic applies as with any agent you hand real access to. We wrote about what Google's separate Gemini agent with its own mailbox inherits from the accounts around it. A migrated skill inherits your old Gem's habits, including the bad ones. A migration is a good excuse to read what your Gem actually says.