Direct answer: Google is replacing Gemini Gems with reusable skills. In Gemini chat, you can invoke a skill by typing / followed by its name, let Gemini apply a relevant skill automatically, or combine multiple skills for a larger task. Existing Gems are scheduled to be recreated as skills automatically, so you do not have to rush into a manual migration.[1][2]
What you should do now
- No important files in your Gems? Wait for Google’s automatic migration, or recreate a Gem manually if you want to use it as a skill immediately.[2]
- Your Gem uses uploaded knowledge files? Download a copy of every file now. Google says files can be moved manually, but GitHub files are not currently supported in skills.[2]
- You use a personal Google account? Google says support for Gems will begin being removed in November 2026.[1]
- You administer Workspace? Plan around a gradual rollout and later retirement dates rather than assuming every user will see Skills on the same day.[3]
- You are creating a new reusable workflow? Build it as a skill instead of investing more time in a new Gem.
Gemini Skills vs Gems: the practical difference
| Feature | Gemini Skills | Gemini Gems |
|---|---|---|
| Where you use it | Directly in a Gemini chat | Opened through the Gem experience |
| Fast invocation | Type /skill-name; Google says @ invocation is planned |
Select or open the Gem |
| Automatic selection | Gemini can recognize when a skill is relevant | Not the new default workflow |
| Combining workflows | Multiple skills can be stacked in one chat | Separate Gem behavior |
| Reference material | Text files, PDFs and images are supported | Knowledge files supported |
| Portability | Workspace describes skills as Markdown-native and based on SKILL.md |
Google-specific Gem setup |
| Future status | New replacement workflow | Being phased out |
Google describes skills as reusable custom instructions. The company says they can be triggered in chat, applied automatically when relevant and stacked for more complex work.[1][2] Google Workspace also says the format is based on the open, Markdown-native SKILL.md standard, which is intended to make instructions easier to move between supported platforms.[3]
How to use Gemini Skills
1. Check whether Skills is available
Open Gemini and look under Settings → Skills. Rollout timing depends on account type and domain, so the menu may not appear immediately even though the launch has been announced.
For the consumer Gemini experience, Google announced a global rollout beginning September 30, 2026. Workspace’s administrator-facing schedule is different: Skills in Workspace begins rolling out October 5, while Skills in the Gemini app for Workspace begins October 13, with completion expected by mid-November.[1][3]
2. Create one narrow skill
Start with a repeatable task that has a clear output. A narrow instruction is easier to test than an “assistant that does everything.” Useful first skills include:
- turning meeting notes into actions, owners and deadlines;
- rewriting text in a defined brand voice;
- converting a rough brief into a presentation outline;
- reviewing a document against a checklist;
- generating several distinct options before recommending one.
Google’s own examples include presentation preparation, matching a writing style and generating multiple perspectives.[1]
3. Give the skill four kinds of information
Use this copy-paste structure when you draft the instructions:
ROLE
You are a [specific role] helping me with [specific job].
TASK
When I provide [input], produce [output].
RULES AND CONTEXT
- Follow these rules: [rule 1], [rule 2], [rule 3].
- Use attached reference files when relevant.
- If required information is missing, identify the gap instead of inventing it.
OUTPUT FORMAT
Return:
1. [first section]
2. [second section]
3. [final checklist or next action]
The important part is not length. It is giving Gemini a defined role, task, constraints and output format.
4. Test it with a normal and a difficult example
Before relying on a skill:
- Run a typical request.
- Run an incomplete request and check whether it asks for or identifies missing information.
- Run an edge case that should be rejected or flagged.
- Confirm that attached files are actually reflected in the answer.
- Revise the instructions where the output is ambiguous.
5. Invoke or combine skills
Type / and the skill name in the Gemini prompt box. Google says Gemini can also match a skill automatically to a relevant prompt. For a more complex job, combine skills—for example, a research-format skill with a brand-voice skill.[1][2]
How to move a Gemini Gem to a Skill
Easiest option: wait for automatic migration
Google says remaining Gems will be recreated as skills automatically when Gems are removed. For Workspace, remaining Gems are expected to become draft skills, which means an administrator or user should still review the migrated instructions before treating them as production-ready.[2][3]
Use this option when:
- the Gem is not business-critical;
- you have few or no attached knowledge files;
- you do not need the skill immediately;
- you are comfortable reviewing it after migration.
Manual option: recreate it now
Google’s current migration process is:
- Open the Gem you want to move on a computer.
- Choose Edit and copy its name, description and instructions.
- Download each file listed under the Gem’s Knowledge section.
- Open Settings → Skills in Gemini.
- Choose Create manually.
- Paste the Gem’s name, description and instructions, then create the skill.
- If there are no knowledge files, test the new skill and stop here.
- If there are files, download the new skill’s ZIP file, which contains
SKILL.md. - Put
SKILL.mdand the downloaded knowledge files in one folder. The folder name must match the skill name and use lowercase words separated by hyphens. - Use Replace skill and upload that folder.[2]
Important limitation: Google says GitHub files are not currently supported in skills. If a Gem depends on a GitHub file, preserve the original reference and do not assume it migrated successfully.[2]
Migration checklist for teams
Copy this checklist into your project tracker:
- [ ] Inventory every active Gem and its owner.
- [ ] Mark which Gems are business-critical.
- [ ] Copy each Gem’s name, description and instructions.
- [ ] Download all attached knowledge files.
- [ ] Record any GitHub-backed file separately.
- [ ] Recreate urgent Gems as skills manually.
- [ ] Test one normal request and one edge case.
- [ ] Check access to every reference file.
- [ ] Review automatically migrated draft skills.
- [ ] Update internal documentation that tells users to open a Gem.
- [ ] Check Workspace Studio flows that use Ask a Gem.
- [ ] Assign a final owner for each shared skill.
Workspace dates administrators need to know
| Date | Workspace change |
|---|---|
| October 5, 2026 | Skills begin rolling out in Workspace; expected completion by mid-November |
| October 13, 2026 | Skills begin rolling out in the Gemini app for Workspace; expected completion by mid-November |
| November 17, 2026 | Gems move into the Gemini app’s Settings panel but remain usable |
| No sooner than March 1, 2027 | Business and enterprise users lose the ability to create, edit or use Gems; remaining Gems are auto-migrated to draft skills |
| No sooner than June 1, 2027 | Education users reach the corresponding Gems removal point |
These are Google’s published Workspace dates, and “no sooner than” is important: they are earliest retirement dates, not a promise that every tenant changes at the same instant.[3]
Workspace administrators should also audit automations that use the Ask a Gem step. Google says those flows stop working when Gems are removed for the applicable account type.[3]
Three ready-to-adapt Skill instructions
Meeting action extractor
You turn meeting notes into an action register. Identify decisions, unresolved questions, action items, owners and deadlines. Never invent an owner or date. Mark missing owners and dates as “Not assigned.” Return a short summary followed by a table with Action, Owner, Due date and Status columns.
Brand-safe content reviewer
Review the supplied draft against the attached brand guide. First list any unsupported claims, missing evidence or style violations. Then provide a revised draft. Preserve verified facts and links. Do not invent statistics, testimonials or product capabilities. End with a checklist of changes made.
Proposal builder
Turn the client brief into a proposal outline. Include the problem, scope, deliverables, exclusions, dependencies, timeline assumptions and next step. If price, deadline or scope is missing, label it “To be confirmed” rather than guessing. Use a concise professional tone.
Common migration mistakes
Assuming “automatic” means “verified”
Automatic recreation saves setup time, but you should still compare the new skill against the original Gem. Test attached files, formatting rules and refusal conditions.
Deleting the Gem before preserving its files
Download important knowledge files first. This gives you a recovery copy if an attachment is unsupported or fails to appear in the migrated skill.
Building one oversized skill
A skill for “all marketing work” is difficult to test. Separate research, brand voice, fact-checking and final formatting so each workflow has a clear job. Skills can be stacked when a task needs more than one behavior.[1][2]
Treating account rollouts as identical
Consumer Gemini and managed Workspace accounts follow different rollout details. Use the schedule for your account type and verify availability inside the actual account.[1][3]
Frequently asked questions
Are Gemini Gems being discontinued?
Yes. Google says skills will replace Gems. Removal begins in November 2026 for personal accounts, while business, enterprise and education accounts have later Workspace timelines.[1][3]
Will my existing Gems disappear?
Google says it will automatically recreate Gems as skills when Gems are removed. Workspace documentation says remaining Gems will be migrated as draft skills.[2][3]
How do I run a Gemini Skill?
Type / followed by the skill name in a Gemini chat. Google also says Gemini can apply a relevant skill automatically, and that @ invocation is planned.[1][2]
Can I use more than one Skill at a time?
Yes. Google says skills are stackable, so multiple skills can be combined for a more complex task.[1][2]
Can Gemini Skills use files?
Google says skills can include plain-text documents, PDFs and images. Its migration help page currently says GitHub files are not supported.[1][2]
Do I need to migrate my Gems manually?
Not necessarily. You can wait for automatic recreation, but manual migration is useful when you need the skill now or want to preserve and test important knowledge files before the retirement date.[2]
Bottom line
Do not panic-delete your Gems. Back up important instructions and knowledge files, recreate urgent workflows as skills, and let Google migrate low-risk Gems automatically. For teams, the real job is validation: assign owners, test migrated draft skills and update any documentation or Workspace Studio flow that still depends on Gems.