Google Rolls Out Gemini Skills and Sets the Clock on Gems

Google announced the Gemini chat rollout on September 30

Google announced on September 30, 2026 that skills are rolling out directly in Gemini chat globally. The launch footnote says they are available across Google AI subscription tiers for people 18 and older, with under-18 access planned later. Google says Workspace business, enterprise, nonprofit and education availability will follow in the coming weeks; the current help page still says work and school accounts cannot use the feature.

This is a Gemini product and workflow update, not a new model or API release. Google does not name a model ID, publish a developer endpoint, quote a separate skills price or provide service-level limits in the reviewed pages. Account eligibility and rollout state should be checked in the actual Gemini client rather than inferred from the global announcement.

Skills turn repeated prompts into reusable workflow components

A skill stores custom instructions that can be reused across chats and tasks. A user can type “/” and choose a skill, while Gemini can also activate a relevant enabled skill automatically from the context and intent of a prompt. Multiple skills can be combined in one task, and one skill can reference another.

Google says skills can be built from a chat, with Gemini’s help, from a template or by uploading a file or folder containing SKILL.md and optional supported reference files. The launch announcement names text documents, PDFs and images as reference inputs. These are useful packaging features, but they do not establish deterministic execution, output accuracy or a stable developer contract.

Current access has account, age, activity and client boundaries

The live help page says users must be 18 or older, sign in with a personal Google Account and keep Gemini Apps Activity enabled. It describes a gradual rollout, so an eligible account may not see skills immediately. The listed clients are the Gemini web app, Gemini mobile app and Gemini app on Mac.

Google currently flags two defects: manually created skills do not save in the mobile app, and skills with uploaded files cannot be edited in the mobile or Mac apps. Its temporary path is to create conversationally or use the web app, and to edit file-backed skills on the web. Teams should treat client parity as unverified until these notices are removed and their own account passes a smoke test.

Gems now have three retirement windows

Google says Gems support will start ending in November 2026 for personal accounts, March 2027 for Workspace business, enterprise and nonprofit customers, and June 2027 for Workspace education customers. It plans to recreate existing Gems as skills automatically when Gems go away. Google also says sharing, Google Drive files and notebooks from Gemini Notebook are coming to skills in the weeks around the transition.

Automatic recreation is a migration mechanism, not evidence of behavioral equivalence. The separate launch footnote says experimental “Gems by Google Labs” will not migrate. Google also says Opal will turn down with the personal-account change in November. Owners should therefore identify the exact product and account type behind each workflow before relying on automatic migration.

Skills in chat are not the same contract as Gemini Spark

Skills were already available in Gemini Spark before this chat rollout. Spark is Google’s separate personal agent surface for managing tasks and schedules using connected apps, websites, chats, location and other sources. Its help page requires a personal account, Keep Activity and a Google AI Pro or Ultra subscription, and currently excludes the European Economic Area, Nigeria, Switzerland and the United Kingdom.

Do not transfer Spark’s price or regional rules wholesale to ordinary Gemini chat skills. The reviewed chat-skills help page does not list the same subscription or regional prerequisites, while the launch footnote references Google AI subscription tiers. The documentation therefore supports reporting distinct surfaces, not claiming universal free access or identical availability.

Automatic activation raises a control question

Convenient automatic selection also means an instruction bundle can affect a response without the user naming it in that prompt. Before enabling a skill automatically, test prompts that should activate it, near-miss prompts that should not and conflicts between stacked skills. Record which skill ran, which files it could use and what output changed.

Reference files and cross-skill composition expand the context boundary. Keep confidential material out unless the account’s data controls and intended users are approved. Separate style and formatting instructions from any workflow that could send messages, modify files or take other consequential actions, and require an explicit review or approval step where an error carries material cost.

What Gem owners should do before migration

Inventory every Gem by owner, account class, instructions, knowledge files, sharing scope and business dependency. Export or separately retain critical instructions and source files before the applicable retirement window. Recreate high-value workflows early in a noncritical setting, pin a small acceptance set and compare outputs from the Gem and skill without silently changing the evidence or model configuration.

Adopt skills now for low-risk reusable instructions when the account has access and the web client passes a save-and-reopen check. Constrain automatic activation until trigger and conflict tests pass. Wait for promised sharing, Drive, Notebook or Workspace support when those are requirements. Replace the workflow rather than migrate it unchanged if it depends on undocumented behavior, unavailable files or unattended consequential actions.

Disclosures

AccessAllGPT received no Google account access, subscription, credits, briefing, demo, migration support, review or compensation for this article. Google did not sponsor, review or endorse it. AccessAllGPT Research is operated by NeuralArc, is independent, and is not affiliated with Google. Publication-wide relationships are listed on the disclosures page.