Gemini Skills Replace Gems in Google Workspace

You spent an hour configuring a Gem so it drafts your meeting notes in the right tone, with the right sections, tagging each decision. It works well. And Google just announced it is going away. The news is annoying, but the reality is more nuanced: Google is not deleting the capability, it is replacing it with a more flexible mechanism called skills, and it gives you several months to handle the transition. The official Workspace Updates post from September 30, 2026 sets out the dates and the rules.

What a skill is, and why it differs from a Gem

A skill is a reusable, custom instruction that guides Gemini. A Gem was that too, so the difference is not obvious at first. It comes down to three concrete things. First, reach: a Gem only lived in the Gemini app, while a skill also works in most Workspace apps, Docs and Gmail included. Second, invocation: instead of opening a dedicated window, you type a slash followed by the skill’s name right in the prompt bar, and Google plans to switch to the at sign later. Third, combination: you can stack several skills in one prompt, for example a brand-voice skill with a summary-format skill.

The detail that matters for technical teams is the format. A skill is built on an open, Markdown-based file, the SKILL.md. Google frames this choice as a way to create, customize, and transfer instructions across tools without platform lock-in. For an organization that has already seen Gems trapped inside a single product, that is a real improvement, not a marketing line. A versionable text file lives in a repository, gets reviewed, and is shared like any other document.

Who gets it, and in which tool

Availability is not the same depending on where you work. In the Gemini app, skills are open to all Workspace editions, with no edition requirement. In Workspace apps, by contrast, access is limited to accounts aged 18 or older with Business Starter, Standard, or Plus; Enterprise Standard or Plus; Google AI Pro for Education; or the AI Expanded Access add-on.

That distinction has a direct consequence. An organization on an edition outside this list will see skills in the Gemini app, but not inside Docs, Gmail, Sheets, or the other apps. For that organization, a skill stays a chat tool, not an assistant embedded in the workflow. Before you promise anything to your users, check your edition in the admin console. This is the kind of nuance that turns an enthusiastic internal announcement into disappointment a few days later.

The timeline, read from today

The rollout has started. Skills have been reaching Workspace since October 5, 2026 for Rapid Release domains, finishing by October 12, and from October 19 for Scheduled Release domains, through mid-November. In the Gemini app, the rollout began on October 13, 2026 for all domains, with completion expected by mid-November. During this phase, Gems and skills coexist: you can keep creating and using both.

On November 17, 2026, Gems move to Settings in the Gemini app. They stay usable, but they leave the foreground, a clear signal of where this is heading. Actual removal comes later: no sooner than March 1, 2027 for business, enterprise, and nonprofit customers, and no sooner than June 1, 2027 for education. On those dates, users can no longer create, edit, or use Gems, and Workspace Studio flows containing the Ask a Gem step stop working.

The phrase “no sooner than” is worth pausing on. Google does not guarantee these dates as firm deadlines, it announces a floor. The transition can slip, but it cannot arrive earlier. For an admin, that means March 2027 is the date to write into the plan, not an estimate to take lightly.

The real friction: syncing and Workspace Studio

One technical detail deserves your full attention, because it decides how much work to expect. Skills do not sync between the Gemini app and Workspace apps. A skill created in one does not appear in the other. To use the same skill on both sides, you have to create it twice. Google will automate the conversion of remaining Gems from the Gemini app into skills, but those skills arrive as inactive drafts: each must be reviewed and then activated before use. Gems used in Workspace are not covered by this automatic migration and must be recreated manually in Google Workspace Studio.

For organizations that have industrialized their automations, the impact concentrates on Workspace Studio. Since the rollout began, the Ask a Gem step can no longer be added to a new flow. Existing flows that use it keep running until 2027, but they will stop abruptly on the cutoff date. Google documents two paths: replace the step with a skill, or fall back to a standard Ask Gemini step when no custom instruction is needed. Spotting the affected flows now avoids discovering a broken automation on the day it was supposed to run on its own.

What an admin should do now

The good news is there is no reason to panic: you have until March 2027. The bad news is that manually migrating critical Gems and Workspace Studio flows will not happen on its own, and it is easier to plan when spread out rather than crammed into a week of panic. Our recommendation comes down to three moves. First, confirm skills are turned on for your domain in the console and verify your edition. Then inventory the Gems actually in use, both in the Gemini app and in Workspace, separating the few critical instructions from the rest. Finally, rebuild those critical instructions as skills before the automatic migration, so you verify the behavior instead of inheriting it.

We view skills as an improvement for most teams: unified reach across chat and apps, slash invocation, and an open format answer real limits of Gems. But this is not a transparent update. The lack of syncing between the Gemini app and Workspace, combined with manual recreation in Workspace Studio, creates genuine work for organizations that had standardized on Gems. In other words, the more you invested in Gems, the more the transition asks of you. It is a textbook case of a change that is useful in daily use and costly at switchover.

This transition fits a broader move where Google unifies its AI around agents and workspace-wide context. If you are still weighing reusable instructions against full automations, our look at Gemini in Google Workspace helps place each tool. Skills fill the middle ground: more flexible than a throwaway prompt, lighter than a full agent.

Read also

• Google Workspace Studio: automate your business without coding
• Gemini in Google Workspace: what it changes for your business
• Temporary Admin Roles in Google Workspace: What Changes

You had standardized Gems across your teams and the switch to skills worries you before March 2027? We audit your Gems and your Workspace Studio flows, then rebuild the critical instructions as skills ahead of the automatic migration. Book a slot →