Gemini’s shift from Gems to skills changes how you reuse instructions

A carefully refined set of instructions can be more valuable than any one AI answer. Google’s move from Gems to skills changes where those instructions live and how they are called into a task. The company’s 30 September announcement describes skills that can be combined within a conversation, rather than requiring a separate Gem window.[1]

For someone who repeatedly prepares product descriptions, edits articles or structures a weekly report, the practical opportunity is to preserve the procedure and apply it to fresh material. Existing Gems still work.[5]

What a skill changes in daily use

Google’s personal-account help describes skills as available to adults aged 18 or over with Keep Activity enabled. A paid Google AI subscription is not required for chat use. Supported surfaces include the mobile app, Mac app and web; file-based skill uploads currently require web or Mac. For managed accounts, the announcement scheduled rollout to begin on 13 October; the start of a rollout does not mean every account receives the feature that day.[3][1]

A skill has a name, a description and instructions. Google says Gemini first checks the name and description for relevance, then loads the instructions and opens reference files as needed. This makes the description operational: it should say which work calls for the procedure, rather than merely giving the assistant an impressive job title.[4]

For example, a proposed check-product-specification skill could apply when comparing a supplied product description with its manufacturer’s specification. Its description would identify that task; its instructions would name the fields to compare, require unsupported claims to be marked and preserve model numbers exactly. A separate publication-style skill could then shape the wording. These are illustrative uses, not measured performance results.

A useful skill is specific enough to capture recurring decisions while leaving room for a new input. Keep the procedure separate from this week’s product or article. Include one short example of an acceptable result and a precise explanation of what to do when a required fact is missing. Google’s writing guidance recommends focused instructions and clear situations in which the skill should apply.[4]

Create one now, or keep the existing Gem until migration

The simplest documented route is to ask Gemini in chat to create a skill from your instructions. It saves the result to Settings > Skills, where you can edit its description and instructions. To call it explicitly, enter / and select the skill, or @ where the updated shortcut is available. Active skills can also be selected automatically when relevant.[3]

To recreate a Gem manually, copy its name, description and instructions into a new skill. If it contains knowledge files, download them, download the new skill’s ZIP and place its SKILL.md file with those references in a folder bearing the skill’s name. Use Replace skill to upload that folder. Waiting for Google’s automatic transition remains an option; supported knowledge files are included in that promised migration.[2]

For a Gem that already uses a Drive document, this difference matters. Current Gems can reference the latest version of that file when it changes. Moving its instructions into a skill does not by itself establish that the same live source connection has moved too. Keep that dependency visible in the working brief until the matching feature is available.[5][2]

Make the recurring procedure easier to maintain

Use the first few attempts to improve the instruction that caused the mistake. If a specification review keeps confusing an optional accessory with an included item, add that distinction to the relevant step. Avoid accumulating unrelated requests in one giant skill: separate editorial style, specification checking and output formatting when they are useful on different jobs.

For managed accounts, Google says automatically migrated skills initially appear as inactive drafts, requiring the creator to review and activate them. That is an opportunity to confirm what the old Gem depended on, including its knowledge files and workflow connections, before the team makes the new skill its regular starting point.[6]

The value of the change is a procedure that can travel with the conversation. A reader can bring in fresh material, apply the relevant instructions and continue the job in the same thread, while keeping the reusable method available for the next assignment.

Report an error or suggest a correction