← All posts / Tools

Gems Are Dead, Skills Are Live: Google Starts the Gemini Skills Rollout in Workspace Today

Starting October 5, Google begins replacing Gemini Gems with stackable, Markdown-native Skills across Workspace — here is the full timeline, what changes for admins and users, and why the SKILL.md standard matters.

Gems Are Dead, Skills Are Live: Google Starts the Gemini Skills Rollout in Workspace Today

For months, Google has been teasing a world where its AI assistant remembers how your team works. Today that world starts arriving on production accounts. On October 5, 2026, Google begins rolling out Skills in Google Workspace, the feature that will replace Gemini Gems as the standard way to give Gemini reusable, custom instructions — and with it comes a deprecation timeline that every Workspace admin should put on their calendar right now.

What is rolling out today

Skills are reusable, custom instructions that you can invoke any time you’re prompting Gemini — in the Gemini app and across most Workspace apps. Think of them as portable prompt playbooks: a “brand voice” skill that keeps every blog draft on-message, a “lesson planning” skill that saves teachers an hour of prep, or an “invoice review” skill that compares new invoices against the latest ones sitting in your inbox and flags discrepancies before an overworked teammate has to.

The October 5 rollout targets Workspace domains on the Rapid Release track, with completion expected by October 12. Scheduled Release domains follow the same window shifted later. Google says the full Workspace rollout should complete by mid-November. Then, on October 13, Skills begin rolling out in the consumer Gemini app as well.

Importantly, this is a staged deployment, not a flip-a-switch launch. If Skills haven’t appeared in your domain yet, that’s expected — but admins can already enable the underlying capability: Skills in Workspace are available to organizations whose administrators have turned on the Gemini Beta setting in the Admin console.

Skills vs. Gems: what actually changes

On the surface, Skills look like Gems with a new name. They’re not. Three differences matter in daily use:

Skills stack; Gems didn’t. Skills function inline in your unified chat threads, which means you can layer multiple sets of custom instructions in a single prompt. An educator can combine a “weekly newsletter” skill with an “institutional brand guidelines” skill to get on-brand communications in one step. A business user can pair a “vendor evaluator” skill with an “executive email drafter” skill — analyze three vendors and draft the recommendation memo without a second round-trip. With Gems, each was its own walled-off persona; you picked one and stayed inside it.

Skills are Markdown-native and portable. Skills are built entirely on the open SKILL.md standard. That has a practical consequence Google doesn’t bury but doesn’t shout either: you can copy skills you’ve created on other platforms directly into the Gemini app and Workspace apps, and upload popular external skills from the web into Drive, then reference them in Workspace Studio. In a market where every vendor wants to lock your prompt library into their silo, an open interchange format is the rare genuinely customer-friendly move — and a small win for interoperability that other assistant makers will feel pressure to match.

Skills live across surfaces. Gems lived in the Gemini app only and couldn’t be used in Workspace apps at all. Skills work in the Gemini app, in the Gemini side panel inside Gmail, Docs, Slides, and Drive, in Ask Gemini in Chat, and inside Workspace Studio flows. Google is unifying instruction-following across its entire productivity estate.

One caveat worth knowing: skills currently do not sync between the Gemini app and Workspace apps. If you want a skill on both platforms, you have to create it separately in each — an awkward gap Google will presumably close, but for now it means duplicate work during the transition.

The deprecation timeline for Gems

Google has published an unusually precise kill schedule for Gems:

  • October 5, 2026 — Skills begin rolling out in Workspace (Rapid Release first, completing by October 12; full completion by mid-November).
  • October 13, 2026 — Skills begin rolling out in the Gemini app, completing by mid-November.
  • November 17, 2026 — Gems move to the Settings panel of the Gemini app. Users can still create, edit, and use them.
  • No sooner than March 1, 2027 (business/enterprise) — Gems can no longer be created, edited, or used. They’re removed from the Settings panel. Workspace Studio flows using the “Ask a Gem” step stop working. Any remaining Gems are auto-migrated to draft Skills in the Gemini app.
  • No sooner than June 1, 2027 (education) — the same cutoff, extended for schools, including Google Classroom and third-party LMS platforms supported by Gemini LTI.

Google says it will share auto-migration details with admins at least 30 days in advance. Two things already changed: you can no longer create Workspace Studio flows with the “Ask a Gem” step (existing flows keep working), and education customers get their own transition guide.

The enterprise angle: governance and a coming marketplace

For admins, the interesting part isn’t the prompt mechanics — it’s the control plane. Skills are managed through Workspace Studio, which Google positions as a centralized control room for delegating work to AI. Teams can build skills manually or with Gemini’s help, test outputs in real time before rolling them out, and share skills across the organization under existing security policies.

Two forward-looking pieces are worth tracking. A Workspace Marketplace for skills is coming, letting organizations publish their internal know-how for others to discover. And administrators will be able to curate, manage, and distribute verified organizational skills across departments via the Agent Registry, spanning both Gemini Enterprise and Workspace. In other words, Google is building the plumbing for organizational prompt governance — versioned, auditable, centrally distributed instructions rather than everyone’s private copy-paste library.

Why this matters beyond Google

The Gems-to-Skills transition is a small feature swap on its face, but it signals where assistant platforms are heading. Custom instructions are becoming modular, composable, stackable units — closer to software dependencies than chatbot personas. The choice of an open, Markdown-based file format (SKILL.md) means prompt engineering artifacts are becoming portable assets you can version in git, review in PRs, and move between vendors. The assistant that wins enterprise workflows won’t be the one with the best system prompt; it’ll be the one where your team’s accumulated operational knowledge — the invoice review checklist, the proposal template rules, the brand voice guide — travels with the model, not against it.

For Workspace customers, the action items are concrete: enable the Gemini Beta setting if you want Skills during the rollout window, start recreating high-value Gems as Skills now rather than waiting for auto-migration, and mark March 1, 2027 (business) or June 1, 2027 (education) on the roadmap — that’s when the Gem-era workflows stop working whether you’re ready or not.