Google is about to change the way you customize its AI. On November 17, 2026, the personal Gems you built inside Gemini Skills' predecessor — the custom-assistant feature Google launched back in August 2024 — become read-only, and a month later they are permanently deleted. In their place comes Gemini Skills: a system that lets you save your most-used instructions once and run them inside any chat, over and over again, without ever leaving the conversation you are in.
If you use Gemini regularly, this guide is for you. Below you will find everything verified so far: what Gemini Skills are and how they differ from Gems, the exact timeline of what happens to your Gems, a step-by-step walkthrough for creating your first skill, how to import Claude Code skills directly thanks to the shared SKILL.md format, ten practical skill ideas to start with, and the honest list of things Skills cannot do yet. Every date, limit and step comes from Google's own announcements and hands-on testing published in early November 2026 — nothing here is invented.
What Are Gemini Skills?
Gemini Skills are reusable instruction sets that live inside the Gemini app. Instead of typing the same setup prompt every time — "You are my patient French tutor, correct my mistakes gently, always end with a practice question" — you save those instructions once as a skill, and then invoke that skill whenever you need it. The skill shapes how Gemini responds, while you stay in the normal chat flow.
Google's own framing is simple. Deven Tokuno, Senior Product Manager for the Gemini App, wrote in Google's September 30 announcement that Skills let users "save your most-used instructions once and run them endlessly" inside any existing chat, allowing people to "skip the repetitive prompting and jump straight to the results." That single sentence is the whole philosophy: write the instructions once, reuse them forever.
Skills are not a brand-new experiment. They first appeared inside Gemini Spark, the version of Gemini aimed at paid Google AI subscribers. On September 30, 2026, Google announced that Skills were rolling out for free in standard Gemini chat — and that they would replace Gems entirely. Since then, hands-on testers (notably XDA Developers, whose test was published November 1, 2026) have been poking at the edges of the system, and this guide is built on what they found.
Gems vs Skills: What Is Actually Different
To understand why Google is making this switch, you have to understand what Gems were. Google introduced Gems in August 2024 as custom versions of Gemini with saved instructions and attached reference files — a coding tutor Gem, a writing coach Gem, a trip-planner Gem. The idea was sound, but the execution had a friction problem: every Gem lived in its own separate chat window. Want your coding coach's advice while you are mid-conversation about a project? You had to leave your active conversation, open the Gem, and start over.
Skills remove that friction. A skill runs inside whatever chat you are already in — you call it, or Gemini calls it for you, and the conversation continues. That is the headline upgrade, and it is why Google is willing to retire a two-year-old feature to make room for it.
| Feature | Gems (retiring) | Skills (new) |
|---|
| Where it runs | Its own separate chat window | Inside any chat you are already in |
| Availability | August 2024 – December 2026 | September 30, 2026 onward (free in standard Gemini) |
| How many you can make | Limited set of custom Gems | Unlimited — up to 100 active at once |
| Triggering | Open the Gem manually | Manual (@ mention) or automatic by Gemini |
| Stacking | One Gem at a time | Multiple skills can stack in one prompt |
| Sharing | Available in Gems | Not yet — "coming in the coming weeks" per Google |
| Attached Drive files | Supported | Not yet — also "coming in the coming weeks" |
The main trade-off is visible in the last two rows: Skills are more powerful in the chat, but at launch they are missing a few conveniences Gems had, which Google says are on the way. More on that later.
The Timeline: Key Dates You Must Not Miss
This is the part that matters if you already have Gems. Google's schedule is strict, and the dates differ depending on your account type:
| Date | Who it affects | What happens |
|---|
| November 17, 2026 | Personal Google accounts (18+) | Gems become read-only; existing Gems auto-convert to Skills |
| December 17, 2026 | Personal Google accounts (18+) | Gems are permanently deleted from Gemini Apps |
| November 17, 2026 | Workspace business, enterprise, nonprofit | Gems move to the Settings panel; remain available until March 2027 |
| November 17, 2026 | Workspace education accounts | Keep Gem access until June 2027 |
The one-month window between November 17 and December 17 is your safety net. That is when you should manually download and re-upload any attachments that did not migrate automatically — oversized files or unsupported formats (details below) will not carry over on their own, and after December 17 they are gone for good on personal accounts.
Mark November 17 on your calendar twice: once as the day Gems freeze, and once as a reminder to check that your important Gems survived the automatic conversion.
What Google Will Migrate Automatically — and What It Will Not
Google says it will automatically convert your existing Gems into Skills — you do not have to rebuild everything by hand. But "automatic" comes with fine print, and understanding it now saves you from discovering a broken skill later.
The 100 MB rule: each skill has a 100 MB total file limit. If a Gem's attached files add up to more than 100 MB, Google does not ask you what to keep — it drops the largest files first until the package fits under the cap. If your coding-tutor Gem had a 90 MB reference PDF plus a few small files, that PDF is the first thing to go.
What transfers over: text files, PDFs and images move across to the new skill without trouble. What does not transfer: GitHub files, audio and video files, legacy Microsoft Office documents (.doc, .xls, .ppt), and compressed archives (.zip, .tar, .7z, .rar, .gz, .tgz). Anything in those formats stays behind.
One more exception: pre-made Gems created by Google Labs will not migrate at all. Only your own custom Gems make the trip. If you have been relying on a Google-made premade Gem, start rebuilding it as a skill now rather than waiting for November 17.
The practical takeaway: audit your Gems this week. Open each one, note which files it has attached, and re-save anything in an unsupported format or over the size limit somewhere safe (your Drive, your computer) so you can re-attach it after the migration.
How to Create Your First Skill: Step by Step
Creating a skill is deliberately simple — Google wants this to feel easier than building a Gem ever did. Here is the full process, based on the released flow:
Step 1 — Open Gemini and find the Customize menu. Go to gemini.google.com (or open the Gemini app) and sign in with a Google account that is 18 or older. Look for the Customize menu — this is where Skills now live, taking the slot Gems used to occupy.
Step 2 — Select Skills, then create a new one. Inside the Customize menu, choose Skills. You will see your existing skills (converted from Gems, if any) and an option to create a new skill. Select it.
Step 3 — Give it a name. Pick a short, lowercase, hyphenated name — for example study-buddy, email-polisher or workout-coach. The lowercase-with-hyphens rule matters: it is the same naming convention Claude Code skills use, and it keeps the system consistent.
Step 4 — Write the description. This is the most important field. Describe what the skill does and when Gemini should use it in one or two plain sentences. Example: "Helps you study for exams by quizzing you with flashcards and explaining concepts simply." Gemini reads this description to decide when to activate the skill automatically — treat it as the skill's job advert.
Step 5 — Write the instructions. This is the skill's brain: the detailed guidance Gemini follows when the skill is active. Write it the way you would brief a smart assistant. You can either paste the name, description and instructions into the manual text boxes, or upload files directly — Gemini accepts a single SKILL.md file, a full skill folder, or a zip archive with a SKILL.md in its main folder.
Step 6 — Save, then test it in a fresh chat. Start a new chat, trigger the skill (see the triggering section below), and give it a realistic task. If the responses are not quite right, you do not need to rebuild anything: hit the "Edit with Gemini" button and describe the adjustment in plain words — "make the quizzes harder," "use shorter answers" — and Gemini updates the skill for you.
That last point is quietly the biggest usability win in the whole system. Small tweaks no longer require re-uploading files. You iterate by talking, the way you already talk to Gemini.
Writing a Great Skill: The Name, Description and Instructions Formula
A skill has three ingredients, and each one has a job:
The name is the skill's handle. Keep it short, lowercase, and hyphenated (study-buddy, not "My Amazing Study Buddy!!!"). This is not just a style rule — the SKILL.md format shared with Claude Code skills expects it, and a clean name makes the skill easy to reference.
The description is the skill's trigger. One or two sentences, plain language, describing what it does and when it applies. Bad description: "A skill for stuff." Good description: "Reviews your code for bugs and suggests simpler alternatives, with explanations a beginner can follow." Gemini matches your prompts against this text when deciding whether to activate the skill on its own.
The instructions are the skill's personality and rulebook. This is where you put the detail: the tone to use, the steps to follow, what to avoid, the format of the output. Think of it as the difference between a job title (the description) and the full job description with procedures (the instructions). A good pattern is: role, rules, output format, example. For instance: "You are a patient French tutor for beginners. Correct every mistake I make, explain each correction in one sentence, and always end your reply with one practice question. Keep answers under 150 words."
The golden rule: specific beats clever. "Help me write better" is a wish. "Rewrite my paragraph to be more direct, cut filler words, keep my meaning, and show me the three biggest changes in a list" is a skill.
The Description Field Does the Heavy Lifting
Here is something hands-on testers discovered that Google's own documentation does not spell out clearly: when Gemini decides whether to fire a skill automatically, the description field does most of the work.
The XDA Developers tester put it plainly: "From what I can tell, and I'm only going off a handful of chats here, the description field does most of that work. For example, my wireframe skill's description mentions sketching a UI layout, and asking for a UI layout for a habit tracker was all it took." No manual trigger, no special syntax — the prompt matched the description, and Gemini activated the skill on its own, even showing the skill's name in its thinking process.
What this means for you in practice: write the description for matching, not for humans. Include the verbs and nouns you would naturally type when you want the skill. A cooking skill's description should contain words like "recipe," "ingredients," "cook," and "meal" — because that is what you will type. A skill whose description says "culinary optimization assistant" will wait politely while you ask for "a quick dinner recipe" and never fire.
Pro tip: after creating a skill, test the automatic trigger with three or four different natural phrasings of the same request. If the skill fires for all of them, your description is doing its job. If it only fires when you mention the skill by name, rewrite the description with more everyday language.
How to Import a Claude Code Skill Into Gemini
This is the feature that surprised everyone, and it is arguably the most useful part of the whole launch. Anthropic's Claude Code and Google's Gemini Skills use the same underlying format for reusable instructions: a markdown file called SKILL.md. Because the formats match, you can take a skill built for Claude and drop it into Gemini without rewriting it from scratch.
Here is how it works, step by step:
Step 1 — Find your Claude skills. Claude Code stores custom skills in the .claude directory of your user profile on your computer. Each skill is a folder containing a SKILL.md file (plus any supporting files). Because Claude skills already use the exact same SKILL.md format and the same hyphenated naming rule, they are structurally ready for Gemini as-is.
Step 2 — Open Gemini's Skills uploader. Go to the Customize menu, select Skills, and start a new skill. Instead of typing into the text boxes, choose the upload option.
Step 3 — Upload in any of three forms. Gemini accepts a single SKILL.md file, a full skill folder, or a zip archive with the SKILL.md in its main folder. Pick whichever is most convenient — the folder or zip keeps supporting files together.
Step 4 — Check the name. Make sure the skill name uses lowercase letters with hyphens between words. Claude skills already follow this convention, so most will pass unchanged — but it is worth a glance.
Step 5 — Test it in Gemini's world, not Claude's. This is the critical step, and it is where testers found the real-world catch (next section).
Why does this matter? Because it means your prompt workflows are no longer locked to one AI platform. The hours you spent crafting the perfect code-review assistant or research helper for Claude Code can now travel with you to Gemini. In an industry where every company wants you locked into its ecosystem, a shared open format is genuinely good news for users.
Rewriting Claude Skills for Chat: The Catch You Must Know
Direct import works structurally — but there is a real-world catch, and the XDA tester's experience is the honest guide here. Skills built for Claude Code to manipulate local PC files did not translate to browser-based study and research chats. A skill that says "read the file at /home/user/project/main.py and patch it" makes no sense to Gemini running in your browser, which has no access to your PC's files.
There is a second, related limit: Gemini does not support scripts that require internet access inside skills. So any Claude skill that depends on fetching live data through a script will not work as imported.
Here is the fix the tester used, and it is the workflow you should copy: have Claude copy the local skills into a new folder and rewrite the instructions for chat-based work — replacing file paths and shell commands with "ask the user to paste the content" style instructions. Then upload the rewritten version to Gemini.
The good news: once the rewritten skill is in Gemini, future tweaks are painless. The "Edit with Gemini" button lets you describe adjustments in plain words — no re-uploading, no re-editing the markdown by hand. Import once, refine by conversation.
The honest summary: Claude-to-Gemini skill migration is a genuine, working feature — but treat it as a head start, not a finished job. Budget ten minutes to adapt any skill that touches the file system or the network, and you will end up with something that actually works in Gemini's chat environment.
How Skills Trigger in Chat: Manual, Automatic, or Both
There are two ways a skill fires, and understanding both is the difference between a skill that sits unused and one that feels like magic.
Manual triggering: you call the skill yourself in the chat. Google's documentation references typing a forward slash (/) to pull up a skill — but according to both XDA Developers and independent consultant Lukas Huettis, the trigger shortcut is transitioning to the @ symbol. Type @, pick your skill from the list, and your next prompt runs through that skill's instructions. Use this when you want to be certain which skill is active.
Automatic triggering: you just type naturally, and Gemini selects the right skill on its own — it can even stack multiple skills when a prompt matches more than one. When this happens, Gemini displays the skill's name in its thinking process, so you can see exactly which skill it chose and why. As the tester's wireframe example showed, a well-written description is often all it takes: ask for "a UI layout for a habit tracker" and the skill whose description mentions "sketching a UI layout" activates itself.
Which should you rely on? Both. Use manual triggering while a skill is new and you are still tuning its description; switch to automatic once you have tested that Gemini picks it up reliably from natural phrasing. And remember: because skills stack, you can build small, focused skills (a "concise-answers" skill, a "beginner-explanations" skill) and let Gemini combine them — composable skills beat one giant mega-skill.
10 Practical Skills to Build First
Theory is nice, but skills earn their place by saving you time every day. Here are ten ideas that fit the system's strengths — each one is a concrete starting point you can adapt:
1. The Email Polisher. "Rewrite my draft emails to be clear and professional. Keep my meaning, fix grammar, cut fluff, and never change the tone I asked for." Paste a rough draft, get a sendable email.
2. The Study Buddy. "Quiz me on the topic I name, one question at a time. If I get it wrong, explain the concept simply and ask a follow-up. Track my score." Perfect for exam prep — the description should include words like "quiz," "study," "exam," and "flashcards" so it triggers automatically.
3. The Code Reviewer. "Review code I paste for bugs and bad practices. Suggest simpler alternatives, explain each issue for a beginner, and rate the code's readability." (Paste the code — remember Gemini skills cannot read your local files.)
4. The Meeting Distiller. "Turn my pasted meeting notes into: decisions made, action items with owners, and open questions. Keep it under 200 words."
5. The Workout Planner. "Build a weekly workout plan from the equipment I list and the days I can train. Include sets, reps and rest times. Ask about injuries first."
6. The Recipe Improviser. "Suggest a dinner recipe from the ingredients I list. Include prep time, steps, and one substitution if I am missing something." Include "recipe," "ingredients," "cook," and "dinner" in the description for reliable auto-triggering.
7. The Writing Coach. "Critique my writing for clarity and flow. Show the three biggest improvements as before/after examples. Be encouraging but honest."
8. The Travel Planner. "Build a day-by-day itinerary for the city and dates I give. Include one budget option and one splurge option per day, plus local transport tips."
9. The Language Tutor. "Teach me the language I name at beginner level. Correct every mistake, explain each correction in one sentence, and end every reply with one practice question."
10. The Budget Explainer. "Explain any finance term I ask about in plain language with a real-life example. No jargon without a definition. This is educational only, not financial advice."
Notice the pattern: each skill does one job, names its inputs, and specifies its output format. Start with two or three that match your daily routine, and add more as the habit forms.
What Skills Cannot Do Yet: The Honest Limitations
Skills are a real upgrade, but they are not a complete replacement for everything Gems could do — at least not yet. According to XDA Developers and The AI Career Lab, Skills do not currently work with Deep Research, Guided Learning, Canvas, Create video, or Create music. If your workflow depends on a Gem inside one of those tools, Skills cannot take over that job today.
Two more gaps come straight from Google's Gemini Apps Help page, which says that "in the coming weeks, skills will have the features you loved in Gems, including the ability to share them with others and add files from Google Drive and notebooks from Gemini Notebook." In other words: no skill sharing yet, and no Google Drive or NotebookLM notebook attachments yet.
None of this is a reason to avoid Skills — the core feature (reusable instructions inside any chat) works now, for free. But it is a reason to keep your expectations calibrated: if you are a heavy Canvas or Deep Research user, or you share Gems with a team, plan your migration around what is missing, not just what is new. Check Google's help page again in a few weeks; the "coming weeks" features are the ones most likely to land before the December 17 deletion deadline.
Managing Your Skills: The 100-Active Limit
You can create an unlimited number of skills — Google puts no cap on your library. But only up to 100 skills can remain active at the same time. In practice, this limit will never bother a normal user: 100 active skills is far more than anyone can meaningfully maintain, and the testers' advice is the same as any productivity system's — a smaller set of sharp skills beats a graveyard of vague ones.
A practical maintenance routine: once a month, open your Skills list and retire anything you have not triggered in weeks. Merge overlapping skills (your "email-fixer" and "email-polisher" are one skill, not two). And keep skill names short and distinct, because when you type @ and see the list, you want to recognize each skill in under a second.
Migrating Your Gems Before November 17: A Checklist
If you have Gems today, do not wait for the deadline. Work through this checklist once, and the transition will be boring — which is exactly what you want:
1. List every Gem you actually use. Open the Gems panel and write down the ones that matter. Be honest — the trip-planner Gem you opened twice in 2025 does not need migrating.
2. Check each Gem's attachments. For every attached file, ask: is it over 100 MB total with the others? Is it a GitHub file, audio, video, a legacy Office document (.doc/.xls/.ppt), or an archive (.zip/.tar/.7z/.rar/.gz/.tgz)? If yes to any, save a copy somewhere safe now — it will not migrate automatically.
3. Let Google auto-convert, then verify. After November 17, your Gems become Skills automatically. Open each converted skill and check that the instructions and surviving attachments look right.
4. Re-upload what did not survive. Use the December 17 safety window to manually re-add oversized or unsupported attachments in supported formats (convert that .doc to .docx or PDF first).
5. Rebuild Google Labs premade Gems by hand. These do not migrate — if you rely on one, recreate it as a skill now.
6. Test the automatic trigger. For each important skill, type three natural prompts and confirm Gemini picks up the right skill. Rewrite descriptions that do not fire.
7. Delete the dead weight. Skills are unlimited, but your attention is not. Retire anything you migrated "just in case" and never touched.
Common Mistakes to Avoid
Most bad skills fail in the same handful of ways. Avoid these and you are already ahead of most users:
Mistake 1 — The vague description. "Helps with writing" tells Gemini nothing. "Rewrites rough email drafts into clear professional emails" tells it exactly when to fire. The description is your trigger; write it for matching.
Mistake 2 — One mega-skill for everything. A single skill that is simultaneously a tutor, a coder, a chef and a therapist will fire at the wrong times and confuse every response. Build small, focused skills and let Gemini stack them.
Mistake 3 — Instructions with no output format. If you do not say how the answer should look, you will get a different shape every time. Always specify: list, table, word limit, tone.
Mistake 4 — Importing Claude skills without adapting them. A skill that manipulates local files or calls the internet will silently fail in Gemini's browser chat. Rewrite for chat first, then import.
Mistake 5 — Never testing the automatic trigger. A skill that only works when you remember to type @ is a skill you will forget to use. Test with natural phrasing until it fires on its own.
Mistake 6 — Attaching files Gemini cannot read. Audio, video, legacy .doc/.xls/.ppt and archives will not migrate from Gems — convert or re-save them in supported formats (PDF, modern Office formats, plain text, images) before the deadline.
Mistake 7 — Waiting until December. The read-only date is November 17, not December 17. December 17 is when Gems are deleted — by then you can only rescue attachments, not edit anything. Do the audit now.
Gemini Skills vs the Competition: A Quick Reality Check
Gemini is not the only AI assistant with reusable instructions — ChatGPT has custom instructions and GPTs, and Claude has its own skills system. The concepts rhyme, but Gemini's current pitch is distinct in two ways worth noting.
First, the cross-platform SKILL.md format. The fact that a Claude Code skill folder can be uploaded into Gemini unchanged is unusual in an industry built on lock-in. Your carefully built prompt workflows become portable assets instead of sunk costs in one app. If you split your time between Claude and Gemini, this alone is a reason to standardize on the SKILL.md format for anything you build.
Second, in-chat activation with stacking. Gems forced you into a separate window; Skills meet you where you are and can combine. The practical effect is that skills behave more like apps you summon than assistants you visit — closer to how you actually work.
The honest counterpoint: ChatGPT's GPTs have had sharing and a store for a long time, and Gemini Skills are still waiting on sharing ("coming in the coming weeks"). If collaboration and publishing are your priority today, the competition is ahead. If personal, in-chat reuse is your priority, Skills are already competitive — and free.
Frequently Asked Questions
Do I need a paid Google AI plan to use Skills?
No. Skills launched inside Gemini Spark for paid subscribers, but since the September 30, 2026 announcement they are rolling out for free in standard Gemini chat.
What exactly happens to my Gems on November 17?
For personal accounts (18+), Gems become read-only and are automatically converted into Skills. On December 17 they are permanently deleted. Workspace business, enterprise and nonprofit accounts keep Gems in the Settings panel until March 2027; education accounts until June 2027.
Will all my Gem attachments migrate?
Not all of them. Text files, PDFs and images transfer. GitHub files, audio, video, legacy Office documents (.doc/.xls/.ppt) and archives (.zip/.tar/.7z/.rar/.gz/.tgz) do not. Each skill also has a 100 MB file limit — the largest files are dropped first if you exceed it.
How do I trigger a skill?
Type @ and pick the skill, or just type naturally and let Gemini activate it automatically — it shows the skill's name in its thinking process when it does. (Google's docs still mention /, but testers report the shortcut is moving to @.)
Can I really import my Claude Code skills?
Yes. Both use the SKILL.md format. Upload a single SKILL.md file, a skill folder, or a zip with SKILL.md in its main folder. Just remember to rewrite any file-system or internet-dependent instructions for chat first, since those do not work in Gemini's browser environment.
How many skills can I have?
Unlimited — but only 100 can be active at the same time. That is more than enough for any real workflow.
Can I share my skills with others?
Not yet. Google says sharing is coming "in the coming weeks," along with attaching files from Google Drive and notebooks from Gemini Notebook.
Do Skills work with Deep Research, Canvas or video generation?
Not currently. Testers confirm Skills do not work with Deep Research, Guided Learning, Canvas, Create video or Create music at launch.
What if a skill's responses are slightly off?
Use the "Edit with Gemini" button and describe the change in plain words — no re-uploading needed.
Should I still build new Gems today?
No — build Skills instead. Gems become read-only on November 17 and are deleted a month later. Anything new should be a skill from day one.
Sources
Key facts in this guide come from the following verified sources, retrieved November 2, 2026:
Google's September 30, 2026 Skills announcement, via Senior Product Manager Deven Tokuno (quoted through reporting); XDA Developers' hands-on test of Gemini Skills, published November 1, 2026 (SKILL.md migration, @ trigger transition, automatic activation, missing tool support); the Gemini Apps Help page (sharing and Drive/Notebook attachments "coming in the coming weeks"); independent consultant Lukas Huettis (trigger shortcut transition); The AI Career Lab (missing tool support); and the Blaze Trends Tech & Science Desk summary of the migration timeline, file limits and account-type dates — Gemini Replaces Gems With Skills on Nov. 17, Supports Claude SKILL.md Files.
Related reading on AI Tech Hub: our step-by-step guide to using Gemini's new file editing to create and edit PDFs, Docs, Slides and Sheets inside the chat, and the beginner's guide to creating AI images for free in 2026. You can open Gemini itself at gemini.google.com.
Conclusion: Write Once, Use Forever
The Gems-to-Skills transition is one of those rare platform changes that is genuinely in the user's favor: free access, in-chat activation, stackable skills, and a shared SKILL.md format that lets your work travel between Claude and Gemini. The price is a migration you have to do once — audit your Gems, rescue the attachments that will not transfer, and rebuild anything Google Labs made for you.
Do it this week, not in December. November 17 is the freeze date; December 17 is the deletion date. Between those two dates you get one month of safety net — use it to verify, not to start.
And once you are through the migration, build the habit that makes Skills worth it: every time you catch yourself typing the same setup prompt for the third time, turn it into a skill instead. That is the whole philosophy — save your most-used instructions once, and run them endlessly.
Both images in this article are AI-generated illustrations created for this guide — they are not screenshots of Gemini, Google products, or any real software.
Comments
Post a Comment