Google notified users that it will migrate their custom Gems to a new "Skills" system starting November 17, 2026. Skills are triggered by typing "/" in the prompt box, several can run at once, and they're created in the Gemini Spark tab — but early reporting flags an access catch for free accounts.
2026-09-28 · by Moe Ameen
Google has started telling Gemini users that Gems are going away. A notice appearing in the Gemini app's Gems manager reads "Gems will become skills starting Nov 17, 2026," and Google says it will automatically begin migrating existing Gems to the new Skills format on that date — users don't have to do anything, and they can keep using their Gems until each one migrates. The change was spotted in the app and reported on September 27–28, 2026; a "Learn more" link in the banner pointed to a Google Support page that wasn't live yet at the time of reporting, so some specifics are still unconfirmed.
Gems, launched in 2024, are custom AI assistants: you give one a name, a set of instructions, and optional reference files, and it becomes a reusable helper for a specific job — a brainstorming partner, a coding assistant, a learning coach, a writing editor. Google later let users share their Gems with others. Skills are the successor concept, but the interaction model is different. Instead of opening a separate Gem from a side panel, you invoke a Skill inline by typing a forward slash ("/") in the main chat box, and you can apply more than one Skill in the same conversation. Skills are created and managed through the Gemini Spark tab, Google's agentic-assistant surface.
The catch reported alongside the change is access. Gems have been available to everyone, including free accounts. Skills, as observed at announcement, are tied to Gemini Spark and creating them currently requires a Google AI Pro or Ultra subscription. Whether free users will be able to use their migrated Skills — or will lose that functionality — wasn't clear from the in-app notice, and the missing support page is exactly where that detail would live. Treat the paid-tier framing as the current state, not a final policy, until Google publishes the documentation.
Commentators also noted the ergonomics. A slash-command interface is efficient for power users but less discoverable than a labeled list of assistants, and the timing lands as rivals push simpler, conversational customization — a contrast with Meta's Muse, where you shape an assistant by just talking to it. In short: the capability is being repackaged and arguably made more powerful (multiple Skills, inline invocation), while the on-ramp for casual and free users gets narrower.
The practical move here isn't to relearn a slash menu — it's to make sure the reusable part of your workflow doesn't live somewhere a vendor can migrate or gate it out from under you. A Gem or a Skill is a saved instruction set that shapes one chat. That's genuinely handy for drafting and ideation, but it's the most portable, least defensible layer of a content operation, and this change is a reminder of how quickly it can move. [Kompozy](/) puts the durable part — your voice and your output pipeline — somewhere it belongs to you. The [Persona Brief](/glossary/persona-brief) is your brand voice, tone rules, and banned words written down once and enforced across every format, so the "custom assistant" you'd rebuild as a Skill becomes a system you own rather than a preset in someone else's app.
From there Kompozy does the part a Skill fundamentally can't: it turns one idea or draft into a finished, cross-platform package. Fan a single source into a [Clipped Short](/glossary/clipped-short), talking-head [Persona Shorts](/glossary/persona-shorts), a brand-exact [Carousel](/glossary/hyperframes), quote graphics, native text posts, a blog, and a newsletter — then [Autopilot](/glossary/autopilot) schedules and publishes the set across the eight social platforms plus blog and email behind a per-post review gate. If Gemini is where you like to think out loud, keep doing that — a Skill can still draft a hook or an outline — and hand the result to Kompozy to caption, reframe, and ship. For the model context around this, see [Gemini Spark](/ai-tools/gemini-spark) and [Gemini Agent](/ai-tools/gemini-agent); if you're weighing Skills as your actual content workflow, the [Gemini Skills alternative](/alternatives/gemini-skills) lays out where a prompt preset stops and a content engine begins.
Google says it will begin automatically migrating Gems to Skills on November 17, 2026. An in-app notice in the Gemini app reads "Gems will become skills starting Nov 17, 2026." You don't need to do anything, and you can keep using your Gems until each one is migrated.
Skills are the successor to Gems — reusable, custom instruction sets for Gemini. The main differences are how you use them: you invoke a Skill by typing "/" in the chat box rather than opening a separate assistant, you can use multiple Skills in one conversation, and Skills are created and managed in the Gemini Spark tab.
Not clearly. Gems were available to all users, including free accounts. As reported at announcement, Skills are tied to Gemini Spark and creating them requires a Google AI Pro or Ultra subscription. Whether free users will retain access to migrated Skills wasn't confirmed in the in-app notice, and the linked support page wasn't live yet — check Google's documentation before relying on it.
No. A Skill is a saved instruction set that shapes how Gemini responds inside a chat. It can help you draft or ideate, but it doesn't caption clips, reframe video per platform, hold a persona across a calendar, or publish to any social account. Turning a draft into finished, scheduled posts across platforms is the job of a content engine like Kompozy.