How to Migrate Gemini Gems to Skills: A Step-by-Step Guide Before the November 2026 Deadline

Introduction

If you built custom Gemini Gems for recurring work, Google is about to change how you use them. On September 30, 2026, Google announced that Skills, reusable custom instructions invoked directly inside any Gemini chat, will replace Gems. Gems begin disappearing from personal accounts in November 2026, while Workspace accounts get until 2027. Google promises automatic migration, but manually migrating while every setting is still editable is the safer path. This tutorial covers the full migration: auditing your Gems, backing up instructions and files, recreating each one as a skill, testing it, and fixing the Workspace Studio flows that will break.

Quick answer

To migrate a Gemini Gem to a Skill, open gemini.google.com, go to Settings, then Skills, click Create manually, and copy your Gem’s name, description, instructions, and knowledge files over. Finish before Google’s automatic migration starts on November 17, 2026.

Evidence: what Google has actually confirmed

Two official sources define everything here. The first is Google’s announcement post on The Keyword, published September 30, 2026, which states that skills rolled out into Gemini chat globally that day, with Workspace customers to follow in the coming weeks. The second is Google’s Gems-to-skills transition guide in the Gemini help center, which documents the manual recreation steps and the retirement schedule.

The retirement is staggered, and Google’s help center names three dates. November 2026: Gems go away for personal Google accounts. March 2027: Workspace business, enterprise, and nonprofit accounts lose the ability to create, edit, or use Gems. June 2027: Workspace education accounts follow, with Gems also removed from Google Classroom and learning systems connected through Gemini LTI. The same page confirms that Opal, Google’s mini-app experiment, and Gems by Google Labs go away in November as well. Google phrases the 2027 cutoffs as “no sooner than,” so the runway could be longer, not shorter.

For personal accounts, the in-app deprecation banner spotted by Android Authority sets two nearer milestones: Gems become skills on November 17, 2026, and you cannot create or edit Gems starting October 13, 2026, though you can keep using them until the migration. Per Google’s help page, skills are currently available only to individuals over 18 with a personal Google account.

Google explains the motivation in its own transition guide:

Later this year, we’re transitioning from Gems to skills to give you an even better, more flexible way to customize Gemini. Skills will let you do more, like using them right in your current chat without having to switch tabs. You can also stack multiple skills together, to create even more customized workflows.

A Gem was a separate persona you opened from a sidebar, with each chat living inside one Gem at a time. A skill is a reusable instruction block that travels across chats: invoke one by typing / followed by its name, let Gemini apply a relevant skill automatically, or stack several in one conversation. Skills are also built on the open, Markdown-native SKILL.md standard, so a skill written for one platform can be copied into another. To understand that format in depth, read our n8n agent skills tutorial.

Prerequisites

Before you start migrating, make sure you have the following:

• A personal Google account, with the account holder aged 18 or older. Skills are not yet available on work or school accounts as of October 2026.
• Gemini’s Keep Activity setting turned on. Google’s skills documentation requires this: with it off, Gemini will not remember your skills or suggest them.
• A desktop browser logged in at gemini.google.com.
• A list of every Gem you own. Open the Gems manager in the sidebar and write down each name.
• A local folder for backups. You will download each Gem’s knowledge files individually, because Google’s docs state that bulk download is not supported.
• If you use Google Workspace: find Flows in Workspace Studio that use an “Ask a Gem” step. New flows cannot use that step, and existing ones stop working when Gems are removed.

Step-by-step guide

Step 1: Audit your Gems before editing is locked

Open the Gems manager in the gemini.google.com sidebar. For each Gem, record four things: its name, its description, its full instruction text, and the list of knowledge files attached under “Knowledge.” Also note which Gemini tools the Gem relies on, because several Gem capabilities do not work with skills yet: Canvas, Deep Research, Guided Learning, Create video, and Create music are all unsupported in skills as of October 2026. A Gem built around Deep Research cannot become a one-to-one skill today; flag it for redesign instead of a straight copy.

Migrate the Gems you use weekly first; rarely used ones can wait for Google’s automatic migration, which converts leftovers into draft skills.

Step 2: Back up each Gem’s instructions and files

For every Gem you plan to migrate manually:

1. Open the Gem and click Edit next to its name.
2. Copy the Gem’s name, description, and instructions into a document you own, such as a Google Doc or a local text file. This text is the core of the backup: it teaches the skill how to behave.
3. If the Gem has files under “Knowledge,” download each one to your computer. Google’s transition guide is explicit that knowledge files must be downloaded individually; there is no bulk export. Put each Gem’s files in its own folder named after the planned skill, for example brand-voice-editor.

Step 3: Create the skill from your Gem’s content

Google’s transition guide documents this flow:

1. Open a new browser tab and go to gemini.google.com.
2. On the sidebar, click Settings, then Skills.
3. Near the top of the Skills page, click Create manually.
4. Copy and paste the name, description, and instructions from your Gem into the skill. Google notes that the skill’s name will automatically update to the correct format.
5. At the top of the skill, click Create.

If your Gem had no knowledge files, you are done: the skill now exists and can be invoked in any chat.

Step 4: Re-attach the knowledge files

If your Gem used knowledge files, Google’s guide adds a file step: to add files, download your skill and upload it with your files. Collect the files from Step 2 and upload them all at once when creating or editing the skill, rather than one at a time as you downloaded them.

Two constraints apply, both from Google’s documentation. You can already upload skills that include text files, PDFs, and images today, but GitHub files are not supported in skills. If your Gem pulled files from a GitHub repository, download them to your computer first and upload the local copies. Sharing, Google Drive attachments, and Gemini Notebook support are coming in the following weeks, so if your Gem depended on Drive files, re-check after that lands.

Step 5: Test the skill the way you will actually use it

Open a fresh Gemini chat and test three things. Manual invocation: type / in the prompt box and select your skill by name. Use a prompt you already ran against the original Gem so you can compare outputs. Automatic detection: start a new chat without invoking the skill and enter a prompt that matches its purpose; Google says Gemini applies a relevant skill automatically, so check whether it engaged. Stacking: invoke two related skills in one chat, for example a writing-style skill plus a brand-guidelines skill, and confirm the output respects both. This stacking is the capability Gems never had, and it is where the migration pays off.

If the output is worse than the Gem’s, tighten the skill instead of deleting the Gem: Google’s best practices say to define exactly when the skill applies, keep instructions focused on the unique guidelines, and include concrete examples of expected output.

Step 6: Fix Workspace Studio flows that use “Ask a Gem”

This step is for Workspace users and prevents a real outage. Per Google’s Workspace Updates announcement, you can no longer create Studio flows with the “Ask a Gem” step, though existing flows keep working until Gems are removed: no sooner than March 1, 2027 for business and enterprise accounts, and no sooner than June 1, 2027 for education accounts.

In Workspace Studio, find each Ask a Gem step and rebuild it around the equivalent skill from Step 3, since Studio supports skills as flow components. Test the rebuilt flow end to end well ahead of the deadline: this failure is a hard break, not a graceful degradation.

Step 7: Decide what to leave for automatic migration

After manually migrating your important Gems, decide what happens to the rest. Google says it will automatically transition your remaining Gems, along with any supported files, to skills when Gems go away. The converted skills arrive as drafts, so you can review them before relying on them. Two exceptions: Gems by Google Labs will not migrate, and any Gem depending on features that do not work with skills yet will arrive in reduced form.

Manually migrate anything tied to revenue, clients, or daily work; let automatic migration handle experiments and one-off helpers, then review each draft skill. To go deeper, our MCP server tutorial shows how to connect external tools to AI assistants, and our n8n vs Make comparison for AI agents covers which automation platform fits agent-driven workflows.

Troubleshooting

The Skills page or the “Create manually” button is missing

Three likely causes. First, the rollout is gradual: skills reached Workspace Rapid Release domains starting October 5, 2026 and the Gemini app starting October 13, 2026, with both expected to complete by mid-November. If your account is not in the rollout wave yet, the page appears on its own. Second, you may be signed in with a work or school account, for which skills are not available yet; switch to a personal Google account to check. Third, Google’s help page lists age 18 or older as a hard requirement for skills in Gemini chat.

A knowledge file will not attach to the skill

Check the file type first. Google supports text files, PDFs, and images in skills today, but explicitly states that GitHub files are not supported. If your Gem referenced a file hosted on GitHub, download it to your computer and upload the local copy instead. Also remember the asymmetry: files come out of a Gem one at a time, but upload into a skill all at once. If a file seems missing, go back to the Gem and download it individually.

The skill does not engage in chat

If typing / shows no skills, or Gemini never applies your skill automatically, check the Keep Activity setting. Google’s skills documentation requires it to be on: with Keep Activity off, Gemini does not remember which skills you created or when to suggest them. Turn it on, start a new chat, and try again. If the skill appears but never auto-engages, the cause is usually vague instructions. Edit the skill to state explicitly when it should be used and add an example of the expected output, following Google’s published best practices for effective skills.

The automatically migrated skill behaves differently from the original Gem

Automatic migration recreates Gems as draft skills, and Google is candid that only supported files and features carry over. Anything your Gem did with Canvas, Deep Research, Guided Learning, Create video, or Create music will not survive, because those tools do not work with skills yet. Treat the draft as a starting point: compare its instructions against your Step 2 backup, re-add what the migration dropped, and test it with a real prompt before discarding the backup.

A Workspace Studio flow breaks with an “Ask a Gem” error

This happens when the flow runs after Gems are removed from your account type, or when someone edits a flow that still references the retired step. Open the flow in Workspace Studio, locate the Ask a Gem step, and replace it with the skill from Step 3. Re-run the flow with test data before returning it to production. You cannot create new flows with the Ask a Gem step even now, so any duplicated flow needs the skill-based version from the start.

FAQ

Will Google automatically migrate my Gems to Skills?

Yes. Google says it will automatically transition your Gems, along with any supported files, to skills when Gems go away, starting November 17, 2026 for personal accounts. Manual migration is still recommended for the Gems you depend on, because the automatic version arrives as a draft and may drop unsupported features.

When exactly do Gems stop working for personal Google accounts?

In November 2026. The in-app banner in the Gemini app says your Gems become skills starting November 17, 2026, and that you cannot create or edit Gems from October 13, 2026 onward. You can keep using existing Gems until each one migrates.

What is the difference between a Gem and a Skill?

A Gem was a standalone custom assistant you opened from the sidebar, and each chat lived inside exactly one Gem. A Skill is a reusable instruction set you invoke with a forward slash inside any chat. Gemini can apply a skill automatically when it detects a match, and you can stack multiple skills in one conversation, which Gems never supported.

Do Skills work with all the Gemini features my Gem used?

Not yet. As of October 2026, skills do not work with Canvas, Deep Research, Guided Learning, Create video, or Create music. Google says sharing, Drive attachments, and Notebook support are coming in the following weeks.

Can I use a skill I created in the Gemini app inside Google Workspace?

No. Skills do not sync between the Gemini app and Workspace apps. If you want to use a skill in both places, you must create it separately in each one.

Are Skills free, or do I need a paid subscription?

Skills require no paid subscription. Google’s help page says they are available in Gemini chat to individuals over 18 signed in to a personal Google Account.

Conclusion

Migrating from Gems to Skills is less a rewrite than a relocation: your instructions and knowledge files move from a standalone assistant into reusable blocks that work inside any chat. Audit your Gems before October 13, back up the ones that matter, recreate them as skills using Google’s manual flow, test invocation and stacking, and rebuild any Workspace Studio flows with an Ask a Gem step before the 2027 cutoffs. Do that, and the November 17 automatic migration becomes a non-event. As a next step, read our n8n agent skills tutorial to see how the same SKILL.md standard powers coding agents like Claude Code.

Frequently asked questions