Gemini Skills Replace Gems: What Google Workspace Changes

Gemini skills are now rolling out across Google Workspace and the Gemini app, and Google has published a schedule for retiring Gems, the custom assistants it introduced earlier. According to the Google Workspace Admin Help page on the transition, skills begin reaching Workspace on October 5, 2026, and the Gemini app on October 13, 2026, with Gems moving into the Settings panel on November 17, 2026. Android Authority's summary of the timeline says both rollouts should complete by mid-November.

The change is small on the surface, a rename of a customization feature, but it reflects a broader shift. Google is adopting a skills format built on the open, Markdown-based SKILL.md standard that Anthropic published in December 2025, and the same format is now supported by several other vendors. This article explains what a skill is, how it differs from a Gem and a custom GPT, why the industry is converging, and what Workspace administrators should do.

Google

Gemini

Anthropic

OpenAI

Microsoft

What a Gemini skill is

Google describes skills as reusable custom instructions. In its announcement on the Google blog, the company says you can "save your most-used instructions once and run them endlessly." Users can create a skill from a chat, then call it by typing a forward slash followed by the skill name in the prompt bar. Skills can be combined, and they support reference files such as plain text documents, PDFs and images.

The Google Workspace Updates post and the admin documentation add the structural details that matter: skills are built on an open, Markdown-based SKILL.md format, they are available in both Gemini and Workspace apps, and several skills can be layered in a single prompt rather than being tied to one conversation.

Skills vs Gems vs custom GPTs

The three concepts overlap, but they package customization differently.

The Gem and custom GPT columns reflect how Android Authority describes Gems (assistants built for individual tasks) and how a summary of OpenAI's own guidance positions skills relative to GPTs. A Custom GPT packages a specialist assistant, while a skill packages a repeatable way of working. That distinction explains the design choice: a person who wants a consistent meeting-summary format applies the same skill in whichever chat they are already using, instead of moving the work into a dedicated assistant.

The SKILL.md standard and progressive disclosure

Anthropic released Agent Skills as an open standard on December 18, 2025, with documentation at agentskills.io. Its stated aim is interoperability: a capability written for one platform should work on others. The Decoder reported that OpenAI had already adopted the framework, and that partners including Notion, Canva, Figma and Atlassian had published skills. Google's use of SKILL.md extends that list.

The specification is compact. A skill is a directory containing a required SKILL.md file with YAML frontmatter (a name of up to 64 characters and a description of up to 1,024 characters) followed by Markdown instructions. Optional folders hold scripts, reference documents and assets.

The design principle is progressive disclosure, which the specification describes in three tiers:

1. Metadata (about 100 tokens): the name and description of every skill are loaded at startup.
2. Instructions (under 5,000 tokens recommended): the full SKILL.md body loads only when the skill is activated.
3. Resources: scripts and reference files load only when a task needs them.

This is the technical reason skills scale where a long system prompt does not. An assistant can know about dozens of skills while spending context only on the one or two relevant to the current request.

Why vendors are converging on skills

Several pressures point in the same direction, though the sources above do not state vendor motives, so the following is analysis rather than reporting.

• Portability. A shared file format lets one team write a skill once and reuse it across tools. Google's documentation highlights that skills written elsewhere can be copied into Gemini and Workspace.
• Context economics. Progressive disclosure keeps large libraries of instructions affordable, which matters as assistants take on agentic, multi-step work.
• Composability. Real tasks rarely map to one persona. Stacking a style skill with a research skill is easier than choosing between two dedicated assistants.
• A precedent in tooling. The industry has seen shared protocols reduce integration work before. Unite.AI draws the comparison to Anthropic's earlier Model Context Protocol, which became widely adopted.

The counterweight is that a common file format does not guarantee identical behavior. Different models interpret the same instructions differently, and fields such as tool permissions are marked experimental in the specification, so portable does not mean interchangeable.

Migration: what happens to existing Gems

According to Google's admin documentation, Gems remain usable during the transition. On November 17, 2026 they move to Settings in the Gemini app. No sooner than March 1, 2027 for business and enterprise customers, and no sooner than June 1, 2027 for education customers, Gems can no longer be created, edited or used. Remaining Gems are then auto-migrated to draft skills that require manual activation, and Drive permissions and sharing settings carry over to the corresponding skills. Google's consumer announcement lists November 2026 for personal accounts.

Two practical constraints stand out:

• Skills do not sync between the Gemini app and Workspace. A skill needed in both places must be created in both, per Android Authority.
• Workspace Studio flows that use the "Ask a Gem" step will stop working at the sunset date, and new "Ask a Gem" steps can no longer be created, according to the same report.

Admin controls and a checklist

The Admin Help page lists the actions Google expects from administrators:

1. Tell users the transition dates.
2. Enable skills for the organization.
3. Encourage people to rebuild business-critical Gems as skills before the deadline.
4. Update Workspace Studio flows that depend on "Ask a Gem."
5. For education domains, distribute transition guides to educators.

Rollout timing varies by release track: Rapid Release domains see skills from October 5 to 12, while Scheduled Release domains follow from October 19 into November.

What to watch

Several questions remain open. Draft skills created by auto-migration need a person to activate them, so inactive Gems could become inactive skills. The lack of sync between Gemini and Workspace may change as the rollout completes. And as more vendors support SKILL.md, organizations may begin keeping skills in version control, independent of any single assistant. Teams already working across several models, including in model-agnostic workspaces such as Metir, are likely to feel that portability most.

Sources:

• Google Workspace Updates: Introducing skills in the Gemini app and Workspace, plus what's next for Gems
• Google Workspace Admin Help: About the transition from Gems to skills
• Google Blog: Let skills in Gemini tackle your most repetitive tasks
• Android Authority: Google maps out transition plan to replace Gemini Gems with Skills
• Agent Skills specification (agentskills.io)
• The Decoder: Anthropic publishes Agent Skills as an open standard for AI platforms
• Unite.AI: Anthropic Opens Agent Skills Standard
• Dig.watch: ChatGPT may move beyond GPTs as OpenAI develops new Skills feature

Image credits

• Hero: Google logo on the Googleplex headquarters building, Mountain View. Googleplex HQ (cropped).jpg by Asoundd, licensed CC BY-SA 4.0.
• In-body: Google logo on a Googleplex building. Outside Googleplex in Mountain View, California.jpg by David Nagle, licensed CC BY-SA 4.0.