What Are Gemini Skills?
Gemini Skills are reusable sets of custom instructions that you save once and then call up inside any Gemini chat, instead of typing the same long prompt over and over again. Think of a skill as a small, portable recipe for how you want Gemini to behave: the tone it should use, the steps it should follow, the format you want back, and the reference material it should keep in mind. Once you have saved a Gemini Skill, you can summon it by name in an ordinary conversation, and Gemini will apply those instructions to whatever you ask next.
Google announced Gemini Skills on 30 September 2026 as the replacement for Gems, the older custom-assistant feature that has been part of Gemini since August 2024. The change matters because Gems are not simply being renamed. They are being retired on a fixed schedule, and the way you work with saved instructions is changing with them. If you built a Gem for editing newsletters, planning lessons, drafting proposals, or reviewing contracts, that setup will not live on in its old form forever. It will be converted into a skill, and you need to understand what survives that conversion and what does not.
The core idea behind Gemini Skills is simple, and it is a genuine improvement for everyday users. A Gem was a separate assistant you had to open: you left your normal chat, entered the Gem, and worked inside that one window. A skill works the other way around. You stay in the chat you are already using, call the skill by name, and keep going. That small difference changes how useful saved instructions are, because it removes the friction of switching contexts every time you want a consistent result.
Gemini Skills are also stackable. Where one Gem meant one set of instructions per conversation, you can combine several Gemini Skills in a single prompt. You might pair a brand-voice skill with a proofreading skill, or a meeting-notes skill with a follow-up-email skill, and Gemini will apply them together. For freelancers, teachers, small-business owners, and anyone who repeats the same kind of work each week, that stacking ability is the feature that turns a nice convenience into a real time saver.
There is one more structural difference worth knowing from the start. Gemini Skills use an open, portable format built around a file called SKILL.md. Your instructions and reference files live in a folder that you can download, edit, and upload again, and the same format is used by other tools, including Anthropic’s Claude Code. That portability is new for Gemini users, and it is the reason this migration is worth doing deliberately rather than leaving everything to automatic conversion.
Contents
- What Are Gemini Skills?
- Gemini Skills at a Glance
- Gemini Skills vs Gems: What Actually Changes
- The Gemini Skills Timeline: Dates That Matter by Account Type
- What Automatic Migration Keeps, and Why You Must Still Review It
- What Gets Lost: The 100 MB Limit and the Files That Do Not Transfer
- How to Migrate Your Gems to Gemini Skills, Step by Step
- Rebuilding With SKILL.md, and Porting Skills From Claude Code
- What Gemini Skills Cannot Do Yet
- A Note for Workspace and Education Users
- Gemini Skills: Frequently Asked Questions
- The Verdict: Migrate This Week, Not in December

Gemini Skills at a Glance
If you only have two minutes, here is the whole story. Gemini Skills replace Gems. For personal Google accounts belonging to adults, Gems become read-only on 17 November 2026 and are removed entirely on 17 December 2026. Google will automatically convert your Gems into Gemini Skills, but the converted Gemini Skills arrive as inactive drafts that you must review and switch on yourself. Files attached to a Gem are capped at 100 MB per skill, with the largest files dropped first if you go over that limit, and several file types do not transfer at all. Workspace and education accounts follow a slower timetable, running into 2027. Skills are free in the Gemini app for users aged 18 and over with a personal Google account, and you do not need a paid Google AI plan to create one.
| Question | Short answer |
|---|---|
| What are Gemini Skills? | Reusable custom instructions you call inside any Gemini chat |
| What happens to Gems? | Read-only 17 November 2026, removed 17 December 2026 (personal accounts, 18+) |
| Do I have to do anything? | Review and enable your converted skills; back up files before 17 December |
| What does it cost? | Nothing extra in the Gemini app; no paid plan required for Skills in chat |
| Biggest catch? | 100 MB file cap per skill, and several file types do not transfer |
Gemini Skills vs Gems: What Actually Changes
To understand why Google is making this change, it helps to compare the two systems side by side. Gems were custom versions of Gemini. You created a Gem, gave it instructions and knowledge files, and then opened that Gem whenever you wanted that behaviour. It worked, and many people built genuinely useful Gems, but it had a structural weakness: every Gem was a separate destination, and you could only use one at a time.
Gemini Skills remove that weakness. A Gemini Skill is not a destination; it is an ingredient. You type a slash, or soon an at-sign, followed by the Gemini Skill’s name, directly in any chat, and Gemini applies it there. You can also let Gemini apply a relevant skill automatically when it recognises that the Gemini Skill fits what you are asking. Google says Gemini checks the skill’s name and description to decide whether it fits, then reads its instructions and supporting files as needed. In practice, that means your saved instructions follow you around instead of waiting in a separate room.
The comparison below sets out the practical differences that affect real work, not just the marketing language.
| Feature | Gems | Gemini Skills |
|---|---|---|
| Where you use it | Open the Gem in its own window | Inside any Gemini chat, by name |
| Combining instructions | One Gem per conversation | Stack several skills in one prompt |
| Automatic use | No, you had to open the Gem | Yes, Gemini can apply a matching skill itself |
| Files | Knowledge files attached to the Gem | Text files, PDFs, and images, up to 100 MB total per skill |
| Portability | Gemini-specific | Open SKILL.md format you can download and move |
| Works with | Includes tools such as Canvas and Deep Research | Not yet with Canvas, Deep Research, Create video, Create music, or Guided Learning |
| Sharing | Gems could be shared | Sharing is coming, says Google, but not available at launch |
| Sync between app and Workspace | Separate systems | Still no sync: a skill made in the app does not appear in Workspace |
That last row deserves emphasis, because it surprises people. Gemini Skills do not currently sync between the Gemini app and Google Workspace. If you use both environments, you must recreate the skill in each one separately. The same applies to the migration itself: a Gem converted in one environment does not automatically appear in the other. Plan for that duplication if you work across a personal account and a work account.
Another difference is the limit on how many Gemini Skills can be active. You can create an unlimited number of Gemini Skills, but only up to 100 can be active at the same time. For most people that ceiling will never matter, but if you are the kind of power user who built dozens of Gems, it is worth knowing that activation is a deliberate step, not something that happens for every skill you own.
Why Google Is Replacing Gems With Gemini Skills
Google has not framed this as a minor refresh, and the design of Gemini Skills shows why. Gems solved one problem, which was repeating yourself, but they created another, which was fragmentation: every custom setup lived in its own window, disconnected from your normal chats. Skills solve the repetition problem without the fragmentation, because they travel with you. They also fit the direction Gemini is heading, toward an assistant that assembles capabilities on demand rather than asking you to pick a separate tool for each job.
The open SKILL.md format points in the same direction. When your instructions live in a standard markdown file, they are no longer locked inside one product. You can keep a copy, edit it in any text editor, share the folder with a colleague, or move a workflow you built in another tool into Gemini. That openness is a genuine advantage for users, and it is also the reason the migration catches matter so much: an open format only helps if the files you care about actually make the journey.

The Gemini Skills Timeline: Dates That Matter by Account Type
The single most important thing to take from this article is the timetable, because it is not the same for everyone. Google is retiring Gems in stages, and the date that matters to you depends on the kind of account you sign in with. Mark the date that applies to you, and work backwards from it.
Personal Google Accounts (18 and Over)
For personal Google accounts belonging to users aged 18 and over, the schedule is the tightest. On 17 November 2026, Gems transition to Gemini Skills and become read-only. From that date you can still see your Gems, but you cannot use them, edit them, or create new ones. A month later, on 17 December 2026, Gems are removed from Gemini Apps entirely, and you will no longer be able to access them or their files. That one-month window between read-only and removal is your last chance to download anything that did not transfer.
If you are under 18 and signed in with a personal Google account, your Gems will transition at a later date that Google has not yet announced. The advice in this article still applies to you, but the deadline pressure does not, and you should watch for Google’s announcement rather than assuming the November dates cover your account.
Workspace Business, Enterprise, Non-Profit, and Education Accounts
Workspace accounts get considerably more time. For business, enterprise, and non-profit accounts, Gems will stop working no sooner than 1 March 2027. For education accounts, the date is no sooner than 1 June 2027. On 17 November 2026, Workspace Gems move into the Settings panel of the Gemini app, but users can continue to create, edit, and use them after that move. That distinction trips people up: 17 November means something different on a work account than it does on a personal account, so do not panic if you see the date mentioned without the account type attached.
There is also a delay worth knowing about for Workspace users. Skills inside Workspace apps and Workspace Studio were delayed until further notice in Google’s October update, even as the Gemini app rollout proceeds. If your team uses Gemini inside Workspace apps, check the current status before promising colleagues a migration date, because the app timeline and the Workspace-apps timeline are not the same.
The rollout itself began in stages. Skills started rolling out in the Gemini app on 13 October 2026, with completion expected by mid-November 2026, while the Workspace rollout began on 5 October 2026 with the same mid-November completion target. If you do not see Skills in your account yet, that may simply mean your account is still in the rollout queue, and it is worth checking again rather than assuming something is wrong.

What Automatic Migration Keeps, and Why You Must Still Review It
Google’s reassuring headline is that when Gems are removed, your Gems will automatically be recreated as Gemini Skills. That is true, and it means most casual Gem users do not need to rebuild everything by hand. The converted Gemini Skill keeps the Gem’s name, description, custom instructions, and uploaded knowledge files, within the limits described below. For a simple Gem with short instructions and a couple of PDFs, automatic migration may be all you ever need.
But there is a catch that changes the whole picture, and it is the reason this article exists. Converted Gems arrive as inactive drafts. You must review each one and enable it before it becomes functional. A converted Gemini Skill that you never switch on does nothing, no matter how perfectly its instructions transferred. If you have ten Gems, that means ten reviews. If you have fifty, it means fifty. Budget that time now, while your Gems still work, rather than discovering the backlog after 17 November.
Reviewing is not a formality, either. The converted Gemini Skill is a new object built from your old Gem, and the only way to know whether it behaves the way your Gem did is to test it. Ask it a question whose answer depends on an attached document. Give it a task in the format your Gem used to produce. Compare the output with what you used to get. A skill’s name alone will not tell you whether the material it needs actually made the journey, and a quick test now is far cheaper than a failed deliverable later.
Google’s own guidance points the same way. Its admin guidance on the transition recommends copying instructions and re-uploading files by hand so you can verify your prompts before the automatic migration. That is not the language of a migration you can ignore. Treat automatic conversion as a safety net, not as a finished job, and treat your own review as the real migration.
The Inactive Draft Trap in Gemini Skills Migration
The inactive-draft detail is easy to miss because it sounds like a minor administrative step, and it is the detail most likely to cause real damage. Imagine a freelancer whose client-onboarding Gem stops working on 17 November. The Gem was converted, the skill exists, and everything looks fine in the list, but nobody switched it on, so the first time it is needed, it simply is not there. The fix takes seconds, but only if you know to look for it. Go through your converted Gemini Skills one by one, enable the ones you still use, and delete or archive the ones you do not, so your active list stays clean and under the 100-active limit.
What Gets Lost: The 100 MB Limit and the Files That Do Not Transfer
This is the section to read with your own Gems open beside you. Gemini Skills have a hard limit: a skill can hold up to 100 MB of files in total. If your Gem’s files add up to more than that when Google converts it, Google automatically removes the largest files first until the skill fits under the cap. Nothing warns you in advance about which files were dropped, beyond the fact that the rule exists, so a Gem built around one large reference document could lose exactly the document it depends on most.
Separately, several file types are not supported in Gemini Skills at all, and those files will not be included when your Gems transition. According to Google’s help page, the unsupported types are GitHub files, audio files, video files, legacy Microsoft Office formats such as .doc, .xls, and .ppt, and archives and compressed formats such as .zip, .tar, .7z, .rar, .gz, and .tgz. If your workflow depends on any of those, automatic migration will silently leave them behind.
There is one more wrinkle that catches even careful users. The Skills upload guide also lists .docx and .xlsx as unsupported. Do not assume a newer Office file is safe simply because the migration list mentions older formats. If a Gem relies on a Word document or a spreadsheet, convert it now: save a PDF version for reference material, or a CSV version for tabular data, and attach that instead. A PDF or a plain-text file transfers; a .docx may not, and finding out after 17 December is too late.
The practical response is straightforward, and it is the same advice Google gives: for personal accounts, download your files from your Gems before 17 December 2026, because after that date your Gems and their files will no longer be available in Gemini Apps. Download the originals to a folder you control, not just to another Google service that might itself change. Once you have the originals, you can decide what to re-upload, what to convert, and what to fold directly into the skill’s instructions.
- Over 100 MB: trim the skill down before migration, keeping the smallest files that carry the most value, or split one big Gem into two focused Gemini Skills.
- Audio or video files: transcribe the essential content into text, or summarise it in the SKILL.md instructions, because the media file itself will not transfer.
- GitHub files: save the content as plain text or PDF, since GitHub-sourced files are excluded from the transfer.
- Old Office files and archives: unpack archives and convert documents to PDF, plain text, or CSV before re-uploading.
- Google Labs pre-made Gems: these will not migrate at all, so rebuild anything you rely on from a Labs Gem as your own skill.
One category deserves its own warning: pre-made Gems created by Google Labs will not migrate into Gemini Skills. If your daily routine leans on a Labs Gem, automatic migration will not save it. Recreate it manually as a skill while you can still open the original and copy its instructions.
How to Migrate Your Gems to Gemini Skills, Step by Step
The safest way to move from Gems to Gemini Skills is to do it yourself, before the automatic migration, starting with the Gem you would miss most. Working through one Gem at a time keeps the job manageable, and it means you are testing the new skill while the old Gem still works as a reference. Here is a sequence that works for personal accounts, and the same logic applies to Workspace accounts with their later deadlines.
Step 1: Inventory Your Gems
Open your Gem manager and list every Gem you have. For each one, note what it does, how often you actually use it, and which files it carries. Be honest about the ones you never use: migrating a Gem you abandoned a year ago just adds clutter to your Gemini Skills list. Delete or ignore the dead ones, and focus your energy on the handful that carry real work. While you are there, check the total size of each Gem’s files against the 100 MB cap, and flag any Gem that depends on audio, video, GitHub files, old Office formats, or archives.
Step 2: Back Up Instructions and Files
For each Gem you intend to keep, open it and copy its instructions into a document you control. Then download its knowledge files, one by one, to a folder on your own device. This backup is the single most valuable step in the whole migration, because it protects you against every failure mode at once: a dropped large file, an unsupported format, a Labs Gem that never migrates, and the December removal itself. Keep the backup even after the skill is working, because a local copy is the only version no platform change can take away.
Step 3: Create the Skill Manually
In the Gemini app, open the Customize menu and select Skills, then choose Create and Create manually. Copy the Gem’s name, description, and instructions into the matching fields. Keep the name short and descriptive, using lowercase letters with hyphens between words, because that naming rule is part of the SKILL.md format and it makes the skill easy to call by name in a chat. A clear name also helps Gemini decide automatically when the Gemini Skill fits a question, so name it for what it does, not for what you happened to call the Gem.
Step 4: Add Files the Right Way
Adding files to a skill works a little differently from adding them to a Gem. Google’s walkthrough describes downloading the skill, combining its SKILL.md file with your reference files in a folder matching the skill’s name, and uploading the whole folder through the Replace skill option. If that sounds fiddly, it is, but it is also the mechanism that makes Gemini Skills portable: the folder is the skill, and you can keep a copy of it. Convert unsupported files before this step, as described above, and keep the total under 100 MB. If a Gemini Skill still exceeds the cap, split it: two focused Gemini Skills beat one bloated skill that silently lost its largest file.
Step 5: Test Before You Rely on It
Once the Gemini Skill is created, test it against the old Gem while both are still available. Ask the same question in both, and compare the answers. Give the Gemini Skill a task that depends on an attached file, and check that the answer actually uses that file rather than guessing. Try a task in the exact format you need for work, and confirm the format survived. If anything is off, fix the instructions now, while you can still read the original Gem for comparison. When the skill matches or beats the Gem, enable it, and only then stop using the Gem.

Rebuilding With SKILL.md, and Porting Skills From Claude Code
The SKILL.md format is the quiet revolution inside Gemini Skills, and it is worth understanding even if you never write a line of markdown by hand. A skill, at its simplest, is a folder containing a SKILL.md file that holds the instructions, plus any reference files the skill needs. Because the format is open and standardised, you can download a Gemini Skill, edit its instructions in any text editor, and upload it again. You can also build a skill entirely by hand: write the instructions, save them as SKILL.md, place the reference files beside it in a folder named for the skill, and upload the folder or a zip archive with SKILL.md in its main folder.
That standardisation has an immediate practical payoff that was in the news on 1 November 2026: because Claude Code uses the same SKILL.md format and the same hyphenated naming rule, skills you built for Claude Code can be ported into Gemini directly. In a hands-on test published by XDA Developers on 1 November, a writer moved Claude Code skills into Gemini’s new Skills system without rewriting them. If you already have a library of Claude skills stored in your local Claude profile directory, try uploading one: open Customize, select Skills, and upload the single SKILL.md file, the full skill folder, or the zip archive. Check the result the same way you would check any migrated skill, because a skill written for one tool may assume capabilities the other does not have, but the transfer itself is designed to work.
Writing a good SKILL.md is a Gemini Skill in itself, and the habits that make a good Gem make a good skill. State the job in the first line, so Gemini and any automatic matching can recognise when the skill applies. Describe the steps in order, not as a vague aspiration. Specify the output format with an example, because a format instruction without an example is often ignored. List the constraints that matter, such as tone, length, or what never to invent, and keep the instructions focused: one skill should do one job well, and stacking handles the rest.
Stacking Gemini Skills in Everyday Work
Stacking is where Gemini Skills start to feel different from Gems in daily use. Instead of opening a separate assistant for each job, you call the Gemini Skills you need into the chat you are already in. A freelance writer might stack a brand-voice skill, a research-summary skill, and a proofreading skill on a single draft. A teacher might stack a lesson-plan skill with a quiz-generation skill. A small-business owner might stack a customer-reply skill with a pricing-check skill. Type the slash, or the at-sign once your account has the updated shortcut, followed by each skill’s name, and Gemini applies them together.
Stacking works best when each Gemini Skill is narrow. A Gemini Skill that tries to do everything will fight with the other skills in the same prompt, and the output will drift toward the loudest instruction. Keep each Gemini Skill to one job, give it a name that says what that job is, and let combinations do the complex work. If a combination produces odd results, remove one Gemini Skill at a time until you find the conflict, then tighten the overlapping instruction in the skill that caused it.
What Gemini Skills Cannot Do Yet
Honesty about the gaps matters, because a migration that promises everything will disappoint. At launch, Gemini Skills do not work with Deep Research, Guided Learning, Canvas, Create video, or Create music. If a Gem you rely on depends on any of those tools, its converted Gemini Skill will not reproduce that behaviour, and Google has given no date for when those capabilities arrive. The right move for such a Gem is to keep using it until your account’s deadline, while building a skill-based alternative for the parts that do transfer, and to check back after the migration for the missing tools.
Sharing is the other gap. Google says Gemini Skills will gain the ability to be shared with others, along with the ability to add files from Google Drive and notebooks from Gemini Notebook, in the coming weeks. Until then, a Gemini Skill is a personal tool: you can download and hand someone the folder, but there is no built-in sharing the way Gems had. Teams that shared Gems should plan around that gap, for example by keeping a shared folder of SKILL.md files that each member uploads themselves.
There are also the limits already mentioned: 100 active Gemini Skills at a time, 100 MB of files per skill, no sync between the Gemini app and Workspace, and no support for several file types. None of these is a reason to avoid Gemini Skills, but each one is a reason to migrate deliberately, with a backup and a test, rather than assuming the automatic conversion has handled everything.
A Note for Workspace and Education Users
If you use Gemini through work or school, your timetable is longer, but your planning needs to be more careful, because teams share setups. Start by listing the Gems your team actually relies on, and check whether any Workspace Studio flow uses an Ask a Gem step, because that step will stop working when Gems stop working for your account type. Back up team instructions and files the same way a personal user would, and decide who owns each converted Gemini Skill, since converted skills arrive as inactive drafts in the creator’s account.
Because Gemini Skills do not sync between the Gemini app and Workspace, anything your team needs in both places has to be created twice, and that duplication should be assigned, not assumed. Keep a shared document listing each Gemini Skill, where it lives, who owns it, and when it was last tested. That document is unglamorous, and it is the difference between a smooth migration and a week of colleagues discovering, one by one, that a setup they depended on never got switched on.

Gemini Skills: Frequently Asked Questions
Do Gemini Skills cost anything?
No. Skills in the Gemini app are available to individuals over 18 signed in with a personal Google account, and they do not require a paid Google AI subscription. Gemini Skills began inside Gemini Spark, Google’s agent for paying subscribers, but in regular Gemini chat they are free. If you already pay for a Google AI plan, Gemini Skills work within that plan too, but payment is not the gate.
Will my Gems convert automatically?
Yes, with the caveats in this article. Google will automatically recreate your Gems as skills when Gems are removed, but the results arrive as inactive drafts that you must review and enable. Files over the 100 MB cap lose their largest files first, unsupported file types do not transfer, and Google Labs pre-made Gems do not migrate at all. Automatic conversion is a safety net, not a substitute for checking.
What happens if I do nothing before 17 November?
For a personal account, your Gems become read-only on 17 November 2026: visible, but unusable and uneditable, and you cannot create new ones. On 17 December 2026 they are removed, along with any files that did not transfer. Doing nothing does not delete your instructions immediately, because automatic conversion creates draft skills, but it does leave you with inactive drafts and possibly missing files, discovered at the worst moment.
Which files should I convert before migrating?
Convert Word documents and spreadsheets to PDF or CSV, unpack archives and upload the contents as plain files, transcribe essential audio or video content into text, and save GitHub-sourced material as plain text or PDF. Then check the total size of each skill’s files against the 100 MB limit, and split any skill that exceeds it.
Do Gemini Skills sync between the app and Workspace?
No. Skills do not sync between the Gemini app and Google Workspace, so a skill created in one environment will not appear in the other. Recreate the skill in each environment where you need it, and keep a note of where each copy lives.
The Verdict: Migrate This Week, Not in December
Gemini Skills are a genuine upgrade on Gems for most people: instructions that travel with you instead of living in a separate window, skills that stack, and an open format you can keep, edit, and move. The migration itself is not hard, but it is not fully automatic either, and the traps are all in the details: inactive drafts, the 100 MB cap, unsupported file types, Labs Gems that never migrate, and the missing tools at launch. Every one of those traps is avoidable if you act while your Gems still work.
Do it this week, in this order. List the Gems you actually use. Back up their instructions and files to a folder you control. Rebuild the most important one as a Gemini Skill, test it against the original, and enable it. Then work through the rest, convert the files that will not transfer, and delete the Gems you no longer need. By the time 17 November arrives, the deadline will be a non-event for you, and your saved instructions will be in a format that is more portable, more flexible, and more useful than the Gems they replace. That is the whole point of Gemini Skills: save the instructions once, and use them everywhere, without ever retyping them again.
For the official word on dates, file rules, and account types, see Google’s help page on the transition from Gems to skills and the XDA Developers hands-on test of moving Claude Code skills into Gemini. For more Gemini coverage on this site, see our guides to editing files inside Gemini chat, the free Mac assistant that runs AI models locally, and the best AI coding assistants of 2026.
