Gemini Skills Are Replacing Gems: What to Check Before You Move

Google announced on 30 September 2026 that skills are coming into Gemini chat and will replace Gems. For a small business that relies on saved instructions, the useful question is what will keep working, what must be checked and what needs rebuilding.

For a separate current example of controlled AI adoption, see our ChatGPT audio uploads workflow, which keeps human verification between the recording and any business action.

The most important distinction is between an ordinary Gemini Gem and an Opal workflow, also called a Gem made by Google Labs. Google describes automatic migration for ordinary Gems. Opal workflows follow a different shutdown path. Treating both as the same product could leave a working process without a replacement.

This guide was checked against Google’s documentation on 1 October 2026. It offers a controlled migration plan, not a claim that we have tested your account. Keep the work within your small-business AI operating plan, including approved data and a named reviewer.

What has changed, and who can use skills?

A skill stores instructions that Gemini can reuse across chats. In its 30 September announcement, Google describes selecting skills with a slash command, combining them and using reference files. The rollout begins with personal accounts; Workspace access is planned for the following weeks.

The current create-and-manage documentation is more specific: users must be at least 18, use a personal Google Account and have Keep Activity enabled. Availability is gradual. Skills in chat do not require a Google AI subscription, but that does not mean every related task or scheduling feature is included.

Check your actual account before designing a business process around the feature. If a work account does not yet expose it, do not move company information into a personal account just to get early access. Prepare the inventory and test cases while your administrator reviews the supported route.

Put the correct migration date beside each workflow

Google’s Gems transition guidance lists three periods for removing ordinary Gems: November 2026 for personal accounts, March 2027 for Workspace business, enterprise and nonprofit accounts, and June 2027 for Workspace education. It says Gems and supported files will be recreated as skills automatically.

Those are account-specific migration periods, not one universal deadline. Record which account owns each Gem and who depends on it. An agency may have a personal experiment, a company workflow and a school-related account with different dates. Do not assume that a change in one proves the others have migrated.

Automatic migration is a starting point for review. Keep a permitted copy of essential instructions, reference-file names and expected outputs in storage your team controls. The AI vendor exit rehearsal explains why a readable backup should support a complete task, rather than simply exist as an archive.

Keep Opal on a separate action list

The official Opal FAQ, updated on 30 September, names 17 November 2026 as the service shutdown date. Existing Opal workflows will not migrate automatically. Google says their files remain in the owner’s Drive, but the workflows will no longer run interactively after shutdown.

If an Opal app handles a useful business task, assign an owner to document its inputs, intermediate steps, tools and final output. Preserve the prompts and reference material you are entitled to keep. A folder of workflow files is not evidence that the workflow can still execute elsewhere.

Then choose the replacement according to the job. A reusable drafting instruction may fit a skill. A mini-app with branching steps, integrations or an interactive interface needs a separate rebuild assessment. Do not promise customers continuity until the replacement has passed a representative end-to-end test.

Check feature gaps before calling the move complete

The transition help page says skills do not yet support several Gem features, including Canvas, Deep Research, video creation, music creation and Guided Learning. It also says GitHub files are not currently supported. Sharing and additional connected-file options are described as forthcoming, so do not mark them present merely because they are on the roadmap.

Make a short dependency record for each important Gem: the instruction it follows, the files it reads, the tool it needs, the output it creates and the person who approves it. Mark each dependency as observed working, unresolved or unnecessary for this task. This prevents a successful text response from hiding a missing tool.

Google’s management guide also reports temporary mobile saving and file-editing limitations, with the web app offered as a supported workaround. It documents uploaded skill folders with a SKILL.md file and supported references; internet-dependent scripts are not supported. Recheck the live documentation before a technical migration, because these details can change.

Run one useful test before moving the whole collection

Start with a modest task using public or invented material. For example, imagine a training business whose Gem drafts a workshop description from a public course outline. The intended output is a short draft with accurate dates, no invented testimonials and an explicit list of missing information. This is a fictional test design, not a reported result.

Save the original instructions and one representative input. Decide what a reviewer will check before running the replacement: the date, audience, included topics, word limit and unsupported claims. Use the same input for both versions where access permits, and compare the outputs against the source rather than asking which sounds more confident.

Include one difficult case. Remove the workshop date from the test outline. The acceptable response should flag the missing date, not invent one. Then introduce a conflict between a tone preference and the factual source: the style instruction asks for an enthusiastic description, but the source contains no results or testimonials. Accuracy should remain a requirement.

Inspect the reference files as well as the generated text. Ask a question whose answer depends on one approved file, then check the answer yourself. Record the filename and version used. If the file is missing or inaccessible, keep that dependency unresolved; do not silently replace it with the model’s general knowledge.

Finally, check how the skill is selected. Test an explicit request and a nearby request where it should not apply. A writing preference that works for a workshop draft may be inappropriate for a complaint response. Keep human approval before consequential actions, including sending or publishing the result.

Write a clear, bounded instruction

Google’s skill-writing guidance recommends a focused job, a useful description and concise task-specific instructions. For the fictional workshop example, an instruction could look like this:

Use this for drafting workshop descriptions from an approved outline.
Write a clear draft of no more than 150 words for the stated audience.
Use only supplied facts; list missing dates, prices or promises separately.
Do not invent testimonials, outcomes, availability or urgency.
Return the draft and a short factual-check list for a human reviewer.
Do not send, publish or change source files.

This is an editorial starting point, not a security control. A request to avoid publishing does not replace the permissions and approval controls of connected tools. Review the instruction with the person responsible for the workflow, then test whether the actual behaviour matches it.

Give the tested version an owner and a review date. Keep the original available until you have reconciled important files, outputs and open tasks. If several people use the workflow, explain the new entry point and the known limitations before switching their routine work.

Google’s broader 8 October work-agent announcement is a separate access decision. Use the Gemini work-agent pilot guide to check early access and test a bounded job before expanding permissions.

Reader Q&A

Are Gemini skills available to every account now?

No. Google describes a gradual rollout beginning with personal accounts for adults. Check the current account requirements and visible availability; work and school access follows a separate rollout.

Will ordinary Gems become skills automatically?

Google says ordinary Gems and supported files will be recreated as skills when Gems are removed. Review important instructions, files and outputs after the transition instead of assuming every dependency works unchanged.

Is the Opal shutdown the same as the Gems migration?

No. The Opal FAQ gives 17 November 2026 as its shutdown date and says workflows will not migrate automatically. Saved Drive files remain available, but that does not keep the hosted workflow running.

Should I move business data into a personal account to try skills?

Do not bypass your organisation’s data and account rules to obtain early access. Prepare a non-sensitive test and have the responsible owner confirm the appropriate account and permitted information first.

Can a saved skill replace a complete mini-app?

Not automatically. Compare the actual inputs, tools, branching logic, interface and outputs. A reusable instruction may cover a drafting task while a multi-step app needs separate rebuilding and testing.

What is a sensible first migration test?

Choose one low-risk task with public or invented inputs. Check facts, reference-file use, missing-information handling and review requirements, then record observed gaps before moving more workflows.

Make the transition a checked handover

Inventory one important Gem or Opal workflow today, identify its account and product type, and attach the correct date and owner. Preserve the instructions you need, test a bounded replacement and keep unresolved dependencies visible. The goal is continuity of useful work, with evidence that the replacement can do the job.

Garry Knight

I'm Garry Knight, the person behind Prodify Digital. I write about email list building, email marketing, SEO, AI search and the tools that connect them. My aim is to make online marketing easier to understand, so creators and small business owners can make informed decisions about building an audience and keeping people engaged. Here you'll find straightforward guides and product reviews that explain what something does, where it fits and which limitations matter. The focus is on clear explanations and useful next steps—not hype, shortcuts or promises of easy earnings.

See Full Bio