Gemini can now decide on its own that a saved instruction set applies to what a person just typed, and run it without being asked. That capability belongs to Skills, the system replacing Gemini Gems, the saved personas people opened by hand from a side panel. Google is retiring Gems completely, and for most users the move takes zero manual work. What deserves attention is not the rename: Skills stack together and trigger themselves mid-conversation, something Gems never did.
Up to 100 skills can stay active at once, and any one of them can fire without being asked. The shutdown runs on three fixed dates: October 13, 2026, November 17, 2026, and March 2027.
Google announced the change on September 30, 2026, in a post by Deven Tokuno, senior product manager for the Gemini app, and detailed the mechanics in its own Gemini Apps support documentation. Anyone who built a Gem has three practical questions: when this happens, whether action is required, and what stops working. Sourced answers to all three follow, pulled from Google's own announcement and support pages rather than secondhand recaps.
Skills are rolling out to every Google AI subscription tier, not a paid-only feature layered on top of the free Gemini app. The one access restriction Google has confirmed is age: accounts under 18 do not have it yet, with support for younger users coming later.
Picture a freelance writer who saved three Gems: one for matching a client's tone, one for formatting invoices, one for drafting pitch emails. Switching between them meant leaving one conversation and opening another, with nothing carried over automatically. As skills, all three can sit active at once. A single prompt asking for a pitch email in a specific client's voice can pull the tone skill and the pitch-email skill into the same reply without the writer naming either, because Gemini matches the prompt to both on its own.
Gemini Gems to Skills: the migration timeline, verified
Personal Google accounts move first, Workspace accounts move later, and Google has published specific dates for both instead of a vague "coming soon." Individual Gemini app users lose the ability to create or edit new Gems after October 13, 2026, though existing Gems keep working past that point. The automatic switch to Skills for personal accounts lands on November 17, 2026. Workspace business, enterprise, and nonprofit accounts get a longer runway: Google says it will remove Gems no sooner than March 2027. Workspace education accounts, covering Classroom and other supported learning platforms, follow no sooner than June 2027.
Workspace admins get a separate rollout calendar for the skills feature itself. Google's Workspace Updates blog lists skills reaching Rapid Release domains between October 5 and 12, 2026, with Scheduled Release domains catching up between October 19 and mid-November 2026. That rollout is independent of the Gems shutdown: a Workspace user can see skills arrive months before their organization's Gems stop working, since Workspace Gems are not removed until March 2027 at the earliest. IT teams should not assume the two dates are the same thing.
Automatic migration, confirmed by Google
Migration is automatic. Google says directly that it will transition existing Gems, including supported knowledge files, into skills without the owner doing anything. A Gem owner who wants more control can rebuild it as a skill by hand before the cutoff and test it once, but waiting for the automatic switch is a supported path, not a way to lose the Gem. The exceptions are the handful of tools skills do not yet run, covered further down.
Google has not published a full list of which knowledge-file formats move over automatically. The one gap it does confirm is GitHub-linked files, which are not yet supported in skills. Everything else Google lists as a supported file type is expected to carry over, but anyone with a Gem built on an unusual file type should check it after the move rather than assume.
What changes when a Gemini Gem becomes a Skill
A skill can run itself without being opened, and several skills can stack in one reply. A Gem could do neither. Under the old system, a Gem was a persona opened on purpose from a side panel, used inside one dedicated conversation, with only one active at a time. Typing a forward slash and the skill's name inside any existing conversation runs a skill on demand. Gemini can also recognize when a saved skill matches what was just typed and apply it without being asked by name, a behavior Google calls self-invocation: Gemini matching a prompt to a saved skill and running it unprompted. Google's own announcement confirms skills can be stacked, combining, for example, a writing-style skill with a brand-guidelines skill in the same reply.
Self-invocation plus stacking is the upgrade a Gem never had. A single Gem could not hand off to another Gem mid-answer, and it could not decide on its own that a saved instruction set applied to a new question. Skills do both, turning a shelf of saved personas into a standing set of rules Gemini checks against every prompt.
| What changes | Gems (retiring) | Skills (replacing them) |
|---|---|---|
| How you run it | Open the Gem from a side panel and chat inside it directly | Type a slash plus the name in any chat, or let Gemini apply it automatically |
| Running more than one at once | One Gem per conversation, switching required to use another | Multiple skills can stack together in the same reply |
| Self-invocation | Never activates unless opened first | Gemini can recognize a matching prompt and apply the skill unasked |
| Active limit | No published cap on saved Gems | Up to 100 active at once; disable one to enable another |
| Tools it can call | Canvas, Deep Research, Create video, Create music, Guided learning | Not yet: Canvas, Deep Research, Create video, Create music, Guided learning |
| Creating or editing | Allowed until October 13, 2026 | Always allowed, no cutoff date |
| Sharing with others | Shareable today via a link | Sharing support is coming "in the coming weeks," per Google |
What happens to a Gemini Gem already built
A migrated Gem keeps its name, its instructions, and its supported knowledge files automatically. A short list of edge cases needs a manual check, covered below: GitHub-linked files, five specific tools, and shared Gems. Google built the migration to require no input by default, so the practical work for most people is verification, not rebuilding.
- Name, description, and the custom instructions typed into the Gem move into the matching skill unedited.
- Knowledge files in supported formats move with the skill automatically.
- Google creates the resulting skill under the same account, so the work that made the Gem useful does not need to be retyped.
A five-minute check before November 17 is enough for anything built with care, especially a Gem that leans on a file type or a tool outside Gemini's core chat:
- Any Gem pointed at a GitHub repository: skills do not yet support GitHub files, so that connection needs a manual rebuild.
- Knowledge files outside the commonly supported formats: confirm they appear in the migrated skill, and re-upload from a local copy if they do not.
- A Gem built around Canvas, Deep Research, Create video, Create music, or Guided learning: the instructions migrate, but the tool call itself will not run inside a skill yet.
- A Gem shared with teammates or shared publicly: confirm the shared version migrates the same way before relying on it past the cutoff.
A Gem built around any of the five tools listed above migrates with its instructions intact, but the tool call itself stops working until Google extends skill support to it.
What Google has not confirmed yet
One detail remains genuinely open: Google's support page says skills will gain the ability to share them with others "in the coming weeks," which implies shared and premade Gems are not yet handled identically to a Gem someone built alone. Anyone who shared a Gem with a team, or who relies on a premade Gem such as a brainstorming or writing-coach persona, should treat the shared version as unconfirmed until Google updates that page.
The real question Gemini's skills raise
Self-invoking, stackable skills are a real jump in what a saved instruction set can do inside Gemini. They also raise a question that applies to any tool that keeps context between sessions: what does it reuse without a visible prompt each time, and does the person using it see that happen. A skill that fires because Gemini decided a saved instruction matched the current prompt is convenient right up until it misfires.
A support lead saves a skill for the refund policy and another for the company's tone guide. Weeks later, a customer asks a question that is not about refunds at all, but the phrasing is close enough that Gemini matches it to the refund skill anyway and answers with policy language that does not apply. Nobody typed a command to call that skill. The agent sees a reply that sounds right and sends it, and only notices something is off when the customer replies confused, because the refund policy the skill quoted was never theirs to apply.
Every tool that remembers across sessions is quietly deciding what still counts as relevant to a new conversation. Gemini's skills just made that decision automatic instead of asked for.
The same question applies to ChatGPT's memory and Claude's project knowledge, not just a Gemini skill that decides on its own that it fits the current chat. MemX (memx.app) takes the opposite default: it only stores what a person explicitly saves from ChatGPT, Claude, Gemini, or their own documents, and nothing from that memory enters a new conversation unless the person brings it in. What MemX holds is private by architecture: per-user isolation and encryption at rest, not a shared pool a platform's own automation can draw from quietly. Skills are a genuine improvement to what Gemini can do inside its own chat window. They do not carry that context into ChatGPT or Claude, which was never a problem a Gemini-only feature could solve, and it is the gap a memory layer built to sit across all three is meant to cover.
Nothing needs rebuilding before October 13 unless a Gem depends on a tool skills do not run yet. The dates are fixed and the migration is automatic: the only real homework is a short list of specific things to double-check. Gemini's assistant just stopped waiting to be asked. Notice that part, even on the day nothing else breaks.
01When do Gemini Gems go away?
Personal accounts lose the ability to create or edit new Gems after October 13, 2026, and existing Gems automatically migrate to skills on November 17, 2026. Workspace business and enterprise accounts follow no sooner than March 2027, and Workspace education no sooner than June 2027.
02Do I have to manually migrate my Gems to Skills?
No. Google automatically transitions existing Gems, including supported knowledge files, into skills once the cutoff date arrives. Rebuilding a Gem as a skill by hand earlier is optional, for anyone who wants more control over the result.
03What can Skills do that Gems could not?
Skills run with a slash command in any chat, combine with other skills in the same reply, and trigger automatically when Gemini matches a prompt to one, without being opened first. A Gem ran alone, only after being opened from the side panel.
04Will my Gem's files transfer to the new Skill?
Supported knowledge files move automatically with the Gem. Skills do not yet support GitHub-linked files, so a Gem pulling from a repository needs a manual rebuild before or after the migration date.
05What stops working when a Gem becomes a Skill?
Skills do not yet run Canvas, Deep Research, Create video, Create music, or Guided learning. A Gem built around one of those tools keeps its written instructions but loses the tool call until Google adds support.
