Google Just Killed Gemini's Gems. The Real Story Is What It Replaced Them With.

Google is retiring Gems, the custom-assistant feature it launched inside Gemini in 2024, in favor of something called “skills.” Most of the coverage this week treated it as a straightforward rebrand. The detail worth actually noticing — easy to skim past, buried a few paragraphs into most of the reporting — is what format Google chose for the replacement: a folder containing a SKILL.md file plus optional reference files. That’s not a Google invention. It’s the same open Agent Skills standard Anthropic built for Claude, the format behind the Cloudflare security-audit-skill we covered last week and the backbone of Anthropic’s new Claude Marketplace.

What’s actually changing, with real dates

• September 30, 2026 — skills became generally available in Gemini chat, no longer gated behind the Gemini Spark tab or a Google AI Pro/Ultra subscription.
• November 17, 2026 — Google begins automatically migrating existing Gems to skills for personal accounts. You don’t have to do anything; your Gems keep working until the migration happens.
• March 2027 — the equivalent deadline for Google Workspace accounts, giving enterprise users a longer runway than personal accounts.

Mechanically, skills work differently from Gems in a way that’s a genuine workflow shift, not just new branding: instead of opening a saved custom assistant, you invoke a skill mid-conversation by typing /, and you can combine several skills within a single task. Gems were a persona you opened. Skills are a composable instruction you call in.

Why the format choice is the actual story

Anthropic’s Agent Skills standard — a folder with a SKILL.md file describing what the skill does and how to use it, plus any supporting reference files — was built for Claude and Claude Code. We’ve now covered three separate instances of it extending well past Anthropic’s own products in the space of a week: Cloudflare’s security-audit-skill, Anthropic’s own Claude Marketplace (built on MCP and Agent Skills together), and now Google adopting the identical file structure for Gemini.

That’s a real standards convergence, and it’s worth being precise about what it does and doesn’t mean. It does not mean a skill built for Claude Code will behave identically if dropped into Gemini — the underlying model, available tools, and runtime behavior still differ by platform, and nothing here guarantees full behavioral portability. What it does mean is that the packaging — how instructions and reference material are structured and described — is converging on one shared shape across competing vendors, which lowers the cost of adapting a skill from one ecosystem to another compared to starting from a completely different format each time. Reporting on the shift explicitly frames it as Google “joining OpenAI and Anthropic in the shift to agent-ready prompt formats” — this is genuinely an industry pattern, not an isolated Google decision.

The practical caveats, before you assume this is fully rolled out

A few real limitations worth knowing if you’re evaluating this now rather than waiting for the November migration:

• Regional availability gaps. As of the September 30 rollout, skills are not available in the European Economic Area, Nigeria, Switzerland, or the UK. If your workflow or your team spans those regions, the migration timeline doesn’t apply uniformly.
• Account requirements. Skills currently require a personal Google account, being 18 or older, and having Keep Activity turned on — real gating conditions, not a universal rollout to every Gemini user.
• Not full feature parity yet. Multiple outlets note that some things Gems could do aren’t obviously replicated by skills yet. If you have a Gem doing something specific and non-trivial, don’t assume the automatic migration preserves 100% of its behavior — worth testing your actual Gems against the skills equivalent before November 17 rather than discovering a gap after the automatic cutover.

What to actually do if you use Gems today

1. Inventory your existing Gems now, particularly any doing something beyond simple custom instructions — before the automatic migration, while you can still compare old and new behavior side by side.
2. If you’re outside the four excluded regions, you can create skills directly today rather than waiting for the Gems migration, which gives you a chance to test the new format on terms you control.
3. If you build tooling across multiple AI platforms, this convergence is worth tracking structurally — a shared skill-packaging format across Anthropic, Google, and reportedly OpenAI’s direction too means the time you invest learning the SKILL.md structure has a longer shelf life than learning any one vendor’s proprietary assistant format.

Official reference: Google’s own Gemini Apps Help documentation and its September 30 announcement (“Let skills in Gemini tackle your most repetitive tasks”), cross-checked against 9to5Google, TechCrunch, and AI in Context’s reporting on the Anthropic-standard framing, all dated September 27-30, 2026. Rollout details and regional availability are the kind of thing that shifts quickly post-launch — confirm current status in your own Gemini account before relying on specifics here.